# Akumi: the EU AI stack. Data residency you can prove

The EU AI stack: one platform for your applications, your team and your codebase. EU data residency enforced per request, with a record you can prove.

## The EU AI stack.

Three products. One audit trail.
Nothing leaves the EU unless you send it. You can prove it.

## Nine services. Three ways in.

The Platform is the services. Chat and Code are two more doors into the same building.

### Akumi Platform

In service. All nine services, over one OpenAI-compatible API.

### Akumi Chat

In preview. Not yet available. The same services, as chat for your whole team.

### Akumi Code

In preview. Not yet available. Recall over every PR, issue and decision, for your coding agent.

### Build

Get a model answering, fast.

- Inference API: OpenAI-compatible, metered per use

- MCP Server: Memory and tools for AI clients

- Cache: Reuse responses, cut cost and latency

### Govern

Decide what a model may see and say.

- Model Router: Policy-based routing with fallback

- Firewall: Pseudonymize before models see data

- Recall: Memory and documents in one knowledge graph

### Prove

Show an auditor what happened.

- Audit Trail: Every request, every product, one record

- Compliance Center: Art. 30 ROPA and EU AI Act records

- Observability: Trace latency, cost and every stage

Whichever product makes the call, the same nine services run, and the same trail records it.

## Answers for the person who has to sign off.

### Where does the data actually live?

Storage and the application never leave the EU. Model calls leave only with your recorded approval. Your CLOUD Act exposure is a list you can produce.

See: [object Object]

### Does a model ever see personal data?

Not with the firewall on. Personal data is replaced with tokens before any model sees it, and restored only in your own response. The firewall is a per-workspace switch, and the audit trail records which setting each request ran under.

See: [object Object]

### Can we prove it afterwards?

Every request records where it ran, and a metadata-only audit trail is retained on your own policy.

See: [object Object]

### Who else touches the data?

Every sub-processor is disclosed up front. The DPA is available on request.

See: [object Object]

### Which regulations does this cover?

GDPR and the EU AI Act from the start, documented for DORA and NIS2. ISO 27001 is in progress, and we say so.

See: [object Object]

Registered in the Netherlands. No US parent.

## This is the whole migration.

Keep your OpenAI client and your code. One line points it at the EU, and the record starts writing itself.

### Before

Your data leaves the EU, and nothing is written down. You write the risk assessment yourself, from memory.

### With Akumi

EU-resident by default, and a record of every call. Hand compliance the log, not a risk assessment.

Only the base URL changes: base_url="https://api.akumi.eu/v1".

## Ship the AI feature legal already approved.

Three ways in, one key, one audit trail. Pick the door that fits.

### Akumi Platform

In service. An OpenAI-compatible API and nine services you switch on per request. Swap one URL and start.

### Akumi Chat

In preview. Not yet available. Private AI chat for your whole team. Same platform, same audit trail.

### Akumi Code

In preview. Not yet available. Recall over every PR, issue and decision, for your coding agent.