Mistral's sovereignty framework leaves out the one question it would win.
Its commercial terms put a European customer under French law before the courts of Paris, exclusively. The four layers of control the company publishes do not mention a court at all.
Mistral's home page animates one sentence letter by letter as it loads. Mistral is #1 in Sovereign AI. Nothing after it says which sovereignty is meant, and there are at least four candidates.
I ask the same four of any claim like this, in this order. Where does the data sit. Who can log in. Which court can compel the company. Who owns the company. Four questions, four separate answers, and most claims answer one of them and let the reader assume the rest — usually in good faith, by somebody who has only ever been asked the first one.
Mistral is unusual, and that belongs at the top rather than saved for effect. It has published enough to answer three of the four properly, which is more than almost any vendor on this beat manages. The question it has not answered is the fourth. The question its own framework leaves out is the third, which is the one it would win.
Four layers, and the two that are not layers
The Sovereign AI page splits control into four layers: data, intelligence, compute, operations. Each gets a sentence. You control where your data goes and who can use it. You own and shape what your AI learns and becomes. You control where your AI runs and on whose infrastructure. A change of provider, model or infrastructure cannot stop the work your organisation depends on.
Then it does something I would put straight into a tender document. It gives a test: you should be able to resume training from your own checkpoint, reproduce a post-training run, move the model to another compute environment, and operate it without the original provider's services. If you cannot, the page says, a dependency remains. That is a four-part test a buyer can run, written by a vendor, against itself. Take it.
Data
Where your records sit, and who may use them.
Intelligence
Whether the model, its adaptations and what it learns stay yours.
Compute
Where it runs, and on whose infrastructure.
Operations
Whether the work survives a change of provider, model or infrastructure.
Which court can compel the company, and who owns the company. The page uses the word jurisdictional once, about the boundary a customer's workload needs. It does not mention applicable law, courts, shareholders, ownership or corporate structure anywhere.
The framework is written from the customer's side, which is a perfectly reasonable place to write it from and is also why it cannot ask either of those two. They are not questions about your estate. They are questions about the counterparty, and the counterparty does not appear on a map of your estate.
Where the data sits is in a list most vendors do not publish
Mistral's trust centre carries a sub-processor list, twenty-five entries, each with an activity, a set of locations and the products it covers. Microsoft Inc., cloud infrastructure, Sweden and Norway, for Studio and the API. Google LLC, cloud infrastructure, the Netherlands, Belgium, and the United States for the US API endpoint. Mistral Compute, France, all products. CoreWeave Inc., inference provider, EEA. Cloudflare for routing, worldwide. CrowdStrike for security, EEA and the United States.
The help centre adds that EU hosting is the default, that the US endpoint is used only if a customer explicitly selects it, that depending on the feature data can be temporarily transferred outside the Union under the Commission's standard contractual clauses, and that enterprise customers can switch the transferring features off for the whole organisation. The August announcement of regional endpoints prints the same caveat in its own voice: processing happens in the region you choose, with limited, safeguarded transfers to sub-processors that may operate outside it. A vendor that publishes the caveat next to the promise is doing something unusual and should be told so.
So: two accurate documents, both Mistral's. The April policy paper warns Europe against deepening its dependency on non-European hyperscalers. The sub-processor list names two of them as cloud infrastructure for Studio and the API. That is not a contradiction and I am not presenting it as one — the paper is about where Europe's future capacity gets built, the list is about who runs servers this quarter. The narrow point is about the word. A reader who took #1 in Sovereign AI to mean no American infrastructure anywhere in the chain has made a reasonable inference from the home page, and the trust centre is where it stops being true.
One procurement note, because nobody else will make it. The list carries no version number and no last-updated date. There is nothing to diff it against.
Who can log in is a list that can change without your signature
One entry on that sub-processor list is Mistral AI Affiliates, for all products, and it links to a page of them. Read it: thirty entities, effective 28 July 2026, across eleven jurisdictions. Mistral AI, SAS in Paris. A Luxembourg S.à r.l., a Singapore Pte Ltd, a UK Ltd, a Dutch BV, German and Swiss GmbHs, Spanish, Polish and Australian companies, a branch office in the United Arab Emirates, and Mistral AI Inc. in the United States.
The commercial terms say the products are provided by the Paris company or its affiliate as specified in an Order Form, and let Mistral subcontract or assign to an affiliate without the customer's prior written consent, remaining responsible for what that affiliate does.
None of this is sinister. It is how a company selling in twenty countries is assembled, and keeping responsibility with the contracting party is the right clause. What it means for your file is narrower and worth writing down: the set of entities that may process your data is a published list that can change without your signature, and one of them is incorporated in the United States.
The question it would win
Clause 14.10 of the commercial terms sets governing law by where the customer is headquartered. The Americas get California law and, exclusively, the federal or state courts of Santa Clara County. Asia-Pacific gets Singapore. Everyone else, which is every European buyer reading this, gets the laws of France and the exclusive jurisdiction of the courts of Paris. The contracting party is a French joint-stock company at 15 rue des Halles in the first arrondissement, registered under 952 418 325.
For a European buyer that is a clean answer, and a markedly cleaner one than most of this market gives. The usual shape is an Irish subsidiary of a Delaware parent and a clause pointing at Dublin, with a separate argument available about whose process reaches the parent.An American customer of Europe's sovereign AI champion litigates in Santa Clara County, California. That is a fact about commercial drafting rather than about sovereignty, and I include it because somebody is going to find it and draw the other conclusion.
The layers describe your estate. The clause describes your counterparty, and the counterparty is not on your estate.
It is also not one of the four layers. A buyer who reads the Sovereign AI page learns a great deal about where the model runs and nothing at all about who can be served with process. Mistral has the better answer of the two, and publishes it in the smaller type.
The question with no document
Mistral names its own investors, and the announcements are primary, so the fourth question can be taken a long way before it stops.
September 2025: a €1.7bn Series C at an €11.7bn post-money valuation, led by ASML Holding NV. The announcement says the round reaffirms the company's independence. Among the named participating investors in the same paragraph: NVIDIA, whose Hopper GPUs trained every model in the Mistral 3 family, three thousand H200s for Mistral Large 3, both figures Mistral's own.
September 2026: €3bn at more than €21bn post-money, led by Samsung Electronics, co-led by the Scaleup Europe Fund managed by EQT and by PSG Equity, with existing investors including a16z, ASML, Belfius, BNP Paribas CIB, Bpifrance, Carmignac, DST Global, Eurazeo, General Catalyst, Headline, Hillspire, Index Ventures, Korelya Capital, Lightspeed, NVIDIA and Salesforce Ventures.
Read that as a head of procurement rather than as an investor. A French company whose two most recent rounds were led by a Dutch listed manufacturer and a Korean conglomerate, with American venture capital across both, its own chip supplier on the register throughout, and the French state present twice over — Bpifrance on the cap table, the Caisse des Dépôts in the compute coalition. None of that makes Mistral less French, and the second round is the largest a European technology company has raised. All of it is the answer to question four, and question four is the only one of the four that none of Mistral's documents frames as an answer to anything.
What is not published is proportions. No percentage appears above for any investor, ASML included: its own release is reported to state one, and investor.asml.com would not serve this desk. France keeps no public register of a private company's shareholders, and the register that came closest was closed by the Court of Justice in 2022.
The structure is also still being built. The affiliate list carries fourteen French companies named Mistral Compute 1 to 14, a Mistral Compute Holding, and a company called Mistral AI Reserved. Fourteen numbered single-purpose vehicles under a holding company is the shape of an asset-financed build, and a sensible way to build data centres. Whether any of them is pledged to anybody is not on the site and I did not establish it. Sovereign is not a property of a data centre. It is a property of a corporate structure, and corporate structures change on a Friday.
The hyperscaler arrangement runs the other way
In July, Microsoft and Mistral expanded their partnership, and the direction is the opposite of the one most summaries assume. Mistral builds the European GPU capacity, on thousands of NVIDIA Vera Rubin GPUs, and Microsoft is the committed buyer of part of it, for its own AI development and its own cloud services, under a commitment Microsoft's release calls worth billions of dollars without giving a figure. No equity, no country named, no site named. Mistral is the seller here, which is a real achievement that the usual story about European dependency has no slot for.
Microsoft's release describes the arrangement as extending Microsoft's Sovereign Cloud approach, and quotes Brad Smith saying Europe should have access to the world's most capable AI without compromising control. Mistral's paper, ten days before the Commission announced its sovereign cloud awards, warned against deepening dependency on non-European hyperscalers. Three documents, three uses of the word, not one of them contradicting itself.
Where it appears in the Commission's own exercise
Bram Coppens read the Commission's framework on 16 October and the scale is his: nobody reached the top of it, and the consortium that includes Mistral came in at the floor while the three above it build their own technology.
Four things about that belong in the same breath as it. Mistral did not design the scale and did not assign the rating. The rating belongs to a consortium and to a technical environment, not to Mistral. A model provider is not a cloud provider, and the objectives scored are largely about running infrastructure. And a single SEAL number is shorthand for eight separate per-objective minimums, so anybody reading a company's position off one of them is reading a press release.
Mistral's news page, read for this piece, carries no announcement of the award. The likeliest explanation is the dull one: the framework went to Proximus, and a subcontractor does not announce somebody else's contract. Which is also the reading in which the company that calls itself first in sovereign AI is not the party that won the European Commission's sovereign cloud framework.
No question was put to Mistral for any of this. Everything above comes from documents the company publishes, which is the method and also the hole in it — a company that answers three questions in writing would probably answer the fourth across a table, and nobody here asked for the table.
So: the afternoon's work. Pull the sub-processor list and the affiliate list and read them against each other. Open clause 14.10 and find out which court. Run the company's own dependency test, which is better than the one in your questionnaire. Then ask who owns the company, and ask the company rather than a register, because the register will not answer and the company can.
Ask them in that order and the fourth one is where the meeting gets short.
Written from
Primary The document itself. Claims in this piece rest only on these.
- mistral.ai home page and mistral.ai/sovereign-aiBoth read for this piece, the home page in a browser because its headline animates letter by letter and a plain fetch returns it as scrambled characters. Source for the headline sentence quoted here, for the browser title 'Mistral | #1 in Sovereign AI: Frontier Open Models You Own', for 'Mistral lets you decide how AI works in your organization', for the public-sector claim about NATO and twenty-plus national government entities, and for the Sovereign AI page's definition, its four layers of control with their one-line definitions, its five-step path and its dependency test, all of which are quoted or closely paraphrased in the body. Also the source for two negatives the body rests on, and they are negatives rather than silences I am inferring: the page uses the word jurisdictional once, about the boundary a customer's workload needs, and nowhere mentions applicable law, courts, shareholders, ownership of Mistral or its corporate structure. If the page changes, that is the part to recheck.
- Trust Center, SubprocessorsRead in full, all twenty-five entries, in a browser: the table renders client-side and a plain fetch of the URL returns the page title and nothing else. Source for every sub-processor named in the body with its stated activity, locations and products — Microsoft Inc. for cloud infrastructure in Sweden and Norway, Google LLC for the Netherlands, Belgium and the United States for the US API endpoint, Mistral Compute in France for all products, CoreWeave Inc. as inference provider in the EEA, Cloudflare Inc. worldwide for routing, CrowdStrike Inc. in the EEA and the United States for security — and for the entry 'Mistral AI Affiliates', which is what sent this desk to the affiliate list. One limitation and it is the body's point: the page carries no version number and no last-updated date, so a customer has nothing to compare against the list that was current when they signed.
- Mistral AI Affiliates, effective 28 July 2026Read in full. Thirty entities with registration numbers. Source for the count, for the jurisdictions listed in the body, for Mistral AI, SAS under 952 418 325, for Mistral AI Inc. in the USA under 990657949, for the fourteen French companies named Mistral Compute 1 to 14, for Mistral Compute Holding and for Mistral AI Reserved. What the page does not give: addresses, legal forms for the Mistral Compute vehicles, or any ownership relation between the entities. It is a list of names and numbers. This desk did not look up a single one of them in the French register, which is a check that costs an afternoon and would tell you more than this paragraph does.
- Commercial Terms of Service, effective 25 September 2026, sections 1.1 to 1.3, 14.2 and 14.10Read in a browser and the operative text extracted rather than summarised, because the governing-law clause is the one claim in this piece that a reader might act on the same week. Quoted verbatim from 14.10: California law and the federal or state courts of Santa Clara County for a customer headquartered in the Americas Region, which the document sets in capitals; the laws of the Republic of Singapore and its courts for the APAC Region; and for everyone else 'the laws of France' with 'the courts of Paris, France' having exclusive jurisdiction. The preamble is the source for the contracting entity, its form, its registration number, its address at 15 rue des Halles, and for 'or its affiliate as specified in an Order Form'. Section 14.2 is the source for subcontracting and assignment to an affiliate without the customer's prior written consent, and for Mistral remaining responsible for the acts and omissions of the third party. The Data Processing Addendum was not read: the path tried returned 404, and nothing in the body rests on it. Transfer mechanisms in the body come from the help-centre article below instead, which is a weaker document for that purpose, and the body says so.
- Where do you store my data or my Organization's data?, 12 August 2026Read in full. Source for EU hosting as the default, for the US API endpoint being used only where the customer explicitly selects it, for temporary transfers outside the European Union depending on the feature used, for the statement that the Commission's standard contractual clauses are attached to the relevant contracts and non-EU sub-processors reviewed, and for enterprise customers being able to switch the transferring features off at organisation level. A help-centre article is not a contract and is not cited here as one.
- In-region inference, open models, and new European infrastructure for sovereign AI, 11 August 2026Read for this piece. Source for Regional Endpoints and the choice between Europe and the US, for the published caveat that processing occurs in the selected region with limited, safeguarded transfers to sub-processors that may operate outside it, for the sentence that control over where AI runs is only one part of AI sovereignty, and for the compute coalition and the enterprises quoted in it: Amadeus, ASML, Capgemini, Caisse des Dépôts, CMA CGM and Factory. Two things deliberately absent from the body. The one-gigawatt-by-2030 figure is in the page's own summary and in trade coverage rather than in the text this desk read, so it is not printed; and the page does not state what each coalition member committed, so nothing here characterises those commitments beyond the word the page uses.
- Mistral raises €3B to make sovereign, open-weight AI the technology frontierRead in full, and it settles a paragraph of background this desk had only from aggregators. Source for the €3bn Series D, the post-money valuation of more than €21bn, Samsung Electronics as lead, the Scaleup Europe Fund managed by EQT and PSG Equity as co-leads, and the full list of named existing investors reproduced in the body. Also the source for the company's claim to be the only AI company in the world building the full stack, and for the question it says that stack answers: how to use AI without surrendering control over the infrastructure and intelligence loop. The page itself carries no date; 8 September 2026 is the date on Mistral's own news index, which is why the body says September rather than a day.
- Mistral AI raises 1.7B€ to accelerate technological progress with AI, 9 September 2025Read in full. Source for the €1.7bn Series C at a €11.7bn post-money valuation, for ASML Holding NV as lead investor, for the sentence that the round reaffirms the company's independence, and for the named participating existing investors including NVIDIA. The body puts that sentence and that name in the same paragraph and draws no conclusion from the adjacency, because there is none to draw: a chip vendor on a cap table is ordinary and the company said so itself.
- Introducing Mistral 3, 2 December 2025Read for one fact and it is the company's own: Mistral Large 3 was trained from scratch on three thousand of NVIDIA's H200 GPUs, and all the Mistral 3 models were trained on NVIDIA Hopper GPUs. Also the source for the Apache 2.0 release. No claim in this piece about silicon comes from anywhere other than Mistral's own announcement, which is the point of putting it in.
- European AI: a playbook to own it, 7 April 2026Advocacy by an interested party, read as such, and primary only as evidence of what Mistral says. Read at europe.mistral.ai; the PDF at europe.mistral.ai/whitepaper.pdf was not downloaded, which matters because the phrase quoted in the body — deepening its dependency on non-European hyperscalers, attributed to the paper's fourth chapter — reached this desk from the landing page rather than from the document. Check it against the PDF before this runs, and cut the quotation rather than approximate it if the wording differs. The paper's recommendation that EU institutions prefer European AI tools for their internal operations, with exceptions where no viable European alternative exists, is characterised and not quoted.
- Microsoft and Mistral expand strategic partnership to give enterprises and regulated industries frontier AI they can control, 21 July 2026Read in full, and it is Microsoft's document rather than Mistral's, which is why the body attributes the characterisation to Microsoft. Source for the direction of the arrangement, which most summaries of it have backwards: Mistral builds and adds the European GPU capacity and Microsoft is the committed buyer of part of it, for Microsoft's own AI development and its cloud and AI services. Source for the capacity being built on thousands of NVIDIA Vera Rubin GPUs, for the commitment being described as worth billions of dollars with no figure given, for the infrastructure being Europe-based with no country or site named, for the release describing the arrangement as extending Microsoft's Sovereign Cloud approach, and for Brad Smith's sentence about Europe having access to the world's most capable AI without compromising control. The release describes no equity stake and no ownership transfer, and the body says so.
- Nobody reached the top of the EU's sovereignty scale and the Belgian winner came in at the floor, 16 October 2026Read in full, including its sources block, before this piece was drafted. Everything in this piece about the Cloud III award, the Cloud Sovereignty Framework, the five SEAL levels, the four winners, the per-objective minimums and the Proximus consortium's technical environment is his reporting off the Commission's own documents and is not re-reported here. His point that SEAL-3 is shorthand for eight separate minimums is load-bearing for the one paragraph in this piece that touches the rating, and a reader who wants the scale explained should go there rather than take it from a sentence of mine.
- ASML's shareholding in Mistral AI, and the percentages held by any other investorNot established and therefore not printed. ASML's own press release of 9 September 2025 is reported to state a shareholding of approximately eleven per cent on a fully diluted basis and a seat on Mistral's Strategic Committee; asml.com redirects to investor.asml.com, which returned 403 to this desk on three attempts, and the release was not read here. No percentage appears anywhere in the body for any investor, including that one. France publishes no register of a private company's shareholders, which this desk has written about before, so the absence is structural rather than a failure of a morning's work.
- Whether any Mistral Compute vehicle is pledged to a lender, and the reported debt financing behind the compute buildNeither established. The affiliate list gives fourteen numbered French Mistral Compute companies and a holding company and says nothing about security, charges or lenders, and nothing on the site does. Separately, figures in circulation through low-tier aggregators — roughly $830m of debt raised to finance a data-centre build, and around 13,800 NVIDIA chips — were not verified against Mistral, a lender or a named wire, and are not printed. The body's observation is narrow and is about the shape of the structure, not about who financed it.
- No contact was made with Mistral AIRecorded as a limitation of the piece because it is one. No question was put to the company, no comment was sought on the sovereignty framework, the sub-processor list, the affiliate list or the governing-law clause, and nobody at Mistral has been given an opportunity to say that the fourth question has an answer this desk did not find. Everything above comes from documents Mistral publishes, which is both the method and the gap: a company that answers three questions in writing would very likely answer the fourth in a meeting, and this desk did not ask for the meeting.