Catalyst Dedicated Cloud
Catalyst Dedicated Cloud gives your organization a single-tenant Catalyst region that Diagrid provisions and operates in a Diagrid-owned cloud account. You get the isolation and capacity of your own data-plane cluster with zero infrastructure responsibility: the networking, the Kubernetes cluster, the storage, and the Catalyst data plane itself are all created and managed by Diagrid.
Choose Dedicated Cloud when you need single-tenant isolation and production sizing without operating any infrastructure. If your data plane must run inside your own cloud account instead, use BYOC.
What you choose, what Diagrid manages
When you create a dedicated region, you make four choices:
- Cloud provider — AWS or Azure.
- Cloud region — where the region runs (for example
eu-west-1on AWS,westeuropeon Azure). The cloud provider and cloud region are fixed at creation time. - Sizing tier —
small,medium,large, orxlarge. The tier sets the compute and storage capacity of the region, and you can move to a larger tier at any time. - Networking —
publicorprivate. See Networking.
Diagrid manages everything else: provisioning the infrastructure, running and upgrading the Catalyst data plane, and scaling it within the tier you selected.
Networking
Dedicated regions support two networking postures:
- Public — your applications connect to the region's endpoints over the internet, protected by TLS and Catalyst authentication.
- Private — the region is exposed through AWS PrivateLink or Azure Private Link, so traffic between your applications and the region stays on the cloud provider's private network. Only the AWS account or Azure subscription you allow can connect.
You can switch a region between public and private networking after creation with diagrid region update.
Create a dedicated region
Create a dedicated region from the Catalyst console — under Regions, select Create region and choose Dedicated Cloud — or with the CLI:
diagrid region create my-region \
--dedicated \
--cloud aws \
--region eu-west-1 \
--tier small
Unlike self-managed BYOC, there is no join token and nothing to install: Diagrid provisions the infrastructure and joins the region to your organization automatically.
Track provisioning
Provisioning typically takes 20–40 minutes. Watch progress with:
diagrid region get my-region
The region moves through these phases:
| Phase | What's happening |
|---|---|
Pending | The request is accepted and queued for provisioning. |
Provisioning | Diagrid creates the cloud infrastructure — networking, identity, and the Kubernetes cluster. |
Deploying | The Catalyst data plane is installed on the new cluster. |
Joining | The region connects to the Catalyst control plane and your organization. |
Ready | The region is available — you can create projects in it. |
The region's status also reports a progress percentage and, if provisioning fails, a message explaining why.
Start using the region
Once the region reports Ready, 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 provisioned.
Resize or change networking
Only the sizing tier and networking posture can change after creation:
diagrid region update my-region --tier medium
diagrid region update my-region --networking private
Moving to a larger tier is always allowed. Downgrades that would shrink the region's storage are rejected.
Support plans
A dedicated region can be purchased with the standard, select, or premium support plan, set with the --support-plan flag on diagrid region create. The region's price reflects its sizing tier and support plan together, so the support plan is part of what you pay for the region rather than a separate add-on.
See Plans & support for what each plan covers.