Who you are actually dealing with.

Latreia Technologies has been taking over and running custom software for fifteen years. This is the record, and these are the people answerable for it.

15+ years20+ clients100+ projects

The short version

Latreia takes over inherited custom software: the systems a business runs on when the people who built them are gone. Much of the work is for member based organisations, where one platform carries certifications, events, affiliations, and years of rules that exist nowhere else and cannot be bought off a shelf. We audit what is there, fix what is worth fixing, and then run it on a monthly plan.

We are not the firm that arrives wanting to rebuild everything. The audit exists to tell you the truth about what you have, and recommending less work than we were asked for is a normal outcome.

Who runs the work

Every engagement is answerable to a name.

Jan Stander, Managing Director at Latreia Technologies

Jan Stander

Managing Director

Jan leads the company: the direction it takes, the commitments it makes, and the standard everything here is held to. If something about an arrangement with Latreia is not working, he is the one to tell.

LinkedIn profile
Hardus Fourie, Software Director at Latreia Technologies

Hardus Fourie

Software Director

Hardus carries ultimate responsibility for every client and every project. He runs the audit and writes the finding, then owns the scope and the price that follow from it, including the findings that tell you to do less work than you asked for.

LinkedIn profile
Sasha Stojanovic, Head of Engineering at Latreia Technologies

Sasha Stojanovic

Head of Engineering

Sasha owns what gets built and what keeps running, end to end: the technical standard on every project, the documentation, and the resolution of anything that breaks. On most engagements he is the technical contact you deal with directly.

LinkedIn profile

If we disappear

Putting names on a page is the easy half. The arrangement underneath it is the half that matters: your code in your repositories, your infrastructure in your cloud subscription, documentation written for whoever comes after us. That is set out in full on how we work.

The audit is where it starts.

Book the audit