Key facts
| API compatibility | OpenAI-compatible /v1/chat/completions - change base_url and model name |
| Models | 30+ models behind one API, from free tiers to frontier reasoning |
| Nearest data plane | US (Virginia); region-locked, so prompts, completions, embeddings and logs stay in-region |
| Deployment | Plugsky cloud, your VPC, on-prem or air-gapped |
| RAG and embeddings | Embeddings and retrieval are live for private document search |
| Pricing model | Flat monthly self-serve plans; no per-token billing on self-serve |
| Free tier | Free plan with 2 free AI models (plugsky-micro, plugsky-lite), no card |
TL;DR
- Pin the US (Virginia) plane so prompts, completions, embeddings and logs stay in one jurisdiction.
- An OpenAI-compatible API means a base-URL change, not a rewrite, for Montreal teams.
- One API covers small pilots and frontier reasoning, so models can change without a migration.
- Deploy in a VPC, on-prem or air-gapped when Quebec privacy law obligations or internal policy require it.
- Evaluate on the free plan or the 14-day full-access trial before committing.
How it works, step by step
- Map which Montreal workloads touch personal or regulated data, and classify each one.
- Choose a data plane; for Canada the nearest documented option is US (Virginia).
- Create a Plugsky account and API key on the free plan (two models, no card), or use the 14-day full-access trial.
- Change base_url to api.plugsky.com, map model names, and run your existing tests and evals.
- Measure latency from your Montreal network and set timeouts and retries for your workload.
- Add scoped keys and logging, then decide whether a VPC, on-prem or air-gapped deployment is required.
Original data
Try it yourself
Open the data residency checker →
Why Montreal teams choose where AI runs
Montreal is a bilingual city with a dense AI research community, aerospace and gaming industries, and a growing fintech base. Teams here build assistants that must handle French and English content equally well. Quebec's privacy law and Canadian federal rules both apply, so residency and consent design get early attention.
Production workloads in Montreal usually sit in AI research and software, aerospace and gaming and financial services. Quebec's privacy law and Canada's federal privacy regime both apply. That turns region choice into an architecture decision: inference, embeddings, retrieval and logs should be pinned to the same place, and the choice should be provable with documentation rather than assumed from a vendor page.
How an AI cloud deployment in Montreal works on Plugsky
Plugsky exposes an OpenAI-compatible /v1/chat/completions endpoint, so migration is a base URL change plus model mapping: your SDK, streaming, function calling and JSON mode keep working. The catalogue holds 30+ models, from the free plugsky-micro and plugsky-lite tiers to frontier reasoning models. Evaluate French and English prompts on the same test set.
Plugsky supports region-locked data planes; see /data-residency. For Canada, the nearest documented plane is US (Virginia), and prompts, completions, embeddings and logs stay in-region by architecture. Enterprise adds customer-managed keys, zero-knowledge mode and right-to-audit clauses; where in-country processing is mandatory, the same API runs in your VPC, on-prem or air-gapped. Canada is not one of the headline planes; teams with Canadian residency requirements should confirm current options at /data-residency or use VPC, on-prem or air-gapped deployment.
Latency, failover and multi-region design
Montreal clients reach the US plane in Virginia over eastern North American routes; latency is moderate, and Canadian residency requirements may rule that plane out entirely.
Where Canadian residency is required, design failover inside your own environment rather than across a border, and document that boundary for auditors.
A rollout plan that fits Montreal
Start with one AI research and software workflow and a fifty-question evaluation set drawn from real cases. Pin the US (Virginia) plane while you evaluate on the free plan (plugsky-micro and plugsky-lite, no card), or use the 14-day full-access trial for larger models, then measure answer quality and round-trip time from your own network. Before production, settle scoped keys with rotation, log retention, a model allow-list tied to evaluations, and a deployment choice that follows from Quebec privacy law obligations.
Honest comparison
| Capability | Plugsky | Single-endpoint AI API | Building in-house |
|---|---|---|---|
| Region options | EU, GCC, APAC and US planes; Riyadh on Enterprise | Usually one global endpoint | You operate every region |
| Residency enforcement | Region-locked by architecture | Often contractual only | You build the controls |
| Migration effort | Base URL plus model mapping | Vendor-specific SDK | Full rewrite |
| Model choice | 30+ models behind one API | Single-vendor catalogue | You host each model |
| Pricing model | Flat monthly self-serve, no per-token billing | Per-token metering | GPU plus operations cost |
| Endpoint roadmap | Audio, images, moderation, files, batch and fine-tuning coming soon | Varies by vendor | Separate pipelines to maintain |
Frequently asked questions
Which region should a Montreal workload use?
The nearest documented plane for Canada is US (Virginia); verify current availability at /data-residency before pinning production.
Does Plugsky have a data center in Montreal?
Plugsky does not publish city-level data center locations. Region availability is listed at /data-residency, and enterprise teams can deploy in their own VPC, on-prem or air-gapped environment.
Is there a free plan?
Yes - the free plan includes two free AI models (plugsky-micro and plugsky-lite) with no credit card required.
How does pricing work?
Self-serve plans are flat monthly with unlimited fair-use usage and no per-token billing; see the live pricing page for current plans.
Can we keep our existing OpenAI SDK code?
Yes. Change the base URL to api.plugsky.com and map model names; streaming, function calling and JSON mode continue to work.
Can data stay inside our own network?
Yes. VPC, on-prem and air-gapped deployments are available, with customer-managed keys and audit-log export on Enterprise.
Is a trial available?
Yes - a 14-day full-access trial is available alongside the free plan for evaluation.