Choose a deployment model
Fabric AI Gateway always has two parts: a control plane, where you configure routes, plugins, and access, and a data plane, which carries your traffic. The plan you choose decides where the data plane runs. On the Free plan, Postman hosts both parts. On the Enterprise plan, Postman hosts the control plane and you run the data plane in your own VPC. This topic explains what runs where, what you operate, and how the two parts stay in sync.
Compare the plans
Fabric AI Gateway offers Free and Enterprise plans. Free is hosted in Postman’s cloud. Enterprise uses a hybrid deployment: the control plane stays in Postman cloud, and the data plane runs in your VPC. See the pricing page for plan details.
Compare the deployment models
There’s no fully self-managed option. The control plane always runs in Postman cloud.
What the console shows
The console adapts to where your data plane runs. When you run your own data plane, Admin also shows Gateway health, Single sign-on, Vaults, and Data plane. Some features need your own data plane, because they rely on resources in your network. For example, JWT Auth validates tokens against an identity provider that you register with your data plane, so it isn’t available on a hosted data plane. For details, see Authenticate requests with JWT Auth.
How the data plane connects to the control plane
On the Enterprise plan, your data plane connects to the control plane as follows:
- Enrollment. The data plane enrolls with the control plane to get its identity. It generates its own private key, which never leaves the data plane, and receives a certificate that names your organization and that node. It can enroll in either of two ways:
- Workload attestation: on Kubernetes, the data plane enrolls with its service account token. Quickstart: Run a data plane in your VPC uses this method.
- Enrollment token: your admin creates a short-lived enrollment token in the control plane, and the data plane uses it once. A token is valid for 10 minutes by default.
- Outbound network connection. The data plane opens a network connection to the control plane, secured with mutual TLS (mTLS) using that certificate. The network connection is always outbound. The control plane never connects into your network, so you don’t open any inbound ports to Postman.
- Configuration sync. When you save a change in the console or through the Admin API, the control plane pushes it to your data plane over that connection. Usually only the changed items are sent. The data plane checks the update, applies it, saves a copy to disk, and confirms the version that it applied.
- Heartbeats and renewal. The data plane sends a heartbeat every 15 seconds by default, so the control plane can show node health. It renews its certificate by itself before the certificate expires.
For the setup steps, see Connect a data plane.
When the control plane is unreachable
The control plane never sits in the request path, so traffic doesn’t depend on it. If your data plane loses its network connection to the control plane, the following happens:
- The data plane keeps serving traffic with the last configuration that it applied.
- It reconnects by itself, waiting a little longer between attempts, up to about 30 seconds. When it’s back, it catches up from the version that it last applied.
- Changes that you make in the meantime reach the data plane only after it reconnects.
- If a data plane container restarts while the control plane is unreachable, it starts from the configuration saved on its disk. A new pod, such as one added by scaling out, a rollout, or a node failure, has no saved configuration until it reaches the control plane. To keep the saved configuration on a persistent volume for each pod, use the distributed store (
distributed.enabled).
If the data plane stays disconnected until its certificate expires, it keeps serving its last configuration but can’t reconnect. To reconnect it, restart it:
- A data plane that enrolls with its Kubernetes service account token enrolls again by itself when it starts.
- A data plane that enrolled with an enrollment token needs a new token from an admin before you restart it.
What leaves your network
On the Enterprise plan, the data plane sends the control plane the following over its connection:
- Configuration acknowledgments and heartbeats.
- Usage counts, such as how many requests each connection handled, sent about every 60 seconds by default.
- A metering record for each LLM request, including the consumer, provider, model, token counts, request and trace IDs, route, and any error message. Prompts and responses aren’t included.
- Health reports, sent periodically. They include upstream health counts and name a sample of upstreams that are unhealthy or recently returned errors.
- Budget totals.
Upstream secrets don’t leave your network. The control plane stores only references to them, and the data plane reads the values from your own vault.
The data plane exports traces, metrics, and logs through OpenTelemetry to the backend that you configure. The console’s Traces and Analytics pages show your traffic only when that backend is Postman’s.
Next steps
- To size and plan your own data plane, see Plan a deployment.
- To see what happens to each request on the data plane, see Follow a request through the gateway.
- To get started on the hosted data plane, see Quickstart: Send your first request on the hosted gateway.
- To review how Fabric protects data and secrets, see Review security and data handling.

