megachangelog
Feature

Regional inference now available on AI Gateway

AI Gateway now supports regional inference, allowing you to pin requests to US or EU data centers via the inferenceRegion field. Every response reports which region served the request, ensuring data residency and compliance requirements are met consistently across all model providers.

AI Gateway now supports . Set on a request to pin it to the US or EU. Every model provider that supports the selected region handles it the same way. Inference runs there, and any data the provider keeps is stored there.regional inferenceinferenceRegion

AI Gateway supports two pinned regions, plus global routing:

If no model provider can serve it, the request fails rather than running somewhere else. Every response reports the region that served it, so you can confirm where each request ran.

Here's a request pinned to the US with the AI SDK:

Until now, teams with data residency or compliance requirements had to configure regional routing separately for every provider, with no reliable way to confirm where a request actually ran. Regional inference replaces that with a single field that behaves the same everywhere and a response that tells you where each request was served.

Filter the for models available in the US or EU, or read the array from . Without , requests route globally with no residency guarantee, so residency is opt-in.model listregions/v1/modelsinferenceRegion

Pinning a region can cost more. The provider sets the regional rate, often around 10% above standard, and AI Gateway passes it through with no markup. For per-provider overrides, response verification, pricing, and BYOK behavior, read the .regional inference documentation

Read more

Region

Where inference runs

us

A US data center

eu

An EU data center

global

Any region

ai-gatewayinferencecompliancedata-residencyapi

Source: original entry ↗