1. You choose where each runs
    1. Control planeConfiguration and policy definitions
    2. Data planeWhere traffic is enforced
  2. Your upstreamsLLMs, MCP servers, and APIs
Self-hosted in your VPC, hosted by Postman, or hybrid: the endpoint your applications call stays the same.
3
deployment models
Same
endpoint in every model
Same
policies, brokering, and observability

The problem

Security reviews often rule out SaaS-only gateways, especially when agents need to reach private APIs and credentials must not leave your environment.

How it works

Fabric separates a control plane (configuration and policy definitions) from a data plane (the traffic path where enforcement happens). You decide where each one runs.

What you get

Self-hosted in your VPC

Run the data plane inside your own Kubernetes cluster or VM fleet.

Postman-hosted

Let Postman operate it for you with regional data planes.

Hybrid

Control plane managed by Postman; data plane stays in your cloud.

Bring every AI interaction under control

Connect your first model, MCP server or internal API and apply consistent governance from one gateway.