Twenty years. Same company.
We have been a software company in Rotterdam since 2006: around a hundred engineers across Rotterdam, Belgrade and Novi Sad, and the same company since day one. After twenty years we are still very fond of smart software. We invent it, design it, build it and look after it, and it shows how much we enjoy that.
Friday afternoons are spent on the roof terrace.
We are a close team, both in the office and outside of it. In Rotterdam, the week ends together on the roof terrace, with a view over the harbour that never gets old. From time to time, we organise trips between Rotterdam and Belgrade, which makes our three offices feel like one.
It is a place where colleagues stay for years. That is why the people who built your software are still here to look after it years later.
Rotterdam · since 2006An engineering company, with AI in production.
We have spent twenty years building software for organisations where a mistake is expensive: rail, parking, justice, publishing, education, healthcare. AI came on top of that, and we stayed the same company.
That order matters. It is why our first move with coding agents was to build the gates, and why our first copilot went into our own product, Yessa, before it went into a client’s.
We say what we do and do what we say.
Our method is written out in full on this website, and the foundation we build on is open source. That is the Rotterdam way: direct, and we would rather have an honest conversation in week one than a hard one in month nine. It also means honest advice: if a standard package largely fits, we say which one.
One software company, three cities.
We have been connected to Serbia from the start, with our own offices in Novi Sad since 2011 and Belgrade since 2013. Everyone who works on your system is employed by Enigmatry, under the same contracts and the same ISO 27001 controls. There is no time difference, and you always know who is working on your system.
Rotterdam
Head office, Groot Handelsgebouw. Client work, architecture, the people you meet.
Belgrade
Engineering. Same company, same standards, same definition of done.
Novi Sad
Engineering. Most of our engineers work in Serbia. If your policy requires the work to stay inside the EU, that is part of the scoping conversation.
Four things we were already doing long before AI.
Existing business. Transformed.
Replacing and modernising the platforms a business runs on, while the business keeps running.
Good idea. Realised.
We are a technical partner for start-ups and scale-ups, and sometimes an investor too: entrepreneurship is in our genes. We invest in ideas we believe in, and Yessa is one we built ourselves.
Data streams. Valuable insight.
Turning the data a business already produces into insight it can act on the same day.
Running software. Smartly managed.
Long-term management of business-critical systems, by the people who built them. Security by design, with the OWASP Top 10 as our baseline.
Craftsmanship you can check.
We care about craftsmanship, yes, but you don’t have to take our word for it. The foundation everything stands on is open source, so you can judge for yourself before you hire us.
Code is read far more often than it is written.
Someone joining in year six should be able to open a file and see what the business rule is without asking anyone. That is why we still take naming seriously in every code review.
The twentieth feature sits where the first one did.
Blueprint architecture: one way of doing a thing rather than fourteen. It is why a new engineer is useful within days, and why an agent can be pointed at a codebase and find its way around.
Every test has a reason.
A test exists because something broke once, or because something has to keep working, always. We report what the tests protect; the percentage follows from that.
Taste a machine can enforce.
Opinions get lost in a bad week or under a deadline. A gate stays. Everything we agreed about quality that could be made deterministic has been, and the rest is a conversation in review.
A good commit removes code.
Every line is a liability somebody has to understand in five years. Agents produce quickly, which turns restraint from a virtue into a daily discipline.
Written for the team after us.
We build as though the next team will read it in ten years without us in the room. That is what makes “you keep the code” worth saying.
On a website, these are just words. In a repository, you can check them, which is why ours is open.
“We found a strong partner in Enigmatry for our digital business transformation.”Eric Razenberg, CEO of ThiemeMeulenhoff
Read the NT2 Online case.
Six things the SaaS Factory and EnigmaSure share.
Two products, one way of working. These are the habits underneath both — and underneath everything else we build.
- ProofProof over promises. We publish the gate and the timed log; EnigmaSure turns “we can leave” into a signed record.
- Own riskOur own risk first. AI went into Yessa before any client product; EnigmaSure runs on our own product. The first product through the factory is our own.
- OwnershipOwnership stays with you. Open-source Entry, your code and data, source in escrow, buy-out in Partner, a rehearsed exit. We make it easy to leave us — and that is why clients stay.
- SecurityNeed-to-know as a habit, not a project. Development, test, acceptance and production strictly separated for years; developers on anonymised data; only ops reach production.
- EngineeringEngineering before paperwork. An exit is an engineering problem before it is a legal one; a questionnaire is answered by how you build, not by a policy document.
- EuropeanEuropean, and nuchter. Rotterdam, Belgrade, Novi Sad; EU hosting; plain language; twenty years of systems where an outage ruins someone’s day.
Read how this works in practice: the SaaS Factory and EnigmaSure.
Come up to the eighth floor.
An hour, a coffee, and the people who would actually work on your project. Drop by on a Friday afternoon and get to know us in person.
Stationsplein 45 · two minutes from Rotterdam Central Station