Skip to Content
Control & ConfigurationGateway Provider Configuration

Gateway Provider Configuration

A Vercel AI Gateway connection is a customer-owned BYOK provider. Add it in Connections with your Gateway API key. Steinkauz AI does not provision a platform Gateway, and platform keys are not a fallback for that connection.

If you add a Gateway, you can configure how it chooses and uses AI providers. These settings apply to your active organization.

Owners and admins configure Gateway settings for all members.

Provider ordering

You can set the order in which providers are tried when a model is requested. Providers at the top of the list are preferred; others are used if needed (e.g. for fallback or capacity). This lets you favor certain providers or regions.

  • In Connections, open the Gateway’s Provider options and find Provider Order.
  • Add or reorder the providers you want. Providers not in the list may still be used after the ones you specified.

Provider whitelist

You can whitelist which backends the Gateway may use for models. When the whitelist is empty, all routed backends are allowed. When you add backends, only those appear in your model catalog and routing context. This is useful for compliance, cost control, or vendor preference.

  • In the Gateway’s Provider options, find Provider Whitelist.
  • Leave the list empty to allow every gateway backend, or add providers to limit to that set.

Note: Provider order and provider whitelist are mutually exclusive in the UI: you configure one or the other, not both at once. Follow the in-app labels.

Zero Data Retention

A customer-owned Gateway connection can enable Zero Data Retention (ZDR) where the Gateway account supports it. The request option restricts Vercel’s routing to its ZDR set. The applicable agreements define the scope and exceptions; this option does not disable the Platform’s own transcript or evidence retention.

  • In the Gateway’s Provider options, find Zero Data Retention.
  • Turn it on to request ZDR routing. Turning it off does not override ZDR enforced by the Gateway account or virtual model, or any configured provider whitelist.

For more on what zero data retention means for your data, see Zero Data Retention.

Execution environment

Your Gateway connection appears as one provider in Connections. Set its execution environment (E-class) to reflect how you treat Gateway-routed traffic for data routing policy.

The usual default for a public Gateway is E1 (Public managed). Gateway is treated as a single hop in routing. Steinkauz AI does not classify each downstream vendor inside the gateway chain separately.

Execution environment complements ZDR and provider order: even with ZDR enabled, the D×E matrix still governs whether a request’s effective data sensitivity may be sent to the Gateway environment you configured.

Where to configure

All of the above are Gateway options on the customer-owned instance. Open Connections (or Provider options for that Gateway) and adjust provider order, whitelist, and zero data retention as needed. Changes apply to new requests immediately. Inference fails closed if the instance has no customer API key.

Provider create, update, and delete appear in Change history. Provider API keys are never stored in that log. See Configuration Audit.

For other providers, see BYOK Provider Configuration.

Model metadataAvailable Providers