The problem
Most AI traffic defaults to a US endpoint, and the data in a prompt is often the most sensitive thing an organization has. GDPR, sector rules, and works-council agreements all ask the same thing: where does the data go, who can see it, and can you prove it. A gateway you do not control does not answer that.
How it works
aigw runs its control and data plane in the EU. You choose which models are available and route each one to an EU region where the provider offers one. The gateway mediates every call, so provider credentials stay inside it and never travel with your apps. For teams that need to own the boundary entirely, a self-hosted deployment is available for enterprise.
What you get
- An EU-hosted control and data plane, not a US service with an EU label.
- Per-model region routing, so you can restrict a workspace to EU-region models.
- Credential custody: the gateway holds provider keys and rotates them centrally, so a leaked app never leaks a key.
- A self-hosted deployment option for enterprise, for air-gapped or fully sovereign environments.
See providers for region and credential configuration.