For months we told clients the same thing: your AI stays on infrastructure you control, under European law, out of reach of the US CLOUD Act. Meanwhile our own source code and build chain still sat on GitHub, an American platform owned by Microsoft. That gap bothered us. We closed it: all of our development now runs on a fully sovereign chain, end to end, with no US dependency. Here is what we changed, and why it says something about how we work. This piece expands on the post we shared on LinkedIn at the time of the move.
Our whole pitch rests on a simple principle: a truly sovereign AI runs on infrastructure you own, under a law you know, out of a third party's reach. That is the entire point of the CLOUD Act, the US law that follows American companies wherever their servers are. Yet our code, the very object of that promise, was hosted at GitHub, meaning at an American company subject to US law. We were asking our clients for a standard we did not hold ourselves to.
A principle stays abstract until it catches up with you. Our GitHub account got flagged. Overnight, the dependency became very concrete: a platform we don't control can freeze the place where our code lives, with no notice and no one to negotiate with. That is exactly the single point of failure we describe to our clients about cloud AI. Living through it has a clarifying effect. So we made the consistent choice: cut the cord.
Gungnir, and with it our whole ecosystem, now rests on a chain where every link is either ours or run by an independent European body:
A single command pushes the code to the forge and the mirror at once. The delivery process itself is identical to the one we had on GitHub, with one difference: none of its steps depends any longer on a provider outside our control.
In practical terms, no single company can pull the plug on our development anymore. The code has three independent copies, the chain that turns it into shipped software rests on no American provider, and the full process, from the first line of code to production, stays in our hands.
Sovereignty was never a line on a sales page for us. It is a property of how the thing is built, down to where the code is stored and how it ships. If we ask clients to trust that principle, we hold ourselves to it first. That is what it means, to us, to take sovereignty seriously: applying it all the way down to our own code.
On raw uptime, a large platform has means a single server does not. But reliability is not only technical, it is also legal and contractual. An account can be flagged, frozen or closed under rules you don't control. Three independent copies, one of them fully owned, protect against a kind of failure no uptime figure covers: a third party's unilateral decision.
Forgejo is open-source git forge software, the equivalent of GitHub but one you install and administer yourself. Codeberg is a European non-profit that hosts code on that same technology. One gives us a repository we own, the other an independent copy placed outside any commercial logic.
Sovereignty is not a purity test, it is a matter of control and jurisdiction over what matters. What we brought back home is the chain that decides where our code lives and how it ships: the repository, the backup, the image registry, the continuous integration. That is where the critical dependency was, and that is what we removed.
Moving all your development off a platform only makes sense if you host code. For most SMEs, the equivalent stake is about data and everyday tools, chief among them AI. The reasoning is the same: work out which third party you truly depend on, and bring back home whatever is critical. That is the principle behind Gungnir.
