Key facts
| Deployment models | Region-locked cloud planes, private endpoint in your VPC, on-prem and air-gapped |
| Plane for this market | US plane, Virginia (us-east-1) is nearest; Canadian residency needs a customer-managed deployment |
| Models | 30+ models behind one OpenAI-compatible API |
| Pricing | Flat monthly self-serve plans, no per-token billing; see the live pricing page |
| Residency enforcement | Architectural region lock; prompts, completions, embeddings and logs stay in-region |
| Access control | Scoped API keys, RBAC, SSO/SCIM and SIEM-exportable audit logs |
| Compliance alignment | The US plane is aligned with SOC 2 and HIPAA programs |
| Product status | Chat, streaming, JSON mode, function calling, embeddings and agents are live |
TL;DR
- Pin the US plane (Virginia) or deploy in your own network to meet PIPEDA, Quebec's Law 25 and provincial PIPA statutes.
- The same OpenAI-compatible API works across every deployment model, so no rewrite is needed.
- 30+ models, from free plugsky-micro and plugsky-lite to frontier reasoning tiers.
- Self-serve pricing is flat monthly; no per-token billing - see the live pricing page.
- Enterprise adds BYOK, zero-knowledge mode, audit export and right-to-audit clauses.
How it works, step by step
- Map your data classes and decide which must stay in Canada.
- Pick a deployment model: the US plane (Virginia), private endpoint, on-prem or air-gapped.
- Create a workspace and issue scoped API keys per environment and team.
- Point your OpenAI-compatible client at api.plugsky.com and map model names.
- Configure prompt retention, RBAC/SSO and audit export to your SIEM.
- Run an evaluation set on local-language and local-regulatory cases before scaling.
- Document the evidence path - DPA, sub-processors and residency attestations - for auditors.
Original data
Try it yourself
Open the AI data residency checklist →
What sovereign AI cloud means for Canada
Canada is a patchwork: federal privacy law, a strengthened Quebec statute and provincial rules that can each shape where AI data may flow. Architecture decisions often start with a data-classification exercise. Montreal (AWS ca-central-1) and Toronto (Azure Canada Central) anchor commercial capacity, while government buyers rely on Cloud Guardrails and Canadian Centre for Cyber Security guidance.
Sovereign AI cloud is a set of choices, not a single product: where inference runs, where prompts and embeddings rest, who holds the encryption keys, and what evidence you can hand an auditor. Plugsky exposes those choices separately, so a regulated workload can be pinned while everything else stays on the default plane.
Regulatory context: PIPEDA, Quebec's Law 25 and provincial PIPA statutes
PIPEDA applies federally; Quebec's Law 25 adds privacy-impact assessments and consent duties, and Alberta and British Columbia have their own PIPA statutes. Government buyers follow Cloud Guardrails and CCCS guidance.
Plugsky's response is architectural: the US plane is aligned with SOC 2 and HIPAA programs. Prompts, completions, embeddings and logs stay inside the selected plane, and the guarantee does not rest on a contractual promise alone.
Deployment options, from region-locked planes to air-gapped
Canadian residency requires in-country deployment - VPC, on-prem or air-gapped - because the headline planes are EU, GCC, APAC and US; the US (Virginia) plane is nearest for latency.
- Region-locked plane: managed inference in the EU (Frankfurt), GCC (UAE), APAC (Singapore) or US (Virginia), with Riyadh on Enterprise.
- Private endpoint: the same API inside your VPC.
- On-prem: run inside your own data centre.
- Air-gapped: fully disconnected environments for critical infrastructure.
Because the API surface is identical, moving a workload between these modes is configuration, not a rewrite.
Models, pricing and proof
One endpoint serves 30+ models, from plugsky-micro and plugsky-lite on the free plan to frontier reasoning tiers. Self-serve plans are flat monthly with no per-token billing, and enterprise plans add customer-managed keys, zero-knowledge mode and right-to-audit clauses; current plans live on the pricing page.
Quebec's Law 25 obligations can bind you even if you are not based there, whenever you serve Quebec residents. Meet the mirror check: audio, image generation, moderation, files, batch, fine-tuning, assistants and responses are coming-soon endpoints rather than live today. Treat them as roadmap items when comparing vendors, and verify per-plane model availability before you commit.
Honest comparison
| Consideration | Plugsky | Global hyperscaler AI | Self-managed in-country |
|---|---|---|---|
| Residency enforcement | Region-locked planes plus VPC, on-prem and air-gapped | Contractual commitments across shared regions | You build networking and controls |
| Model access | 30+ models on one OpenAI-compatible API | Vendor catalogue per platform | You serve and patch every model |
| Pricing | Flat monthly self-serve plans; see the live pricing page | Consumption-based line items | GPU capex plus operations |
| Time to first request | API key and a base-URL change | Platform-specific setup | Weeks to months |
| Audit and keys | Audit-log export, BYOK on Enterprise | Varies by service | You build everything |
Frequently asked questions
How does PIPEDA, Quebec's Law 25 and provincial PIPA statutes affect AI cloud choices in Canada?
PIPEDA applies federally; Quebec's Law 25 adds privacy-impact assessments and consent duties, and Alberta and British Columbia have their own PIPA statutes. Government buyers follow Cloud Guardrails and CCCS guidance. Canadian residency requires in-country deployment - VPC, on-prem or air-gapped - because the headline planes are EU, GCC, APAC and US; the US (Virginia) plane is nearest for latency.
Can Canada teams keep data in-country with Plugsky?
Canadian residency requires in-country deployment - VPC, on-prem or air-gapped - because the headline planes are EU, GCC, APAC and US; the US (Virginia) plane is nearest for latency. Plugsky publishes region-locked planes in the EU (Frankfurt), GCC (UAE), APAC (Singapore) and US (Virginia), with Riyadh on Enterprise; stricter in-country requirements are met with VPC, on-prem or air-gapped deployment.
Does Plugsky have a data centre or office in Canada?
Plugsky publishes region-locked planes rather than country-by-country facilities, so check /data-residency for the current list. Deployments in your own VPC, on-prem or air-gapped cover requirements that demand an in-country footprint.
Can we keep prompts, embeddings and logs in our jurisdiction?
Yes, on a region-locked plane the processing path - inference, embeddings and logs - stays in the selected region by architecture rather than by contract. Enterprise agreements add customer-managed keys, zero-knowledge mode and right-to-audit clauses.
What deployment models are available?
Four: a managed region-locked plane, a private endpoint inside your VPC, on-premises deployment, and air-gapped installation for disconnected environments. The API surface is identical across all four.
How is pricing structured, and is there a free option?
Self-serve plans are flat monthly with no per-token billing on the free plan or paid tiers beyond it; plugsky-micro and plugsky-lite are free with no card, and a 14-day full-access trial exists. See the live pricing page for current plans.
Which capabilities are live today?
Chat completions, streaming, JSON mode, function calling, embeddings, RAG and agent loops are live. Audio, images, moderation, files, batch, fine-tuning, assistants and responses are coming-soon endpoints.
How do we prove residency to an auditor?
Provide the DPA, the current sub-processor list, exported audit logs and a description of the residency architecture; Enterprise contracts add right-to-audit clauses. Keep sub-processor notifications in your evidence trail.