Key facts
| API compatibility | OpenAI-compatible /v1/chat/completions; change the base URL |
| Models | 30+ models, from free chat tiers to frontier reasoning |
| Pricing | Flat monthly self-serve plans with unlimited fair-use usage; no per-token billing |
| Free plan | plugsky-micro and plugsky-lite; no card required |
| Trial | 14-day full-access trial for higher tiers |
| Deployment | Plugsky cloud, your VPC, on-prem and air-gapped |
| Data residency | GCC plane (me-central-1, UAE); Riyadh available on Enterprise |
| Local presence | No Dukhan office or data-centre claim; residency is region-based |
TL;DR
- OpenAI-compatible API: change the base URL and keep your SDK.
- 30+ models behind one endpoint, from free chat tiers to frontier reasoning.
- Flat monthly plans with no per-token billing on self-serve.
- GCC region-locked plane (me-central-1, UAE) keeps data in-region; Riyadh is available on Enterprise.
- Free plan with plugsky-micro and plugsky-lite; 14-day full-access trial.
How it works, step by step
- Create a Plugsky account and issue an API key on the free plan — no card required.
- Point your OpenAI SDK at api.plugsky.com and map your model names.
- Choose the deployment topology that matches your rules: Plugsky cloud region, your VPC, on-prem or air-gapped.
- Select the GCC plane (me-central-1, UAE) for in-region processing, or ask about Riyadh on Enterprise.
- Replay your existing prompts and evaluations against the same test set.
- Measure latency from your Dukhan network against candidate regions before cut-over.
- Review the DPA, the SLA and the /data-residency documentation, then cut over behind a flag with the one-line rollback ready.
Original data
Try it yourself
Open the data residency checker →
What Dukhan teams need from sovereign AI
Dukhan sits on Qatar's western coast and grew around the Dukhan oil field, one of the country's oldest energy operations. Its workforce is industrial and engineering-heavy, with operations, maintenance and HSE teams that handle sensitive technical documentation and need tooling that stays reliable in the field.
Typical workloads include maintenance-manual search, HSE reporting, inspection summaries and shift-handover notes. Plugsky serves that mix with one OpenAI-compatible endpoint and 30+ models, so prototypes on plugsky-micro or plugsky-lite can move to larger models without changing SDKs. Existing code, prompts and evaluations keep working; the docs list endpoints and current model names.
Which region serves Dukhan workloads?
Plugsky publishes region-locked data planes in the EU (Frankfurt), GCC (UAE), APAC (Singapore) and US (Virginia), with Riyadh available on Enterprise. Prompts, completions, embeddings and logs stay in the plane you choose by architecture rather than contract. For Dukhan, the closest published plane is the GCC plane (me-central-1, UAE). There is no Plugsky office or data centre in Dukhan; residency is a property of the region and deployment model, not of local premises.
The GCC plane is aligned with PDPL, DIFC and NSD expectations in the UAE, and additional regions are listed in the docs. Validate the current list and the contractual wording in the data-residency overview, the DPA and the SLA before you sign.
Deployment models for Dukhan teams
Four paths cover most Dukhan scenarios: a managed Plugsky cloud region, a private endpoint inside your own AWS, Azure or GCP account, on-prem infrastructure you own, and air-gapped deployment for classified or critical workloads with no internet egress, a local model registry and offline update channels. Moving from global routing to a locked plane changes latency: the closer the plane to your network the shorter the path, though strict boundaries can cost round-trip time against globally distributed endpoints.
Test before you commit — send representative prompts from your Dukhan environment to each candidate region, compare p50 and p95, then choose. Region and deployment changes are configuration, not code changes.
How Dukhan teams migrate and control spend
Migration is one line: point the OpenAI SDK base URL at Plugsky and map model names, then replay your evaluations and cut over behind a flag so rollback stays trivial. Chat, streaming, JSON mode, function calling, embeddings, RAG and agents are live; audio, images, moderation, files, batch, fine-tuning, assistants and responses are coming soon — label them before planning those workloads.
Cost control is flat-rate on self-serve plans: unlimited fair-use usage with no per-token billing, so Dukhan teams forecast a monthly line item instead of token spend. Start free with plugsky-micro and plugsky-lite, and use the 14-day full-access trial to evaluate larger models. Current plans are listed on the pricing page.
Honest comparison
| Capability | Plugsky | Typical global API provider | Building in-house |
|---|---|---|---|
| API compatibility | OpenAI-compatible — change the base URL | Usually compatible, varies by model | Full rewrite and integration work |
| Models | 30+ models behind one endpoint | Mainly the provider's own catalogue | You host and maintain each model |
| Pricing | Flat monthly self-serve plans, no per-token billing | Per-token billing, harder to forecast | GPU, operations and staffing costs |
| Data residency | GCC plane (me-central-1, UAE); VPC, on-prem, air-gapped | Limited region choices | You own the responsibility |
| Local presence in Dukhan | No office or data-centre claim; residency is region-based | Varies; few publish local commitments | Depends on your own facilities |
| Migration effort | Base URL plus model mapping | Depends on compatibility gaps | Long integration cycle |
Frequently asked questions
Does Plugsky have a data centre or office in Dukhan?
No. Plugsky does not claim a local office or data centre in Dukhan; residency is delivered through region-locked data planes, or through deployments in your own VPC, on-prem or air-gapped. See /data-residency for the current region list.
Which region should Dukhan teams choose?
The closest published plane is the GCC plane (me-central-1, UAE), with Riyadh available on Enterprise. The right choice depends on your jurisdiction and regulator rather than distance alone; confirm the current region map at /data-residency.
Can we keep using the OpenAI SDK?
Yes. Plugsky exposes an OpenAI-compatible chat completions endpoint, so you change the base URL and model name and keep your existing SDK, prompts and evaluations.
Is there a free plan?
Yes — the free plan includes plugsky-micro and plugsky-lite with no credit card required. A 14-day full-access trial is available when you want to evaluate larger models.
How is pricing structured?
Self-serve plans are flat monthly with unlimited fair-use usage and no per-token billing. See the live pricing page for current plans and fair-use limits.
Which capabilities are live today?
Chat, streaming, JSON mode, function calling, embeddings, RAG and agents are live. Audio, images, moderation, files, batch, fine-tuning, assistants and responses are coming soon — check the docs before planning those workloads.
What about latency from Dukhan?
It depends on the region you select and how your network routes to it. Measure candidate regions from your own environment, compare p50 and p95, and treat residency and latency as an explicit trade-off.
Do you support customer-managed keys?
Yes — enterprise deployments support customer-managed keys; check the docs and the DPA for the exact scope in your chosen region.