Sovereignty falls out as a natural consequence of engineering for ownership.

Twenty years in IT, fifteen professional, since I was twelve and fixing whatever was broken in the house. My first formal role was an apprenticeship in Plymouth at seventeen. Then The Hague. Then a security engineer at Fox-IT.

Then Principal Solutions Architect at SuperBrave, migrating a fourteen-year-old PHP monolith to Kubernetes for a healthcare product running 2.2 million consultations across sixteen countries. That is the kind of migration where a mistake shows up as a missed medical appointment, not a support ticket.

After that came four and a half years as de-facto CTO to a UK healthcare platform, the same client relationship carried across three different employers of record as my own business structure changed underneath it. DSPT, GDPR, CQC: three acronyms, one job, keeping patient data where it should be and proving it under audit.

By then I had spent long enough as the delivery engineer inside someone else's consultancy relationship to know exactly what slow, expensive, and locked-in feels like from underneath it. Genitco is the company I built to be the opposite: fast, fixed-fee, and legible enough that a client can see what they are paying for and why.

When I started building it, the first thing I did was price up the stack I'd need. Email. Documents. CRM. AI. Monitoring. Security. The number came back as a four-figure monthly bill, before a single client had signed, before I had hired anyone, before a line of product code existed.

The self-hosted alternative was a fraction of that in compute costs, about six weeks of serious engineering work upfront, and an ongoing operational load that was real but manageable. I had done that kind of engineering for two decades. The maths was clear.

That was not idealism. That was arithmetic.

We built the platform from open-source components, on infrastructure we control, hosted in EU jurisdictions. Every service self-hosted. Every credential in our own secrets manager. Every byte in named locations we can account for.

What we did not anticipate — or rather, what we built before we understood we were building it — was that sovereignty falls out as a natural consequence of this architecture. When you own the stack end to end, your data does not leave your jurisdiction by default. Your compliance obligations become easier to meet, not harder. Your exit from any one component is open.

We did not build a sovereignty product. We built an infrastructure product. Sovereignty is what you get when you engineer for ownership.

The platform that runs Genitco's own operations is the platform we sell. We use it every day. It is not a demo or a reference architecture. It is in production.