---
title: "Augure vs Claude: sovereign inference versus regional endpoints"
description: "For Canadian teams comparing Claude for Work or the Anthropic API with Augure: storage, inference, training policy, prices and a chat plus SDK migration guide."
competitor: "Claude for Work and the Anthropic API"
vendor: "Anthropic"
category: "chat"
canonical: "https://augureai.ca/compare/claude"
updated: "2026-10-27"
summary: "Anthropic's first-party API publishes US as its only workspace geo and offers Canadian residency through Amazon Bedrock and Google Vertex AI; Augure stores customer data in Canada, never routes inference to US providers, and offers an OpenAI-compatible API, so the Anthropic SDK is swapped for the OpenAI SDK with a base URL change."
faqs:
  - q: "Is there a Canadian alternative to Claude for Work?"
    a: "Augure is a Canadian company with no US parent or investors. Customer data is stored in Canada, inference runs on Canadian infrastructure and with vetted EU partners under zero-data-retention agreements, and it is never routed to providers in the United States. Chat plans are billed in CAD: Free C$0, Pro C$20 per month, Max C$80 per month, Enterprise custom with SSO."
  - q: "Can Claude keep my data in Canada?"
    a: "Per Anthropic's documentation as of October 2026, the first-party Claude API offers inference_geo values of global and us only, and us is the only workspace geo for data at rest. Anthropic's regional compliance page lists Canada as a regional endpoint on Amazon Bedrock and Google Vertex AI. Augure's Canada-only account setting keeps requests in Canada or fails them with 503 residency_unavailable."
  - q: "Does adding Augure as an MCP server make Claude Code sovereign?"
    a: "No. Augure's MCP server gives Claude Code an ask_augure tool whose calls run on Augure models in Canada and bill your Augure developer account. Claude's own reasoning, context and tool calls still run wherever Anthropic serves them. To run the whole loop on Canadian inference, use Augure Code or point an OpenAI-compatible agent at https://api.augureai.ca/v1."
---

# Augure vs Claude: sovereign inference versus regional endpoints

Claude for Work (Team and Enterprise) and the Anthropic API are Anthropic's products for organisations and developers. Augure is a sovereign AI platform for Canadian organisations: chat, knowledge base, a desktop agent and an OpenAI-compatible API, with customer data stored in Canada. The biggest difference is how residency is delivered. Anthropic's own API publishes US as its only workspace geo and routes Canadian residency through Amazon Bedrock and Google Vertex AI. Augure runs inference on Canadian infrastructure and with vetted EU partners, never US providers. Read this if you are a privacy officer, CTO or developer weighing Claude's model quality against a Canadian residency commitment.

## At a glance

