Your prompts carry client matters, patient records, financial PII. Sending them to OpenAI, Anthropic, or Google means a transfer to a US provider: a Schrems II problem, a sub-processor your DPO has to approve, an EU AI Act exposure you can't wave away. So the feature stalls on the roadmap while legal and engineering argue, and your competitors ship.
Keep your OpenAI client and your code. Point it at Akumi and you are running on EU-resident models, no rewrite and no new SDK.
Read the quickstartFlip on the PII firewall, Recall, guard, or cache. Each is a per-request toggle, metered on its own, not a project.
Explore the PII firewallEvery request is metered, audited, and EU-resident from the first token. Hand compliance the log, not a risk assessment.
See the audit trailInference and storage stay in the EU, no US CLOUD Act exposure. Personal data is pseudonymized before any model sees it, non-EU routing is blocked unless you allow it, and every request is audited. Hand your DPO the trail, not the risk.
Point your existing OpenAI client at one base_url. It runs unchanged: chat, tools, streaming, structured output. One metered bill, no migration.
Recall, guard, caching, and observability are toggles, not projects, each EU-resident and metered per use. Build real products on your own data without wiring up five vendors.
Start on pay as you go, or talk to us about your compliance requirements.
We use privacy-friendly, EU-hosted analytics to understand how Akumi is used. Accept analytics cookies, or continue without them. See our cookie policy.