Cohere vs Augure: where each one actually runs your data

Two Canadian companies sell AI to Canadian organizations, and they answer the question "where does this actually run" in almost opposite ways. One sells models that a customer deploys. The other sells inference it runs itself, at a per-seat price. The distinction matters more than the shared nationality, and it is the thing most comparisons skip.

By a wide margin, Cohere is the larger and better known of the two. Founded in Toronto in 2019 by Aidan Gomez, Nick Frosst and Ivan Zhang, it has raised roughly US$1.6 billion, most recently US$500 million at a US$6.8 billion valuation in a round led by Radical Ventures and Inovia Capital. Canadian institutions including PSP Investments, the Healthcare of Ontario Pension Plan and BDC are on the register, alongside Nvidia, AMD, Oracle, Salesforce and Cisco.

Augure operates at a fraction of that size. It sells a chat and document platform to Canadian professional teams, priced at C$20 per seat per month with a free tier, and runs the inference behind it rather than shipping weights for someone else to host.

Four paths, four different answers

Four ways to consume the models appear in Cohere's published deployment documentation, and residency lands differently on each.

One is Cohere's own hosted platform, described in its docs as the fastest way to start. A second is through cloud AI services: Amazon Bedrock and SageMaker, Azure AI Foundry, and Oracle's generative AI service. On that path the processing region is whichever one the customer selects inside that provider, and all three providers are American companies. A third is a private deployment inside the customer's own virtual private cloud. A fourth is on-premises, including air-gapped environments physically isolated from outside networks. On the last two, Cohere's documentation is explicit that prompts, outputs and fine-tuned models stay inside the customer's environment and Cohere has no access to them.

That last pair is a strong residency answer, and it is worth saying so directly. It is also an infrastructure project. Someone has to provision the environment, operate it, and pay for capacity sized to the workload. For a bank or a federal department with a platform team, that is routine. For a twelve-person firm, it is not a thing that happens this quarter, or possibly ever.

On its own security page, Cohere states its API platform is hosted on "industry-leading cloud infrastructure" and is SOC 2 Type II compliant, and directs readers to its trust centre and privacy policy for specifics. It does not name a processing region for the hosted platform on that page.

What is being built, and when

Canadian infrastructure is coming, and it is genuinely under construction.

In June 2026, Bell, Cohere, Hypertec and BUZZ HPC announced a three-year US$220 million agreement to stand up an AI compute cluster built around 2,304 Nvidia Grace Blackwell GPUs in Bell's data centre in Merritt, British Columbia, on hardware assembled in Canada by Hypertec. It is scheduled to go live in late 2026 to early 2027. Separately, Cohere received $240 million in federal funding toward a $725 million data centre in Cambridge, Ontario.

Both are substantial commitments to domestic capacity, and Canadian AI is better off for them existing. Both are also dated. An organization signing a contract this month is buying what runs today, not what is scheduled for next year.

One wrinkle on the Cambridge facility has been picked up by Canadian press. Writing in The Walrus in November 2025, under the headline "Cohere Is Canada's Biggest AI Hope. Why Is It So American?", Julie Sobowale noted that the federally supported data centre is being built with CoreWeave, a US AI infrastructure company, on the reasoning that no Canadian operator had equivalent access to Nvidia hardware. That piece also flagged Cohere's commercial relationship with Palantir, the US analytics company known for its work with American military and intelligence agencies.

Neither fact makes Cohere less Canadian, and the article does not claim it does. They are the kind of detail a procurement reviewer should weigh rather than discover afterwards.

A vendor's nationality is a fact about the company. Residency is a fact about the request.

Priced by token, or priced by seat

Commercial shape separates these two as cleanly as architecture does.

Cohere meters by token through its API and through the cloud marketplaces it sells on, with enterprise and private-deployment terms negotiated rather than published. That is the normal model for a foundation-model vendor, and it is well suited to an organization embedding AI in its own product, where usage is a function of traffic and someone on staff can forecast it.

Per-seat pricing is published on the other side: free to start, C$20 per month per person, in Canadian dollars. A finance lead can multiply that by headcount and be done. Nobody has to model token consumption or discover the bill after the fact.

Neither approach is better in the abstract, and a team that outgrows per-seat pricing should move to metered pricing. The relevant question at the point of purchase is which one the buyer can actually budget for, and small organizations are consistently worse at forecasting token spend than vendors assume they will be.

Two buyers

Who signs the cheque separates these two more cleanly than any capability chart.

Enterprise and government is Cohere's motion. Its strongest residency answers require the customer to run infrastructure, and its pricing and contracting assume an organization capable of that. The Bell and Cambridge projects are aimed at the same tier of buyer, plus the public sector.

Augure sells a layer below that: law firms, clinics, municipal offices and professional teams that want AI with Canadian handling and no deployment project. Customer data is stored in Canada, and inference runs on Canadian infrastructure and with vetted EU partners under zero-data-retention agreements, never routed to providers in the United States. Some model tiers run in Canada, others in the EU, and it would be dishonest to describe that as every request being processed on Canadian soil. Limited US processing exists for payment card networks and email delivery, listed in the privacy policy. There is no US parent company and no US investors, so no US-controlled provider handles customer content.

Both directions of that trade are legible. An organization that needs an air-gapped installation on its own metal, or a foundation model to fine-tune and embed in its own product, is describing Cohere's business and not Augure's. An organization that wants to open a laptop on Monday and have Canadian-handled AI working, without provisioning anything, is describing the opposite.

Where the comparison stops being useful

A caveat belongs on any piece like this, and it applies to both companies.

Model quality is not settled by either firm's marketing, including this article's. Cohere's models are used by large enterprises that ran their own evaluations before signing, and any organization with a specific task in mind should do the same rather than take a vendor's word on benchmarks. Published scores are measured on public test sets, and the correlation between those and a given firm's actual documents is weaker than the numbers suggest.

Residency claims deserve the same treatment in both directions. Every assertion in this article about Cohere comes from its own documentation, its June 2026 announcement with Bell, or Canadian press coverage cited above, because those are checkable. Every assertion about Augure comes from its privacy policy and sub-processor list, which are published for the same reason. A reader who takes neither company's word and reads both sets of primary documents will reach a better decision than one who reads either company's comparison page.

The two questions that settle it in writing

Buyers evaluating either company, or any vendor making residency claims, tend to get further with two questions in writing than with any amount of homepage copy.

Whose hardware runs the request, and in which country. And which country's courts can order that company to produce what the request contained. A vendor that answers the first with a head office address has answered a different question, and a vendor that cannot answer the second in a sentence is worth a follow-up.

Cohere publishes more deployment detail than most vendors in this market, which makes it straightforward to ask the first question and get a real answer, provided the buyer knows which of the four paths applies to them. That is the part worth pinning down before signing anything.

Augure's current architecture, model tiers and sub-processor disclosures are published at augureai.ca. Cohere's deployment documentation and trust centre are on its own site, and the Bell announcement and Walrus piece are linked above for anyone who would rather read the primary material than a comparison written by one of the two companies in it.