Provider matrix

Managed-provider operating matrix

The managed providers Dolphin can route to, with region and sovereignty posture. Source of truth is packages/provider-adapters/src/provider-registry.ts; keep this table in sync when the registry changes. This is staff-only — real provider names never appear on the customer help portal (aliases only, D-5).

Provider Adapter family Region Sovereignty Status Operational notes
OpenAI OpenAI-compatible us us_jurisdiction default-on Tier-1 OpenAI-compatible adapter. US jurisdiction — disclose in DPA.
さくらのAI Engine OpenAI-compatible japan jp_sovereign default-on JP-sovereign. Lead option for customers asking for domestic processing.
Azure OpenAI (Japan East) Azure OpenAI japan-east jp_sovereign default-on API version 2024-10-21. JP-sovereign via Japan East region.
Google AI Studio (Gemini) Gemini global us_jurisdiction default-on Served from Google's US-jurisdiction global edge. Non-bearer x-goog-api-key auth.
Cloudflare Workers AI OpenAI-compatible global global_edge default-on Global edge. Requires account_id path param.
Groq OpenAI-compatible us us_jurisdiction default-on US jurisdiction. Quirks: forces n=1, replaces temperature 0.
DeepSeek OpenAI-compatible china china_processing default-off (gated) China processing. OFF by default — requires explicit per-tenant approval (doc 05 §3).
Kimi / Moonshot OpenAI-compatible china china_processing default-off (gated) China processing, region-bound API key. OFF by default — gated per tenant.

Sovereignty key

China-provider gating

DeepSeek and Kimi/Moonshot are default-off and gated per tenant (doc 05 §3). They are never routed to unless a tenant has been explicitly approved. Use the China-provider talking points in sales enablement when a customer asks why these are not on by default.