Key facts
| API compatibility | OpenAI-compatible /v1/chat/completions, /v1/embeddings and /v1/models |
| Migration effort | Change base_url and model name; keep your OpenAI SDK |
| Plane for this market | EU plane, Frankfurt (eu-central-1); region-locked for GDPR-aligned processing |
| Models | 30+ models behind one API, from free tiers to frontier reasoning |
| Pricing | Flat monthly self-serve plans, no per-token billing; see the live pricing page |
| Free tier | plugsky-micro and plugsky-lite with no credit card |
| Compliance alignment | The EU plane is aligned with GDPR and ISO 27001 expectations |
| Roadmap endpoints | Audio, images, moderation, files, batch, fine-tuning, assistants and responses are coming soon |
TL;DR
- Keep the OpenAI SDK; switch base_url to api.plugsky.com and map model names.
- Pin the EU plane (Frankfurt) or deploy in your own network to satisfy the GDPR and the Loi Informatique et Libertes.
- Flat monthly pricing replaces per-token cost surprises on self-serve plans.
- Start free with plugsky-micro and plugsky-lite, or use the 14-day full-access trial for deeper testing.
- Where Plugsky does not replace OpenAI yet: audio, image and fine-tuning endpoints are still roadmap items.
How it works, step by step
- Inventory which OpenAI endpoints you call: chat, embeddings, streaming and tools.
- Create a Plugsky workspace and API key; the free plan needs no card.
- Point your OpenAI SDK at api.plugsky.com and map model names.
- Re-run your existing tests and evaluations against the same prompts.
- Pin the deployment or plane that satisfies the GDPR and the Loi Informatique et Libertes.
- Cut over gradually and keep the old base URL for rollback.
- Document the residency evidence France reviewers will ask for.
Original data
Try it yourself
Open the OpenAI migration checker →
Why France teams look for an OpenAI alternative
French teams look for alternatives that reduce CLOUD Act exposure and produce residency evidence for CNIL reviews and public-sector tenders. Three pressures dominate: unpredictable per-token bills, residency rules that a US-default endpoint does not satisfy on its own, and the cost of maintaining integrations for several providers.
Sovereignty is an architecture decision covering processing location, storage location, key custody and audit evidence. Plugsky separates these layers, so you can adopt a strict posture for one workload and a lighter one for the next without running two platforms.
Migration: keep your OpenAI SDK and code
You keep your OpenAI SDK and change two values: base_url and model. Streaming, JSON mode, function calling and embeddings work through the same shapes you already use, which keeps your existing tests meaningful.
- Inventory which OpenAI endpoints you actually call: chat, embeddings, streaming, tools.
- Create a Plugsky workspace and a scoped API key; the free plan needs no card.
- Point your SDK at api.plugsky.com and map model names.
- Re-run your existing tests and evaluations on the same prompts.
- Pin the deployment that satisfies the GDPR and the Loi Informatique et Libertes.
- Cut over gradually and keep the old base URL for rollback.
Data residency and compliance for France
GDPR, as implemented by the Loi Informatique et Libertes, applies with the CNIL as regulator. The state 'cloud au centre' doctrine requires sovereign-qualified services for public workloads, and ANSSI's SecNumCloud is the reference certification for them. HDS certification governs health data hosting.
French teams pin the EU plane (Frankfurt) for GDPR-aligned processing, or run in-country VPC, on-prem or air-gapped deployments when SecNumCloud-style guarantees are mandatory. The EU plane is aligned with GDPR and ISO 27001 expectations.
Region-locked planes keep prompts, completions, embeddings and logs inside the chosen jurisdiction by architecture, and Enterprise agreements add BYOK, zero-knowledge mode and right-to-audit clauses.
What it costs, and what is still missing
Pricing is flat monthly on self-serve plans with no per-token metering, plus a free tier (plugsky-micro and plugsky-lite) and a 14-day full-access trial for evaluation. See the live pricing page for the current line-up.
CNIL guidance on AI expects a documented legal basis for training and inference data, so keep a record of your processing decisions. Where Plugsky does not replace other providers yet: audio, images, moderation, files, batch, fine-tuning, assistants and responses are roadmap items. Chat, streaming, tools, JSON mode, embeddings, RAG and agents are live today.
Honest comparison
| Capability | Plugsky | OpenAI | Building in-house |
|---|---|---|---|
| API compatibility | OpenAI-compatible chat, embeddings and models endpoints | Native SDKs and API | Full rewrite |
| Pricing model | Flat monthly self-serve plans; see the live pricing page | Per-token billing | GPU plus operations cost |
| Model choice | 30+ models from one endpoint | OpenAI models only | You host each model |
| Data residency | Region-locked planes plus VPC, on-prem and air-gapped | US default with some enterprise options | Wherever you deploy |
| Migration effort | One-line base URL change | Not applicable | Months of engineering |
| Free tier | plugsky-micro and plugsky-lite, no card | Limited trial credits | Not applicable |
Frequently asked questions
Is Plugsky a drop-in replacement for OpenAI in France?
Yes for the live surface: chat completions, streaming, JSON mode, function calling, embeddings, RAG and agent loops all work through OpenAI-shaped requests. You change the base URL and model name and keep your SDK.
How does data residency work for France teams?
GDPR, as implemented by the Loi Informatique et Libertes, applies with the CNIL as regulator. The state 'cloud au centre' doctrine requires sovereign-qualified services for public workloads, and ANSSI's SecNumCloud is the reference certification for them. HDS certification governs health data hosting. French teams pin the EU plane (Frankfurt) for GDPR-aligned processing, or run in-country VPC, on-prem or air-gapped deployments when SecNumCloud-style guarantees are mandatory. Plugsky publishes planes in the EU (Frankfurt), GCC (UAE), APAC (Singapore) and US (Virginia), with Riyadh on Enterprise.
How is pricing different from OpenAI?
Self-serve Plugsky plans are flat monthly with no per-token metering, so forecasting is simpler; the free plan includes plugsky-micro and plugsky-lite, and a 14-day full-access trial exists. See the live pricing page for current plans.
Can we keep using the OpenAI SDK?
Yes. Plugsky exposes an OpenAI-compatible chat completions endpoint, so you change base_url to api.plugsky.com and map your model names while keeping existing SDK code.
How does the GDPR and the Loi Informatique et Libertes affect migration?
GDPR, as implemented by the Loi Informatique et Libertes, applies with the CNIL as regulator. The state 'cloud au centre' doctrine requires sovereign-qualified services for public workloads, and ANSSI's SecNumCloud is the reference certification for them. HDS certification governs health data hosting. French teams pin the EU plane (Frankfurt) for GDPR-aligned processing, or run in-country VPC, on-prem or air-gapped deployments when SecNumCloud-style guarantees are mandatory.
Does streaming and function calling work?
Yes, streaming, JSON mode and function calling are live, as are embeddings, RAG and agent tool loops; check the docs for the per-model capability matrix.
What is not available yet?
Audio, image generation, moderation, files, batch, fine-tuning, assistants and responses endpoints are coming soon. Keep those workloads on their current provider until the status page marks them live.
How do we migrate and roll back safely?
Run both providers behind a routing flag: send a percentage of traffic to Plugsky, compare latency and quality on your own evaluation set, then switch fully. Rolling back is the same one-line base URL change in reverse.