News analysis · 17 September 2026
Cohere and Aleph Alpha Merger: Revalidate Your Sovereign AI Boundary
By the ELYMENT AI editorial team · Free to read
Cohere and Aleph Alpha signed a definitive business combination agreement on 16 September 2026, creating a planned transatlantic enterprise AI company operating under the Cohere name. The deal still requires regulatory approval. For customers, the important question is not whether the combined supplier uses the phrase sovereign AI. It is whether each deployed workload retains its promised data location, administrator boundary, support path, legal exposure, update control and exit route after the organisations and products are integrated.
What the companies signed on 16 September
Cohere said the agreement formalises the planned combination first announced in April. The unified company is expected to operate globally as Cohere, with headquarters in Toronto and Berlin, while Aleph Alpha's Heidelberg office remains a research centre. Cohere said the transaction would take combined headcount above 1,000 and remains subject to final regulatory approvals.
The companies describe the result as the first transatlantic sovereign AI solution. Cohere says the structure will include safeguards and oversight for Canadian and German requirements, and that the business will deepen its partnership with Schwarz Group companies to deliver AI through STACKIT's sovereign cloud service.
Reuters reported that the combination was valued at about US$20 billion when first disclosed. It also reported a €500 million Schwarz Group investment and plans for substantial German data-centre capacity. Those figures describe the transaction and infrastructure programme; they do not by themselves prove the control boundary of any customer's workload.
Sovereignty is a property of a workload, not a headquarters
A supplier can have local offices, local leadership and local compute while a production workload still depends on remote administrators, foreign support teams, cross-border telemetry, external model services or contract rights governed elsewhere. The company name and data-centre address are useful facts, but neither is a complete operating boundary.
A merger can also move that boundary without changing the customer-facing product. Identity systems may consolidate, incident response may be centralised, model updates may come from a different engineering organisation and subprocessors may change. Regulated buyers should therefore treat the combination as a change-control event, even when existing services continue normally.
Build a before-and-after sovereignty map
For every consequential AI workload, record the current state and the promised post-integration state across six tests:
- Data: where prompts, outputs, embeddings, logs, backups and fine-tuned artefacts are stored and processed.
- Control: which legal entities and named roles can administer infrastructure, models, keys and customer content.
- Operations: where support, monitoring, incident response and model-update decisions occur.
- Dependencies: which cloud, model, identity, security and telemetry providers remain outside the combined company.
- Evidence: which logs, audit reports, architecture records and contractual notices prove the boundary in operation.
- Exit: how models, data, prompts, evaluations and workflow logic can be exported, migrated and deleted on a tested timetable.
Revalidate before expanding the dependency
Cohere currently offers customer-managed private cloud and on-premises deployment options. Its private-deployment materials say prompts, outputs and fine-tuned models can stay within the customer's environment, with no Cohere access to processed data. Buyers should convert those product statements into environment-specific acceptance tests rather than assume every combined-company service inherits the same properties.
Ask for a dated integration notice, post-close architecture, subprocessor list, administrator-access model, support-region map, key-management design, model-update process and tested exit procedure. Re-run residency and access tests after material platform migrations, not only at renewal.
ELYMENT AI helps organisations turn supplier promises into operational evidence, approvals and repeatable verification. The commercial opportunity in a larger transatlantic provider may be significant. The safe decision is to expand only when the sovereignty boundary can be demonstrated for the exact workload being purchased.
Sources
- Cohere, Cohere and Aleph Alpha sign agreement (16 September 2026) - Primary announcement covering the definitive agreement, planned operating structure, leadership, regulatory status and sovereignty claims.
- Reuters, Cohere and Aleph Alpha combine (16 September 2026) - Independent reporting on the agreement, transaction value, investment, leadership, infrastructure and company financial context.
- Cohere, Private deployments (17 September 2026) - Current product documentation for customer-managed private cloud, on-premises, Model Vault and data-control claims.
Continue learning
Frequently asked questions
Have Cohere and Aleph Alpha completed their merger?
No. They signed a definitive business combination agreement on 16 September 2026, but the transaction remains subject to final regulatory approvals and is expected to close later in 2026.
What will the combined company be called?
The companies say it will operate globally as Cohere, with planned headquarters in Toronto and Berlin and Aleph Alpha's Heidelberg office retained as a research centre.
How should an enterprise verify a sovereign AI claim after the merger?
Map the exact workload's data locations, administrator access, operational teams, external dependencies, audit evidence and tested exit path before and after integration.