Skip to main content
Data residency restricts inference on your account to a single region. Once a region is set, every request must use that region’s API endpoint and a model served in that region. It does not change how your requests are routed. Turning it on will not move existing traffic into the region. This setting enforces all requests to be in the set region, and rejects the ones that are not.
Enterprise feature. Data residency is available on Enterprise accounts. Contact your Fireworks representative if you need this enabled.
Only account Admins can change data residency. Other roles can view the current setting but cannot change it.
Residency applies account-wide: every API key on the account is restricted to the selected region.

​
Available regional restrictions

None is the default. For a region that is not listed, contact sales.

​
Before you switch it on

A residency change takes effect as soon as you save it, and anything that does not match the region is rejected.

​
Serverless

Point your clients at the region’s API endpoint and change every request to use a model from that region. See US-only Serverless for the US endpoint and model IDs.
inference_geo is deprecated in favor of data residency. As you switch over, remove the inference_geo field from your request bodies and the Fireworks-Inference-Geo header from your requests.

​
Dedicated deployments

Every dedicated deployment must run in the selected region. Create it with --region set to that region, or to a single region inside it. See Regions. Check what you already have before you save the setting:
  • New deployments outside the region are rejected when you create them.
  • Existing deployments are not checked, moved, or stopped when you switch the setting on. One outside the region keeps running and keeps costing you money, but requests to it are rejected. Replace it first.
  • You can move a deployment to another region inside your residency region, but not out of it.

​
Configure in the console

Account admins can set data residency in the Fireworks console at Settings → Governances → Data Residency (open in console). Select the region and save. The console asks you to confirm that your clients already use the endpoint and models shown for that region.

​
Configure with firectl

Set the region:
Inspect the current setting:
Remove the restriction and return the account to unrestricted serving:

​
Pricing

Regional models are priced at a premium over the base serverless price for the same model. See Serverless pricing.

​
Limitations

The following are not supported while a region is set: calls are rejected, and stay rejected until you clear the setting.
  • Training. Fine-tuning and training jobs are blocked. Support is coming soon.
  • FireRouter. FireRouter can pass a request through to a third-party provider, which Fireworks cannot constrain to a region.
  • BYOC. BYOC deployments run in your own cloud account, so Fireworks cannot enforce where they run.