Aleph Alpha and Cohere: What the Merger Means for Access to Sovereign Models—and What Still Needs Verification

Introduction: Why the Aleph Alpha–Cohere merger matters for sovereign enterprise AI

The planned combination of Aleph Alpha and Cohere is a significant structural development in enterprise AI, particularly for organisations that need control over sensitive data and the systems used to process it. The companies have announced a transatlantic business combination intended to bring together Aleph Alpha’s research and public-sector relationships with Cohere’s global reach and deployment capabilities. That stated ambition is not, by itself, evidence that products, infrastructure, or customer arrangements have already changed.

For European IT and compliance teams, the immediate questions are operational: will existing services remain available, will licences or terms of use change, and where will customer data be processed and governed? The available evidence confirms that a definitive agreement was signed, but the transaction remains subject to regulatory approvals. It does not establish that access, licensing, or product integration has changed. This analysis separates what has been announced from what customers still need to confirm directly.

Confirmed facts: what is known about the transaction and its participants

On 24 April 2026, Cohere and Aleph Alpha announced a plan to join forces. On 16 September 2026, they announced that they had signed a definitive business combination agreement. The transaction is still subject to final regulatory approvals; the announcement said it was expected to close later in 2026. The agreement’s signing is confirmed by the companies’ announcements, but the evidence available here does not confirm that the transaction has closed.

The announced plan is for the combined company to operate globally as Cohere, with headquarters planned in Toronto and Berlin and Aleph Alpha’s Heidelberg office retained as a research centre. Ilhan Scheer, then Aleph Alpha’s co-CEO, is due to become Cohere’s chief operating officer, while Aleph Alpha co-founder Samuel Weinbach is due to become Cohere’s chief research officer. Both appointments are conditional on completion of the transaction. Companies of Schwarz Group announced a commitment of €500 million in structured financing in connection with the planned combination. These are announced intentions and commitments, not evidence that the transaction or its operational integration is complete.

Model availability, access channels, and licences: what the evidence does—and does not—show

Aleph Alpha’s current corporate website presents Kolibri as a sovereign large language model and describes access as available live or through an API. That establishes how the company’s website describes the product at the time represented in the available evidence. It does not establish that the merger has changed Kolibri’s availability, access methods, licence, or terms of service. Nor does the evidence identify an inventory of Aleph Alpha or Cohere models that will be affected by the transaction.

The announced combination is intended to bring together Aleph Alpha’s research expertise and Cohere’s reach and deployment capabilities. But the companies have not provided, in the evidence available here, specific integration plans for individual models, a revised product catalogue, or updated licensing terms. Customers should therefore avoid assuming either that existing terms will remain unchanged after closing or that they will automatically change. The status of each model and service must be checked against the applicable contract and current provider documentation.

Cohere’s announcement describes deployment flexibility across cloud, private on-premises, and air-gapped environments. That is a company-level description of its offering; it does not establish which deployment options will be available for each model, in each jurisdiction, or under the combined company. Likewise, no evidence here confirms that a Cohere model will replace an Aleph Alpha model, that Kolibri will be withdrawn, or that either company’s licences will be transferred or amended as a result of the transaction.

Regulatory and data-sovereignty implications for European customers

The companies say the combined business will operate within the applicable legal and regulatory frameworks in Canada and Germany, including rules concerning the protection and handling of sensitive data and technology. They also describe safeguards and oversight mechanisms intended to support operational control, accountability, and compliance. These are commitments stated in the announcement; they do not, on their own, establish how a particular customer’s data will be hosted, accessed, transferred, or governed in practice.

For EU customers, a transatlantic corporate structure does not remove the need to assess the specific service and deployment. A customer should establish which legal entity provides the service, which entity acts as controller or processor where relevant, where data and backups are stored, who can access them, and whether support or administration involves transfers or remote access across jurisdictions. The announcement does not provide customer-specific data-residency terms, technical architecture, or a complete account of how EU requirements will be implemented for each product.

A sovereignty assessment should therefore distinguish corporate location and public commitments from verifiable controls. The existence of headquarters in Canada and Germany, or a stated intention to align with both countries’ rules, is not sufficient evidence of EU data residency, exclusive local administration, or a particular technical isolation model. Customers need the applicable contract, data-processing agreement, security documentation, and deployment-specific details before concluding that a workload meets their requirements.

Customer checklist: verify licences, access channels, and model policies

Because detailed product-integration arrangements have not yet been published in the evidence available here, customers should seek written answers from the provider before making procurement or architecture decisions. Ask about the specific model, account, deployment, and contract in question; general assurances about a future combined offering do not resolve customer-specific obligations.

Keep the response alongside the current service terms and technical documentation, noting the date and version of each. If the provider’s answers are preliminary, record what remains conditional on regulatory approval or closing, and request an updated confirmation after those milestones. This approach helps teams distinguish current contractual rights from planned future capabilities.

Limits of the evidence: what remains unverified

The definitive agreement has been announced, but the available evidence does not confirm completion of the transaction. The companies have said that further integration and product details will follow. There are no model-specific licence documents, revised terms of service, technical migration plans, or complete model inventories in the evidence available here. As a result, claims about how Aleph Alpha models will be integrated into Cohere’s platform, whether Kolibri’s access or licensing will change, and which products will continue after closing remain unverified.

The companies’ description of the future business as a transatlantic sovereign AI solution is a strategic claim about an intended offering, not independent proof that every service will meet a particular customer’s sovereignty requirements. Similarly, the announced plans for dual headquarters, a Heidelberg research centre, safeguards, and a STACKIT partnership do not by themselves demonstrate where a specific customer’s data will reside or who can access it. Customers should wait for applicable regulatory approvals and rely on current, service-specific contractual and technical documentation when assessing compliance.

The most defensible conclusion is limited but useful: the companies have signed a definitive agreement that remains subject to regulatory approval; Aleph Alpha’s website describes Kolibri as available live or through an API; and the evidence provided does not show merger-driven changes to models, licences, access channels, or data-residency guarantees. Those questions require confirmation from the providers for each affected service and customer.

Keep exploring

Corrections and transparency

If you spot incorrect or outdated information, send us a correction with the page and source we should review.