Short answer: On September 16, 2026, Cohere and Aleph Alpha announced that they had signed a definitive business combination agreement. The proposed combination would operate globally as Cohere, retain substantial Canada and Germany operations, and pursue a sovereign AI offering connected to Schwarz Digits’ STACKIT cloud. It is a corporate transaction and delivery roadmap—not a newly released model, public API, or generally available customer product.
The transaction remains subject to final regulatory approvals and is expected to close later in 2026, according to the announcement. Further integration and product details are still to come. For an enterprise buyer, the useful question is therefore not “is this sovereign AI?” but “which sovereignty controls will be contractual, technically verifiable and available for my workload, and which are still plans?”
This guide separates the announcement from current Cohere and Aleph Alpha product surfaces, then gives you a procurement checklist for jurisdiction, model control, deployment, data handling, operations and exit risk.
What was signed on September 16
Cohere’s announcement describes a definitive business combination agreement with Aleph Alpha GmbH, following the companies’ April announcement of a planned combination. The public release identifies Cohere Inc. and Aleph Alpha GmbH as the parties and says the unified company would operate under the Cohere name. The transaction is not complete: regulatory approvals remain outstanding, and the companies say they expect closing later this year.
| Announcement detail | What it means now | What it does not prove |
|---|---|---|
| Definitive business combination agreement | A signed transaction framework announced by the companies. | That the merger has closed or that customer contracts have already changed. |
| Operating globally as Cohere | The proposed post-close brand and operating identity. | A new live product catalogue or a new API endpoint. |
| Toronto and Berlin plans, with Aleph Alpha’s Heidelberg office as a research centre | Planned operating footprint across Canada and Germany. | A guarantee that every request, support action or control-plane record stays in either country. |
| Ilhan Scheer as COO and Samuel Weinbach as CRO | Leadership appointments described as effective upon deal close. | Current authority or completed organizational integration. |
| €500 million structured financing from Schwarz Group | Strategic financing and infrastructure alignment around the proposed combination. | A customer price, capacity reservation or procurement commitment. |
| Further integration and product details to follow | The combined roadmap is not fully specified publicly. | Immediate interoperability between all existing products. |
The “first transatlantic sovereign AI solution” description is the companies’ positioning. It is a meaningful strategic ambition, but it is not a certification, a standardised legal category or a complete technical specification.
Which products and capabilities exist today
The transaction brings together two different kinds of enterprise assets. Cohere supplies foundation models and managed or private deployment options. Aleph Alpha has focused on specialised language models and the PhariaAI application stack for public-sector and regulated workflows. The September 16 announcement does not state that one product is being replaced by another.
| Existing surface | Current documented role | Safe procurement question |
|---|---|---|
| Cohere Command models | Generative model family exposed through Cohere’s platform and deployment channels. | Which exact model, licence, region, provider and support tier would be contracted? |
| Cohere North | Enterprise workplace system with agents, search and workflow capabilities; Cohere lists custom enterprise pricing. | Where do the application, control plane, connectors, prompts and outputs run? |
| Cohere Compass | Search and discovery system with connectors, indexing, parsing and retrieval; Cohere lists custom enterprise pricing. | What data is indexed, retained, exported or reprocessed? |
| Cohere Model Vault | Cohere-managed, single-tenant inference with model selection, performance tiers, scaling and monitoring. | Is the required model available in the selected vault type and region? |
| Cohere Encrypted Vault | Model Vault option with confidential computing, end-to-end encryption and client-side remote-attestation checks. | Can the application verify the attested environment on every connection, and is the required GPU available? |
| Cohere Private Deployments | Customer-managed deployment on premises or in a customer VPC, with Cohere guidance and support. | Who owns hardware, patching, drivers, monitoring, incident response and upgrades? |
| Aleph Alpha PhariaAI | Specialised language-model and application stack described for sovereign European enterprise and public-sector work. | Which PhariaAI components, model, region and operating responsibilities are included after close? |
| STACKIT route | The agreement says the combined company will advance a sovereign offering with Schwarz Group on STACKIT. | Is there a named, orderable service, supported model, region, SLA and date? |
Aleph Alpha’s current public materials describe PhariaAI as a stack that can connect domain knowledge with operational workflows. Its PhariaFiles updates describe user-level access management in PhariaStudio and dynamic model management through PhariaOS. Those pages are useful evidence of the existing product direction, not proof of what the post-close combined catalogue will contain.
Sovereignty is a stack of controls, not a country label
The announcement puts Canada and Germany at the centre of the proposed company. That helps establish where headquarters, research and leadership are intended to sit. It does not by itself answer every question a regulator, security team or procurement group will ask. A sovereign deployment can still have separate locations for inference, storage, support, telemetry, key management and subprocessors.
| Control layer | Question to answer | Evidence to request |
|---|---|---|
| Legal and ownership | Which legal entity signs the contract, controls the service and can change the terms? | Contracting entity, governing law, ownership/change-of-control notice and regulatory conditions. |
| Model and intellectual property | Who owns the weights, fine-tunes, evaluation data, prompts, adapters and generated artefacts? | Model card, licence, usage rights, training opt-out, customisation terms and exit rights. |
| Inference and storage | Where are requests, responses, embeddings, files, logs and backups processed? | Region matrix, data-flow diagram, subprocessor list, storage/backup locations and route evidence. |
| Operator access | Can provider staff, cloud operators or support teams access plaintext or administration paths? | Access-control design, key ownership, privileged-access logs, support procedure and audit evidence. |
| Control plane | Where are identity, billing, telemetry, model configuration and policy records kept? | Control-plane residency, retention schedules, export/deletion process and incident notification. |
| Operational resilience | Who patches the stack, supplies capacity and handles an outage or model change? | SLA, support boundary, RTO/RPO, capacity terms, deprecation notice and rollback plan. |
| Exit and portability | Can the application move to another model, cloud or operator without rebuilding everything? | API compatibility, export formats, model and prompt portability, notice periods and transition assistance. |
This is why the April and September announcements should be read as strategic direction. The planned Canadian-German footprint may be valuable, but “sovereign” should not be used as a substitute for a route, retention setting or contract clause.
Deployment choices you can verify now
Managed Cohere API
Cohere’s current installation documentation presents a public SaaS platform, Model Vault, private deployments and cloud-provider deployments as separate ways to use its models. A standard managed API may be the fastest baseline, but your team must still verify model version, request routing, retention, training use, rate limits, support and the applicable legal entity. A trial API key is not a production approval: Cohere’s pricing page says trial keys are rate-limited and not permitted for production or commercial purposes.
Model Vault
Cohere documents Model Vault as a Cohere-managed, dedicated, single-tenant inference environment. The documentation describes configurable replicas, performance tiers, monitoring and API access. Its standard and encrypted variants have different security properties. Cohere says the encrypted option keeps prompts and responses protected in use inside hardware-backed trusted execution environments and uses an OHTTP proxy to verify attestation before sending requests.
That is a concrete control design, but it is still product-specific. The docs say supported models and GPU availability differ by vault type, and generative models may require a waitlist. Region selection and available capacity need confirmation for the exact model and workload.
Private cloud or on-premises
Cohere’s private-deployment documentation says the customer manages the deployment infrastructure, including hardware, drivers and prerequisites, while Cohere provides guidance and support. On premises, the customer procures the servers and GPUs; in a VPC, the customer controls the cloud environment and how data is stored and processed. This can reduce exposure outside the environment, but it increases operational ownership. Ask who patches the container, validates model artefacts, monitors abuse, handles incidents and supports a rollback.
PhariaAI and the prospective STACKIT offering
Aleph Alpha’s homepage describes specialised models running on European infrastructure and says its teams co-build solutions with customers. Its published PhariaAI updates describe application access controls, model management and workflow integration. The September 16 Cohere announcement says the companies will advance a sovereign offering with Schwarz Group on STACKIT, but it does not provide a customer-facing product name, model list, endpoint, availability date or SLA.
Until those details are published, treat STACKIT as a planned deployment route. Do not infer that every existing Cohere model, PhariaAI component or customer contract will automatically be available there.
Security and data-residency claims: turn them into tests
Cohere’s security materials describe configurable data handling and retention, private deployments, a SOC 2 Type II API and annual third-party audits and penetration tests. Its encrypted-vault documentation describes hardware-backed confidential computing, zero-data-retention operation when enabled, and signed attestation evidence. These are specific vendor-described controls, not a universal property of every Cohere product or future combined service.
Aleph Alpha’s public company material says its models run on European infrastructure and are built for EU-regulated environments. That is a vendor statement about the platform direction. Request current, workload-specific proof rather than assuming that a German research centre, a Canadian headquarters or a European cloud name determines every data path.
- Draw the complete request path: client, gateway, model endpoint, retrieval store, tool system, logs, backups and support channel.
- Record physical processing and storage regions separately from the location of the contracting entity.
- Ask whether customer prompts, outputs, files, traces or feedback are used for training, product improvement or abuse monitoring, and what opt-out applies.
- Require the subprocessor list, privileged-access process, key-management model and deletion/export procedure.
- For an encrypted vault, verify the client-side attestation result and retain the signed evidence with the request record.
- Test an incident: identify who can suspend the workload, rotate keys, export data, restore service and communicate the breach.
Access, procurement and pricing boundaries
The September 16 agreement does not announce a new customer signup, model release or general-availability date. Existing Cohere products remain governed by their own access and commercial surfaces. The public pricing page lists custom enterprise pricing for North and Compass, and sample Model Vault rates for specific Embed, Rerank and Parse tiers. It says production API access uses a production key and pay-as-you-go billing, while private deployment and model customisation use custom pricing.
| Commercial question | What is public | What procurement must obtain |
|---|---|---|
| Combined-company price | No customer price is stated in the agreement. | Quote naming the legal entity, service, model, region, capacity, currency, taxes and renewal terms. |
| Model Vault | Public examples include $4–$10 per instance-hour and $2,500–$6,500 per instance-month for selected retrieval/parsing models. | Exact model, tier, region, minimum commitment, autoscaling, support and overage terms. |
| North or Compass | Custom enterprise pricing. | Seat/usage basis, connectors, data retention, implementation and exit fees. |
| Private deployment | Custom enterprise engagement with customer-managed infrastructure. | Container licence, model list, GPU requirements, updates, support, security responsibilities and transfer rights. |
| STACKIT offering | Strategic offering described; no public SKU or date in the announcement. | Availability, region, service level, model support, data path and contract owner before budgeting. |
The €500 million structured financing mentioned by Cohere is not a customer budget, a token price or a capacity guarantee. It is part of the proposed company’s financing and strategic infrastructure story.
How this differs from the other same-day Cohere partnership
Cohere’s same-day OpenText announcement is a partner integration story aimed at trusted agentic AI for governments and regulated industries. The Aleph Alpha item is different: it is a proposed business combination that changes ownership, leadership, research footprint and the planned sovereign delivery stack. The two announcements can belong to the same sovereign-AI cluster, but they answer different questions. A buyer evaluating OpenText integration needs data/connectors and agent workflow evidence; a buyer evaluating the Aleph Alpha transaction needs governance, jurisdiction, product-continuity and exit evidence.
The existing Mistral sovereign-AI buyer checklist is a useful comparison for separating funding, inference geography and retention. For current Cohere product-specific questions, see the North Small Translate access guide and the Cohere Parse access guide.
A procurement checklist for the proposed combined company
Use this sequence before signing a new multi-year commitment or migrating a regulated workflow:
- Freeze the transaction state: record that the agreement is signed but not closed, approvals are pending and product integration details are future work.
- Name the service: write the exact Cohere or Aleph Alpha product, model version, API/endpoint and deployment mode. Do not contract against “the combined platform.”
- Map the sovereignty requirement: decide whether you need Canadian or EU legal control, EU-only processing, customer-owned infrastructure, open weights, confidential computing, or a combination.
- Trace every data path: include prompts, outputs, embeddings, files, retrieval stores, logs, traces, backups, support sessions and fallbacks.
- Test access: confirm the organisation can actually order and operate the named model in the target region, with production credentials and required support.
- Set acceptance criteria: measure task accuracy, refusal/approval behaviour, latency, throughput, cost, language fit, auditability and failure recovery on your own redacted cases.
- Contract the controls: attach region, retention, training-use, subprocessor, audit, incident, SLA, model-change and change-of-control clauses.
- Design the exit: maintain an alternative model, exportable prompts/configuration, portable retrieval data, a rollback path and a realistic transition window.
What current coverage and community signals add
Current search results are dominated by Cohere’s September 16 announcement, the April Cohere announcement, the PR Newswire copy and Reuters reporting. TechCrunch’s April analysis frames the deal as Cohere taking over Aleph Alpha and highlights the STACKIT and sovereignty questions. Reuters’ September 16 report confirms the definitive agreement, pending approvals, dual Toronto/Berlin plans, Heidelberg research and Schwarz Group’s computing role. These sources improve transaction context but do not provide a new product SKU or independently validate the companies’ sovereignty claims.
Community discussion raises the right unresolved questions—whether the deal is really an acquisition, how Canadian and German control will be preserved, and whether rented chip or cloud dependencies complicate “sovereignty.” Those comments are signals, not deployment evidence. No first-hand public test of the proposed combined service was found.
FAQ
Has Cohere already acquired Aleph Alpha?
Not on the evidence reviewed. The companies announced a definitive business combination agreement on September 16, 2026, but said final regulatory approvals remain and the transaction is expected to close later this year.
Is this a new Cohere model or API?
No. The announcement describes a corporate combination and sovereign-AI roadmap. It does not name a new model checkpoint, API, endpoint, access programme or general-availability date.
Does Canada-Germany ownership make a deployment sovereign?
Not by itself. Ownership and headquarters are one layer. You still need to verify processing geography, storage, operator access, control-plane location, model rights, support, subprocessors and exit terms.
Is STACKIT available as the new combined service?
The companies describe a sovereign offering connected to Schwarz Group’s STACKIT, but the announcement does not give a public service name, model list, endpoint, date or SLA. Treat it as a planned route until those details are published or provided in a contract.
Should existing Cohere customers change products now?
Not because of this announcement alone. Continue to evaluate the exact product and contract you already use, ask for a continuity and change-of-control plan, and request written details before relying on a future combined catalogue.
Bottom line
The Cohere–Aleph Alpha agreement could combine Cohere’s model and deployment scale with Aleph Alpha’s European enterprise and public-sector relationships, while anchoring a proposed offering across Canada, Germany and STACKIT. That is strategically important. It is not yet a completed transaction or a ready-made sovereignty guarantee.
For procurement, freeze the current product and legal state, map sovereignty across all seven control layers, and require technical and contractual evidence for the exact workload. Buy the service you can verify today; treat the post-close product story, new integration and STACKIT route as roadmap items until they become named, testable and contractually defined.
Sources checked
- Cohere: Cohere and Aleph Alpha sign agreement to become the first transatlantic sovereign AI solution (September 16, 2026).
- PR Newswire release provided by Cohere (September 16, 2026).
- Cohere’s April planned-combination announcement (April 24, 2026).
- Cohere newsroom, including the same-day OpenText partnership listing.
- Cohere Model Vault documentation, Encrypted Vault documentation, Private Deployment overview and Cohere pricing.
- Cohere security and data-protection overview.
- Aleph Alpha company and PhariaAI overview and PhariaFiles access/deployment update.
- Reuters reporting republished by MarketScreener (September 16, 2026).
- TechCrunch analysis (April 25, 2026) and Barhum.ai’s on-prem buyer comparison (July 12, 2026), used for context rather than primary proof.
- Reddit discussion and Mistral sovereignty discussion, used only as low-signal community questions.
