Self-managed BYOC
In a self-managed BYOC region, you deploy the Catalyst data plane onto a Kubernetes cluster you run, and manage it through the Diagrid-hosted Catalyst control plane. This combines a streamlined cloud management experience with the security, control, and flexibility of keeping your applications and data in your own environment.
Your applications connect directly to the Catalyst region over your private network. That keeps data local and removes Diagrid Cloud from the critical path of your application's data flow: Diagrid Cloud manages the lifecycle of resources within your region, while your application availability and reliability remain fully under your control.
If you'd rather Diagrid provision and operate the region inside your cloud account, see Managed BYOC — it needs no cluster of your own.
Choose your path
How you deploy depends on what you're doing:
| Your situation | Start here |
|---|---|
| Evaluating Catalyst, or deploying onto a cluster you already have | Quick deployment — diagrid region deploy takes you from zero to a connected region against a local kind cluster or an existing EKS, AKS, or GKE cluster. |
| Building a production region on AWS | AWS deployment — a reference architecture with Terraform for a private VPC and EKS. Or deploy through the AWS Marketplace. |
| Building a production region on Azure | Azure deployment — a reference architecture for a private AKS cluster behind Azure Firewall. Or deploy through the Azure Marketplace. |
Whichever path you take, read Production planning before sizing a production region — it covers cluster requirements, sizing profiles, high availability, and private registries.
Start using the region
Once your region is deployed and reports as connected, it behaves like any other Catalyst region. Create a project in it:
diagrid project create my-project --region my-region
To make it the default region for every new project in your organization, use diagrid region use.
From here, run any quickstart against your new project to verify the region end to end — the workflow and agent quickstarts exercise the data plane you just deployed.
Operate the region
- Lifecycle management — supported versions, upgrade and rollback, join-token rotation, region updates and deletion.
- Architecture — components, data flow, outbound connections, network policies, and regional PKI.
- Observability — forward metrics, traces, and logs to your own OpenTelemetry backend.
- Helm reference — every configuration option in the Catalyst Helm chart.
Support plans
A self-managed BYOC region can be purchased with the select or premium support plan, set with the --support-plan flag on diagrid region create. Regions running on your own infrastructure start at select.
See Plans & support for what each plan covers.