data-residency compliance inference ai-gateway regional-routing

AI Gateway pins inference to US or EU regions

Set `inferenceRegion` to enforce data residency; every request reports where it ran, replacing multi-provider regional config.

Summary

Teams with compliance requirements no longer need per-provider regional routing setup. Requests fail rather than escape the pinned region, giving you verifiable data residency without guesswork.

Why it matters

Teams with compliance requirements no longer need per-provider regional routing setup. Requests fail rather than escape the pinned region, giving you verifiable data residency without guesswork.

Implementation verdict

Replaces manual regional routing config across providers. Requires updating calls with `inferenceRegion: { scope: 'zone', geoRegion: 'us' }` or `'eu'`. Ready now—check model availability via `/v1/models` endpoint first, accept ~10% regional cost premium.

Sources

1.Set `inferenceRegion` on a request to pin it to the US or EU
2.Every response reports the region that served it, so you can confirm where each request ran
3.If no model provider can serve it, the request fails rather than running somewhere else
4.Pinning a region can cost more. The provider sets the regional rate, often around 10% above standard

Dev Signal

Get briefs like this in your inbox — free, every weekday.

100+ sources compressed into one 4-minute read. Ranked, cited, implementation-ready.

Read the full issue →All briefs