Five European companies just agreed to buy AI compute that doesn’t exist yet

Mistral AI, the French AI company that built its reputation releasing open-weight models, wants companies to use its infrastructure even when they pick a model other than Mistral.

The company said Tuesday that it will begin hosting third-party open models, starting with GLM-5.2 from China’s Z.ai. The model will run on the same infrastructure as Mistral’s own models, with access to its regional processing controls and new priority service tier.

The company wants to give enterprises one place to run different open models, without forcing them to start over every time they switch.

Mistral’s regional endpoints are now largely available in Europe and the United States. Its Priority Tier, which puts eligible requests ahead of standard traffic and comes with a 99.5% uptime service-level agreement, is in public preview.

The company wants to give enterprises one place to run different open models, without forcing them to start over every time they switch.

Third-party models, same pipes

The first is GLM-5.2, a model from Z.ai with a 1 million-token context window. Mistral lists coding and long-context agentic work among its main uses. GLM-5.2 is available through the company’s API as zai-glm-5-2 and costs $1.40 per million input tokens, $4.40 per million output tokens, and $0.14 per million cached input tokens.

A team might use GLM-5.2 for coding, Mistral Medium for work involving images and text, and Small for cheaper, everyday requests. Using the same API doesn’t make the models interchangeable. Each model has its own quirks, so teams will still need to test it before putting it into production.

And while GLM-5.2 has open weights, using it through Mistral is still a hosted service. Mistral decides which version is available and runs the infrastructure behind it.

Each model has its own quirks, so teams will still need to test it before putting it into production.

Regional boundaries have gaps

With Mistral’s regional inference service, developers can decide whether their requests are processed in Europe or the United States by changing the API endpoint. The regular endpoint comes without that guarantee. Mistral says keeping inference closer to users could reduce latency and help companies meet data-location requirements, although it adds 10% to the cost of every input, output and cached token.

Mistral says some account and usage data may still leave the selected region. Information may also be shared with outside companies under the safeguards in its Trust Center.

Companies working with financial, health or government data will still have some homework to do. The prompts may stay in Europe, but teams also need to find out what Mistral logs, where that information is stored, who can see it, and what gets through to outside companies. The Microsoft-Mistral sovereign compute partnership addresses some of these questions for Azure customers, but teams running workloads directly on Mistral’s own endpoints face a different set of guarantees.

The regional endpoints don’t support everything yet and, depending on the region, some models are missing. Developers can use function calling, but not Agents, Batch or the Files API. That indicates moving an existing application to the EU endpoint may take more than swapping out the base URL. If the application depends on an unsupported feature, Mistral’s regional processing guarantee no longer covers the workload.

Priority isn’t always guaranteed

Mistral’s Priority Tier puts eligible API calls into a queue ahead of Standard Tier requests when infrastructure is busy. Customers must arrange access with Mistral and agree on custom limits for each model. Once that is set up, developers can add service tier: auto to a completion request. Leave the field out, and the request goes through Standard Tier.

A request only gets prioritized when the organization has an active entitlement, the selected model is covered, the request falls inside its custom rate limit, and Mistral has capacity for that model in that region. Miss one of those conditions and the request can drop to Standard Tier.

Mistral includes the tier that served the request in the response’s usage object. Developers can record that field to find out how often requests are being downgraded, rather than assuming every call marked auto received priority treatment. If latency suddenly climbs, the team needs to know whether the model slowed down or requests quietly fell back to the standard queue.

Compute commitments without specific

The company is gathering a group of European businesses and institutions willing to make multi-year compute commitments. ASML, Amadeus, Capgemini, Caisse des Dépôts and CMA CGM were named in the announcement, but the company didn’t say how much capacity any of them committed to buy. Mistral calls the resulting allocations European Compute Units, or ECUs. Customers will be able to apply those units across Mistral Compute products as their needs change.

For customers, it is a bet made years in advance. They may know they will need AI compute, but not which models they will use, how large those models will be, or whether the workload will be inference, fine-tuning or something that has not been productized yet. Letting ECUs move across Mistral’s products is supposed to leave room for that uncertainty.

Mistral has not said how much compute an ECU buys, what it will cost, whether customers can carry over unused capacity or what happens if the infrastructure is not ready on time. But it’s clear that Mistral needs customers to keep using its infrastructure, whichever model they choose. That same bet — that the infrastructure layer matters more than any single model — is one that a number of enterprises are already making. GLM-5.2 is the first sign of how that could work.

Mistral needs customers to keep using its infrastructure, whichever model they choose.

The post Five European companies just agreed to buy AI compute that doesn’t exist yet appeared first on The New Stack.