Our European vision: sovereignty is a setting, not a sticker
Digital sovereignty has become a logo on a website. We think it is a property of a configuration: where inference runs, who can be compelled to disclose, and whether a rule refuses a call or merely disapproves of it. This is what we are building in Europe, what we can point at in code today, and the three claims we deliberately do not make — including that our own process model has its own weights.
Nearly every software vendor selling into Europe now has a sentence about European hosting. Almost none of them have a control. That gap is not a marketing problem; it is what makes procurement departments treat the whole subject as theatre, and it is the reason a team that genuinely needs data residency has to read architecture diagrams instead of a checkbox.
This is what we believe instead, and what we have built to back it. It is a position piece rather than a specification — the checkable version, with the six questions we would ask a supplier, lives in what “EU-hosted” actually has to mean.
Why build this in Europe at all?
Not out of sentiment. Three reasons, in descending order of how much they would still hold if the politics changed tomorrow.
Because the work we automate is the work with the customer’s words in it. A coding assistant sees code. A delivery platform sees the analysis document, the bug report with a customer’s name in it, the e-mail thread pasted into a requirement, the test case built from someone’s personal data. That is the material that makes a data protection officer ask where it goes, and they are right to ask.
Because process work is winnable and code work is not. The frontier labs are spending more on code generation than we will ever raise, and they are extremely good at it. Turning an analysis into a correct backlog, deriving test cases from acceptance criteria, composing release notes from merged pull requests — nobody has a benchmark for that, and the data to learn it is generated by our own platform. A smaller European model can win a narrow, high-volume job. It cannot win the general one.
Because there is a real customer here who cannot buy the alternative. Public sector, healthcare, finance, and anyone with a works council. Their constraint is not a preference to be overcome by a better demo; it is a rule. Building for that constraint from the start is easier than retrofitting it, and the retrofit usually turns out to be impossible.
What sovereignty actually buys, and what it does not
It is worth being precise, because inflated claims here have poisoned the well. Data residency answers where the bytes sit. It does not by itself answer who can be compelled to produce them — a European datacentre operated under non-European disclosure law is a European datacentre with a caveat. Whether that caveat matters depends on your sector, and pretending it does not exist is how vendors lose the customers who understand it best.
What it does buy is real: a shorter chain of custody, a jurisdiction whose rules you can read, a supplier you can subpoena in your own language, and — the underrated one — an answer to the question your customer will ask you, not us. Most of our users are agencies. Their sovereignty story is the one they have to tell their own client.
Three things we can point at instead of claiming
A claim is a sentence. A control is a thing that refuses. These three are in the product, and each one is checkable by someone who has an account and ten minutes.
- The process work runs on our own model, in France. Turnado‑1 serves the routine process work — classifying comments, deriving test cases, drafting release notes — on Mistral’s platform. Ten models sit in the catalogue; seven of them run inside the EU, and every one states which it is on the screen where you pick it.
- An organisation can refuse non-EU inference. Switch on “EU only” and a model hosted outside the EU is not logged for later review — choosing one is refused at the moment you choose it, and if the rule tightens after the fact the lane falls back to an EU model with the reason recorded against the run. A rule that produces a report is a suggestion; a rule that produces a refusal is a rule.
- The code work never has to touch us at all. You bring your own key, or your own endpoint: on-premise, your own cloud, your own contract. For a customer whose code may not leave their walls, that is the difference between a pilot and a no.
Why our base model is European, and why that is partly a legal question
The obvious answer is data residency, and it is the less interesting one. The binding reason is contractual: the terms of most commercial model providers forbid using their output to train a competing model. Turnado‑1 is a competing model. So every run that happens on a commercial model is training data we are not allowed to use — and without usable training data there is no flywheel, only a resale business.
That constraint is why outputTrainable is a field on every entry in our model catalogue rather than a note in someone’s head, and why an agent run records whether it may ever be used for training. The permission your organisation gives us covers your data. It cannot cover a model vendor’s.
What being European does not excuse us from
A European product that is worse is not a European win; it is a subsidy request. The flag does not substitute for the platform being good, and it does not substitute for the guarantees that have nothing to do with geography: conditions calculated outside the model, a set of permissions no agent ever receives whatever roles it is given, every run recorded with its model, its duration and its cost against the work item it was made for.
Those are the things that make an audit answerable, and an auditor does not care which continent the answer came from. We happen to think both matter. We are not asking anyone to accept one instead of the other.
Three claims we deliberately do not make
- That Turnado‑1 is our own weights file. It is our prompts, our tool contract and our yardstick, running on an open European model. Saying otherwise would be a claim that quietly becomes a lie the moment somebody asks a specific question.
- That your custom endpoint is EU-hosted because we say so. When you point Turnado at your own endpoint, that promise is yours: you chose the machine. We cannot verify it and we do not pretend to.
- That we are AI Act compliant on your behalf. Most delivery tooling is not high-risk under the AI Act, and vendors implying otherwise are selling fear. What we can do is produce the boring, useful part — a record of which system did what, per work item, with the human decisions still human.
Where this goes next
The direction is narrow and unglamorous: move more of the process work onto our own model as the evaluations justify it, one lane at a time, and never the code work. Publish what the evaluations say, including when the challenger loses. Keep the refusal messages readable, because an administrator who does not understand a refusal removes the rule rather than the cause.
If a European claim is going to mean anything again, it will be because a handful of products made it checkable rather than because more of them made it loudly. That is the part we can actually control.
What is digital sovereignty for a software delivery platform?
In practice it is four separate answers, not one: where inference runs, where the data rests, which jurisdiction can compel disclosure, and whether the rule is enforced when a call is made or merely written down. A platform delivers sovereignty when a non-EU model can be refused at call time, with the reason attached, rather than reported on afterwards.
Is there a European alternative to US AI coding tools?
For code generation, the strongest models are largely non-European, and open European models such as Devstral are a genuine option at roughly a tenth of the price rather than a like-for-like replacement. The layer around the code work — the board, the process, the records — is where a European platform competes on equal terms, which is why Turnado runs the process work on its own EU-hosted model and lets you choose whatever model you like for the code.
Can I run Turnado without any data leaving the EU?
Yes. Switch on EU only for your organisation, which refuses any model hosted outside the EU at the moment of the call, and pick EU-hosted models for all three kinds of work — seven of the ten models in the catalogue qualify, and a custom on-premise endpoint counts as your own promise rather than ours. What you cannot get is a guarantee about a provider we do not operate.