Cohere and Aleph Alpha signed a definitive business-combination agreement on September 16, moving their April merger plan toward a transatlantic sovereign-AI provider. The deal remains subject to regulatory approval, and Cohere says integration and product details will follow. For operators, this is a vendor-continuity and contract-diligence event, not proof that a unified platform is ready.

Key Takeaways

• The combined company would operate as Cohere, with headquarters in Toronto and Berlin.
• Aleph Alpha’s Heidelberg office would remain a research center.
• The deal is not closed, and customer-level migration details are not public.
• Sovereign-AI claims still require deployment- and contract-specific verification.
• Operator posture: ask sharper vendor questions before renewing or expanding.

What actually changed in the Cohere-Aleph Alpha merger?

The companies announced a planned combination in April. The new step is a signed agreement. According to the companies’ formal announcement, the combined organization would employ more than 1,000 people, retain Heidelberg as a research center, and deepen its partnership with Schwarz Group to deliver sovereign AI through its STACKIT cloud.

That is still a plan. Reuters reported that regulatory approvals remain outstanding. Cohere’s announcement says further integration and product details will come later. It does not provide a unified product map, customer migration schedule, or post-close pricing.

Why does a sovereign-AI merger matter to operators?

The sharp observation is that this merger may reduce dependence on one jurisdiction while increasing dependence on one vendor. A broader Cohere could offer regulated buyers more deployment options and support depth, but consolidation can also change products, contracts, pricing, and exit paths.

“Sovereign AI” does not settle those questions. Buyers still need to verify which legal entity processes data, where inference and support operations run, which subprocessors apply, and whether a model or platform change creates migration work. The Next Web’s account confirms the dual-headquarters plan, but geography alone does not prove that a specific workload meets its contractual residency or regulatory requirements.

For context, AdvancedAI has previously examined how cloud channels can simplify procurement while changing the contract path and why operators must identify the underlying models in enterprise tools.

What should customers ask now?

Ask sharper vendor questions. Existing Cohere and Aleph Alpha customers should request a written change-impact statement covering:

1. contracting entity, DPA, subprocessors, and hosting regions;
2. support ownership, product roadmap, and model-change notifications;
3. pricing, migration assistance, data export, and termination rights.

Prospective buyers should evaluate the offered deployment and agreement, not the combined company’s positioning. Watch next for regulatory approval, a named post-merger product map, customer-specific migration guidance, and generally available STACKIT deployments.

FAQs

Is the Cohere and Aleph Alpha merger closed?

No. The companies signed a definitive business-combination agreement, but the transaction remains subject to regulatory approval. Product integration details have not been released. Buyers should treat this as a pending transaction, not a completed one, and should not assume that a unified platform or migration path exists yet.

What should existing Aleph Alpha customers ask now?

Request a written change-impact statement covering the future contracting entity, DPA and subprocessors, hosting location, support ownership, product roadmap, pricing, and model-change notifications. Also confirm termination and data-export rights in case the post-close product plan no longer fits your deployment or compliance requirements.

Does the merger make Cohere a sovereign-AI provider?

Not automatically for every customer or workload. The companies plan to expand sovereign-AI delivery through STACKIT, but buyers must still verify where inference runs, which entity processes data, what support access crosses borders, and which subprocessors apply under their specific agreement. Sovereignty is an architecture-and-contract property, not just a vendor label.