Digital sovereignty is a capability, not a badge.
Being able to choose your dependencies, and to leave them. Here is what that means for your software, your data and your suppliers.
Digital sovereignty gets talked about a great deal, usually as a badge or a hosting offer. Our definition is more down to earth: a company is sovereign over its tools when it can choose its dependencies and walk away from them without putting the business at risk.
The test is simple. If your vendor doubles its prices, if your supplier stops answering, if a provider changes its terms overnight: what happens next? If the answer is “we have no choice”, you do not own your tools. You rent them, on terms you never negotiated.
Sovereignty is not something you declare. It is built project by project: in the choice of standards, in where the data is hosted, in who owns the code, and in who controls the technical accounts.
What that changes on our projects
Open standards
Documented data formats, widely used building blocks, no in-house framework. Whatever we build can be taken over by any competent team.
Your code, your data
The repository is in your name with its full history, the exports are documented, and the database belongs to you, structure included.
Account control you can take back
Hosting, domains, email: we can administer them while we work together, and we sign over full control whenever you ask.
European suppliers by preference
Where the service is comparable, we choose a supplier under European law. And where no serious alternative exists, we say so.
Where Europe holds its own
Hosting is the clearest case. This site runs on Scaleway in Paris, under European law, and we are building Tensel to make that choice as easy as deploying with an American giant.
In other areas the gap is still real. We will never recommend a worse tool purely because it is European: the choice is compared, explained, and fitted to your situation.
Frequently asked questions
What is sovereign software?
Software whose code, data and technical accounts you control. You can hand it to the team of your choice, host it where you like and leave with your data: sovereignty is measured by how easy it is to walk away, not by the flag on the brochure.
Is digital sovereignty the same thing as hosting in Europe?
No. Hosting in Europe shields your data from non-European law, but software hosted in Paris whose code and exports you do not own is still a rental. Hosting is one part of the answer; reversibility is the test.
Should we replace every American tool?
No, and we do not advise it. Many are excellent and some have no serious equivalent. Our rule: where the service is comparable, prefer a European supplier; where it is not, choose knowingly and keep a documented way out.
How do you make custom software reversible?
Through choices you can verify: the code in a repository in your name, widespread standards rather than an in-house framework, operating documentation, documented data exports, and control of the technical accounts signed over on request.
Where do we start, concretely?
With an inventory: who holds your accounts, your domain names, your code, your data? An audit of what you already run often shows the riskiest dependency is not the one you expected. It is also a far cheaper starting point than a forced migration.
Tell us what brings you here.
A specific project, an idea that is still vague, or something you already run and want an outside opinion on. The first conversation commits you to nothing, and you will be talking to one of the two founders.
We reply within 24 working hours