Quick Deployment
The fastest way to get started with Catalyst Enterprise Self-Hosted is to deploy a region with diagrid region deploy. This is ideal for understanding what the platform offers, integrating your applications, and getting familiar with the management experience. Once you're comfortable, plan a production installation with Production Planning.
diagrid region deploy is best suited for evaluating the platform. For production deployments, follow the Production Planning guidance and adopt a deployment method tailored to your organization's infrastructure, security, and operational requirements.
Before you begin
- 1Create a Diagrid Cloud account, if you don't have one already. Sign up for free at catalyst.diagrid.io.
- 2Install the Diagrid CLI — see the Diagrid CLI overview, then authenticate:
diagrid login - 3Install the local prerequisites below.
Deploy a Catalyst region
The diagrid region deploy command is the fastest path from zero to a connected Catalyst region — it works against a local kind cluster or any existing Kubernetes cluster (EKS, AKS, GKE, or generic).
🧭Interactive (recommended for first run)
Launches a TUI that walks you through picking a region name and target cluster. Best when you're exploring Catalyst for the first time.
diagrid region deploy⚡Non-interactive (scripts & CI)
Skip the TUI and pass a region name plus a target flag. Ideal once you know which cluster you want to use.
diagrid region deploy my-region --create-clusterWhat diagrid region deploy does
- 1Registers the region in Diagrid Cloud, or connects to an existing region with the same name.
- 2Prepares the cluster — creates a local kind cluster if requested, or targets the Kubernetes context you selected.
- 3Detects the cloud provider (EKS, AKS, GKE, kind, or generic) and configures the gateway
Serviceaccordingly — aNodePortfor kind, or aLoadBalancerwith the right provider annotations for cloud clusters. - 4Installs the Catalyst Helm chart, or upgrades an existing release in place when re-run against the same cluster.
- 5Waits for the region to connect and prints the next steps (quickstarts, endpoint URLs) so you can start using it immediately.
The defaults generated by diagrid region deploy are opinionated toward testing and PoCs. For custom setups, pass --values-file ./my-values.yaml to layer your own Helm values on top — see the Helm Reference for the full set of options.
Route projects to your new region
diagrid region deploy does not mark the new region as the organization default. To use it for new projects, either set it as the org default once, or pass --region on each diagrid project create:
# Option A — set as default for the organization (applies to all future projects)
diagrid region use my-region
# Option B — pass --region when creating a project
diagrid project create my-project --region my-region
See Set the organization default region for details.
Next steps
- Production Planning — size your infrastructure for a production installation.
- AWS Deployment / Azure Deployment — reference architectures for deploying on your cloud.