Skip to main content

Enterprise Tier

Project and data plane management

Isolated projects are created here, the gateways that serve them are provisioned, the data planes that host those gateways are deployed, and runtimes are moved between data planes without disruption. Models must be enabled in the organization catalog before they can be granted to a project; that catalog work is covered in Provision models and providers.

Three objects underpin these guides; the full treatment is in Key concepts and Planes and core components.

  • A project is the logical boundary that owns models, API keys, Model Context Protocol (MCP) servers and profiles, routing and policy, budgets, and members. It is also the isolation boundary: each project sees and serves only its own configuration.
  • A gateway is a single inference endpoint (one customer-facing URL) provisioned by a data plane and mapped to exactly one project. By default a project gets one gateway when a data plane is selected; on Enterprise, additional gateways can optionally be attached for high availability (see Gateway sets and DNS-level failover). A project has no endpoint until at least one gateway is provisioned for it.
  • A data plane is the layer, deployed in a Kubernetes cluster, that provisions and manages gateways. One data plane can host many gateways, and one management plane can manage many data planes.

Set up a project

Create and delete a project

Create the project with the wizard, granting members, models, and MCP servers in one pass, or delete a project when it is no longer needed.

Provision a gateway for a project

Give the project a live inference URL by selecting a data plane, which provisions the project's gateway.

Manage project Users and access

Add members, assign roles, and keep project access separate from data-plane operations.

Issue a project-scoped API key

Create a key that works only against one project's gateway.

Grant MCP servers and profiles to a project

Scope MCP servers and profiles to a project under the same isolation as models.

Operate data planes

Deploy and register a data plane

Provision a data plane, install its credential, and connect it to the management plane.

Manage multiple gateways on a data plane

Review the gateways a single data plane provisions and manages after projects select it.

Migrate a gateway or upgrade its runtime

Move a gateway between data planes, or upgrade it in place, without changing its URL.

Gateway sets and DNS-level failover

Run a project on several like-configured gateways and fail over between them with customer-managed DNS.