Trust & compliance · Saudi Arabia
Evidence, not promises.
Sadu is built for PDPL-era deployments: residency is enforced in the router core, every request leaves an audit row, and the controls below map to the frameworks your assessors ask about. This page is the technical evidence pack — forward it to your compliance team.
The invariant
A ksa-pinned key can never reach a non-sovereign provider
Enforcement lives in one place — the router core — and applies to every model, including our own Sadu orchestrator. A request with no sovereign route fails closed with 403 residency_violation. It is a property of the system, provable in our test suite and verifiable against production with one script.
Control mapping
Where each framework concern is handled
| Framework concern | Technical control |
|---|---|
| PDPL cross-border transfer restrictions | Per-key residency pin + router-core filter; requests without a sovereign route fail closed (403), never silently fall back |
| NCA ECC / CST cloud controls — data classification | Residency is a property of the API key, decided at issuance: classify a workload once, the router enforces it on every request |
| SAMA outsourcing & financial-sector rules | Sovereign-only routing for pinned keys plus a complete per-request audit trail (provider, residency, tokens, cost, latency) |
| Auditability | Every request writes an immutable usage row; one-call CSV export covers NCA / SAMA / internal-audit reviews |
| Data minimization & training consent | Trace prompt excerpts are capped; per-key training opt-out is enforced at the write path — opted-out prompts are never stored |
Engineering documentation, not legal advice — map these controls to your own PDPL/NCA/SAMA/CST assessment with counsel.
Data flow
What stays in the Kingdom
Your application
Speaks the OpenAI wire format to a single endpoint: api.sadu.cloud.
Sadu — KSA region
Gateway, router, billing ledger, usage rows, Sadu traces and policies: all state lives on in-Kingdom infrastructure.
Model providers
ksa-pinned keys route only to in-Kingdom deployments. Global keys may use frontier providers abroad — your choice, per key.
The sovereign lane is enforced by the same router that serves global traffic — one codebase, one audit trail, two residency classes.
Live catalog
Residency status per model
Read live from the production catalog. ksa models never leave the Kingdom.
| Model | Provider | Residency |
|---|---|---|
| local-ksa/allam-2-7b | local-ksa | ksa |
| sadu/sadu-1-ksa | sadu | ksa |
| anthropic/claude-haiku-4-5 | anthropic | global |
| anthropic/claude-opus-4-1 | anthropic | global |
| anthropic/claude-sonnet-4-5 | anthropic | global |
| deepseek/deepseek-chat | deepseek | global |
| deepseek/deepseek-reasoner | deepseek | global |
| google/gemini-2.5-flash | global | |
| google/gemini-2.5-pro | global | |
| groq/llama-3.3-70b-versatile | groq | global |
| mistral/mistral-large-latest | mistral | global |
| mistral/mistral-small-latest | mistral | global |
| openai/gpt-4.1 | openai | global |
| openai/gpt-4.1-mini | openai | global |
| openai/gpt-4o | openai | global |
| openai/gpt-4o-mini | openai | global |
| openai/text-embedding-3-large | openai | global |
| openai/text-embedding-3-small | openai | global |
| sadu/sadu-1 | sadu | global |
| sadu/sadu-1-ultra | sadu | global |
| together/meta-llama/Llama-3.3-70B-Instruct-Turbo | together | global |
Audit evidence
One call, assessor-ready CSV
Every request is metered into an immutable usage row. Export any date range as CSV with a single authenticated call — the exact columns your reviewers will see:
Sadu provides engineering controls and documentation; it does not provide legal advice. Compliance mappings on this page describe how the system behaves, verified by automated tests.
Bring your compliance team.
Start with a global key in minutes, pin a ksa key when your workload demands it — the audit trail is on from the first request.
Get your API key