| | Augure | Claude for Work and the Anthropic API |
|---|---|---|
| Company and jurisdiction | Canadian company, no US parent or investors. | Anthropic, a US company. |
| Where customer data is stored | Canada. | Per Anthropic's API documentation (October 2026), `us` is the only available workspace geo for data at rest. The pricing page does not describe a residency option for Team or Enterprise. |
| Where inference runs | Canadian infrastructure (Ontario) and vetted EU partners under zero-data-retention; never US providers. | First-party API: `inference_geo` is `global` (any available geography) or `us` (1.1x price). Canada is listed as a regional endpoint on Amazon Bedrock and Google Vertex AI, not on the Anthropic API. |
| Your data used for training | Never. | Not by default for commercial products; feedback you submit can be used. Consumer plans choose via a Model Improvement setting. |
| Canadian residency option | Storage always in Canada. Accounts can be set Canada-only: requests then stay in Canada or fail with `503 residency_unavailable`, never served elsewhere. tofino-3 and the Augure Open models never leave Canada. | Through Bedrock or Vertex regional endpoints, which Anthropic says keep storage and processing in the chosen region. |
| API | OpenAI-compatible, https://api.augureai.ca/v1 | Messages API at api.anthropic.com, plus an OpenAI SDK compatibility endpoint. |
| Models | ossington-5 (256K), rosedale-1 (up to 1M), tofino-3, Augure Open (GLM-5.3, Qwen3.8-Flash-Next) | Claude Fable 5.1, Opus 5.5, Sonnet 5.5, Haiku 5.5; 1M context and 128K output on all four. |
| Languages | English and Quebec French natively. | Multilingual; no published statement on Quebec French. |
| Billing currency | CAD. | Team $20 per seat annual or $25 monthly, 2 to 150 seats (shown in $, currency not labelled); Enterprise US$20 per seat plus usage at API rates, 20-seat minimum. |
| Certifications published | SOC 2 and ISO 27001 in progress (readiness underway with Vanta, per https://augureai.ca/security). TLS 1.3 in transit, AES-256 at rest. | SOC 2 Type I and II, ISO 27001:2022, ISO/IEC 42001:2023, HIPAA-ready with BAA, for commercial products. |
| Enterprise controls | SSO, dedicated support, custom compliance documentation on Enterprise. | SSO, SCIM, audit logs, Compliance API, custom retention, IP allowlisting on Enterprise. |
| Best fit | Canadian organisations where data jurisdiction decides the purchase. | Teams that prioritise Claude's models and agent tooling and can accept US or cloud-partner-region processing. |

## Where Claude wins

- Model limits. All four current Claude models publish a 1M-token context and 128K output tokens. Augure caps output at 32,768 tokens, and only rosedale-1 reaches 1M context.
- Agentic tooling. Claude Code, Cowork and Managed Agents ship today, with per-agent geo pinning on Managed Agents. Augure Code and the desktop app cover coding and local tasks, but the catalogue is smaller.
- Enterprise governance. Anthropic's Enterprise plan lists SCIM, audit logs, a Compliance API, custom data retention controls and IP allowlisting. Augure Enterprise publishes SSO, dedicated support and custom compliance documentation.
- Published certifications. Anthropic lists SOC 2 Type I and II, ISO 27001:2022, ISO/IEC 42001:2023 and a HIPAA-ready configuration with a BAA. Procurement teams can pull those from its Trust Portal today.
- Low-end price. Claude Haiku 5.5 starts at US$0.10 input and US$0.50 output per 1M tokens. tofino-3 is C$0.60 and C$2.00.

## Where Augure wins

- Residency is first-party, not a cloud partner's region. Augure runs inference on Canadian infrastructure and with vetted EU partners under zero-data-retention agreements, and never routes it to providers in the United States. Anthropic's own API offers `us` or `global` inference only.
- A hard Canada-only switch with a visible audit trail. A Canada-only account fails a request with `503 residency_unavailable` rather than serving it elsewhere, and every response carries `_augure.inference_region`.
- Jurisdiction, scoped to customer content. Augure has no US corporate parent and no US investors. Customer conversations, documents and AI inference are never handled by US-jurisdiction providers, so the CLOUD Act's reach over US-controlled providers does not extend to customer content. Limited US processing exists for payment card networks and email delivery only, documented in the privacy policy.
- Training is never, not by default. Customer data is never used to train models, with no feedback exception.
- Quebec French natively, CAD billing, and chat plans from C$0 to C$80 per month with no seat minimum.

## Switch from Claude to Augure

### Chat path (Team or Enterprise)

1. Export your data. In Claude, Settings > Privacy > Export data emails a download link that expires after 24 hours. Team and Enterprise members can export only if an owner enables it; Primary Owners export the whole organisation from Organization settings > Data and privacy. Uploaded file contents are not included, so collect source documents separately.
2. Create an Augure account at https://chat.augureai.ca. Free gives you ossington-5 with a daily limit; Pro removes message limits and allows 100 document uploads a month.
3. What carries over: documents you re-upload, projects you recreate, and Knowledge sources (5 at a time on Free and Pro, 15 on Max).
4. What does not: chat history, Claude projects and connectors, Cowork sessions and Managed Agents. Rebuild project instructions as Augure projects.
5. For SSO, dedicated support and custom compliance documentation, write to enterprise@augureai.ca.
6. Run both for two weeks with one team and compare answers on your own documents, in both languages.

### API path

1. Create a key at https://augureai.ca/developers (self-serve, billed monthly in CAD).
2. Replace the `anthropic` client with the `openai` client pointed at `https://api.augureai.ca/v1`. If you already use Anthropic's OpenAI SDK compatibility endpoint, only `base_url`, the key and the model id change.
3. Map model names.

| Claude model | Augure model | Why |
|---|---|---|
| `claude-fable-5-1`, `claude-opus-5-5` | `ossington-5` | Flagship reasoning and code; `reasoning_effort` from `none` to `high`. |
| `claude-sonnet-5-5` on long inputs | `rosedale-1` | Up to 1M context, tool calling and agent loops; use `reasoning_effort: "low"` for fast tool calls. |
| `claude-haiku-5-5` | `tofino-3` | Fast, thinking always off, classification and extraction. |

4. Before and after in Python:

```python
# Before: Anthropic
import os
import anthropic
client = anthropic.Anthropic(api_key=os.environ["ANTHROPIC_API_KEY"])
msg = client.messages.create(
    model="claude-sonnet-5-5",
    max_tokens=1024,
    messages=[{"role": "user", "content": "Summarise this contract in two lines."}],
)
print(msg.content[0].text)

# After: Augure
from openai import OpenAI
client = OpenAI(base_url="https://api.augureai.ca/v1", api_key=os.environ["AUGURE_API_KEY"])
resp = client.chat.completions.create(
    model="ossington-5",
    messages=[{"role": "user", "content": "Summarise this contract in two lines."}],
)
print(resp.choices[0].message.content)
print(resp.model_extra["_augure"]["inference_region"])
```

5. Re-check: Anthropic requires `max_tokens`; Augure reasoning models want it omitted (cap 32,768; tofino-3 16,384). Thinking comes back as `reasoning_content`, not as thinking blocks. The `system` prompt becomes a `system` role message. Tool definitions move to the OpenAI `tools` shape, and tool results become `role: "tool"` messages. `response_format` json_schema is prompt-enforced on reasoning models, so validate and retry once.
6. Run both providers in parallel for a week, log `_augure.inference_region` and `finish_reason`, then cut over.

### Claude Code users

`claude mcp add --transport http augure https://mcp.augureai.ca/mcp` gives Claude Code an `ask_augure` tool that runs on Augure models in Canada. That tool is sovereign; Claude Code's own model is not. For an agent that runs end to end on Augure, install Augure Code or point an OpenAI-compatible agent at `https://api.augureai.ca/v1`.

## Keep Claude if

- You need 128K output tokens or 1M context on every model, or you depend on Cowork and Managed Agents.
- Your residency requirement is satisfied by a Canadian region on Amazon Bedrock or Google Vertex AI, with Anthropic's published certifications.
- Your buyers require SCIM, audit logs and a Compliance API today.
- Your workload lives at the price point of Haiku 5.5.

## Sources

- https://claude.com/pricing (checked 2026-10-27): Team $20 annual or $25 monthly per standard seat, premium seats $100 or $125, 2 to 150 seats (only Enterprise is labelled US$); Enterprise US$20 per seat plus usage, 20-seat minimum; SSO, SCIM, audit logs, Compliance API, custom retention, IP allowlisting; "No model training on your content by default"; US-only inference at 1.1x.
- https://platform.claude.com/docs/en/manage-claude/data-residency (checked 2026-10-27): `inference_geo` values `global` and `us`; `us` is the only workspace geo; 1.1x pricing; Claude 4.6 and later; not available through the OpenAI SDK compatibility endpoint; Managed Agents geo pinning.
- https://claude.com/regional-compliance (checked 2026-10-27): regional data residency for Europe, United States, Canada and Asia-Pacific on AWS Bedrock and GCP Vertex; "Regional endpoints guarantee that both data storage and model processing remain within your specified geographic region."
- https://platform.claude.com/docs/en/models/overview (checked 2026-10-27): Claude Fable 5.1, Opus 5.5, Sonnet 5.5, Haiku 5.5 ids, USD prices, 1M context, 128K max output.
- https://privacy.claude.com/en/articles/7996868-is-my-data-used-for-model-training (checked 2026-10-27, dated 2026-08-18): commercial products not used for training by default; feedback opt-in; "Rate chats" admin setting.
- https://www.anthropic.com/news/updates-to-our-consumer-terms (checked 2026-10-27, dated 2025-08-28): consumer Free, Pro and Max users choose whether chats train Claude; five-year retention if allowed, 30 days otherwise; commercial terms unaffected.
- https://support.claude.com/en/articles/10015870 (checked 2026-10-27, dated 2026-03-16): SOC 2 Type I and II, ISO 27001:2022, ISO/IEC 42001:2023, HIPAA-ready with BAA, for commercial products.
- https://support.claude.com/en/articles/9450526-how-can-i-export-my-claude-ai-data (checked 2026-10-27): export steps, 24-hour link, owner-enabled export on Team and Enterprise, uploaded files excluded.
- https://platform.claude.com/docs/en/manage-claude/api-and-data-retention (checked 2026-10-27): ZDR and HIPAA arrangements; retained data never used for training without express permission.
- https://platform.claude.com/docs/en/api/messages (checked 2026-10-27): Messages API parameters `model`, `max_tokens`, `messages`.
- https://augureai.ca/llms.txt, https://augureai.ca/docs/api, https://augureai.ca/docs/models, https://augureai.ca/docs/agents, https://augureai.ca/docs/integrations/openai-python (checked 2026-10-27): all Augure facts, prices in CAD and model ids.