Skip to main content

Platform setup

Stacklok Enterprise

Stacklok Enterprise ships as one umbrella Helm chart that bundles every platform component, so you install the whole platform in a single Helm release rather than wiring up each chart yourself.

Learn more about Stacklok Enterprise.

How the platform fits together​

The platform components run together in your Kubernetes cluster. The Enterprise Manager serves policy to the Stacklok clients, the Registry Server holds the approved MCP server and skills catalog, the Enterprise Cloud UI manages that catalog, and the ToolHive Operator reconciles MCP server workloads. Your identity provider authenticates every client and component.

Deployment sequence​

When you are ready to deploy, work through these steps in order. Each links to its detailed guide.

  1. Configure identity. Set up your identity provider (authorization server, audiences, scopes, claims, and OAuth clients) so the platform components and clients can authenticate. Do this first, because deployment wires in the client IDs and audiences you create here. See Configure platform identity.
  2. Deploy the platform. Install the umbrella chart, wiring in the identity values from the previous step. The chart deploys the ToolHive operator, the Enterprise Manager, the console, and the Registry Server as subcharts. See Deploy the platform. Before you install, run preflight checks to catch cluster problems that would otherwise surface partway through the release.
  3. Enable the gateways you need. Both are off by default. See Configure the AI Gateway and Configure the MCP gateway.
  4. Populate the directory. Provision users and groups from your identity provider, since access and budgets are granted to them. See SCIM provisioning.
  5. Configure policies. Use the Enterprise Manager to pin the registry, control non-registry servers, and standardize telemetry. See Configure policies.
  6. Set up authorization. Map identity-provider groups and roles to MCP access with the enterprise authorization custom resources. See Enterprise authorization.
  7. Roll out the clients. Distribute the Stacklok CLI to your users, and point them at Connect a client for their editors and agents.
  8. Verify end to end. Sign in to the console and confirm the path from catalog to client.

Contents​