Skip to main content

Catalyst is now Diagrid

Catalyst and Diagrid Catalyst are now called Diagrid. Your projects, apps, keys and integrations keep working, and this page lists what was renamed, what didn't change, and the few text changes your scripts might notice.

What's renamed​

BeforeNowWhere you see it
Catalyst, Diagrid CatalystDiagridEverywhere
Catalyst CloudDiagrid CloudThe deployment model, and the free plan
Catalyst Cloud PlusCloud PlusPaid plan, in the console and on invoices
Catalyst EnterpriseEnterprisePaid plan, in the console and on invoices
Catalyst console, web console, dashboard or portalDiagrid ConsoleSign-in, billing, region and getting started pages
Catalyst in CLI help, output and errorsDiagrid CLIHelp text, prompts and error messages
Catalyst in API error messagesDiagridControl plane API errors
Catalyst MCP serverDiagrid MCP serverMCP clients and coding agents
Catalyst AssistantDiagrid AssistantThe console's assistant
Diagrid ConductorDapr Ops DashboardDapr on Kubernetes operations

The AI coding agent plugin, catalyst-ai, is being renamed too. Until then, install and use it as before.

Docs URLs​

Docs pages with Catalyst in their URL moved. The old URLs redirect permanently to the new ones, so bookmarks and links keep working.

Old URLNew URL
/concepts/what-is-catalyst//concepts/what-is-diagrid/
/operate/hosting/catalyst-cloud//operate/hosting/diagrid-cloud/
/develop/local-development/catalyst-cli//develop/local-development/diagrid-cli/
/develop/agents/catalyst-assistant//develop/agents/diagrid-assistant/
/dapr-open-source/migrate-to-catalyst//dapr-open-source/migrate-to-diagrid/
/references/catalyst/.../references/diagrid/...
/dapr-open-source/conductor/.../dapr-open-source/dapr-ops-dashboard/...

Some sample repositories in the diagrid-labs GitHub organization were renamed, for example catalyst-samples to diagrid-samples, and GitHub redirects their old names. Others, such as diagridio/catalyst-quickstarts, keep their names for now.

What didn't change​

  • APIs. API paths, request and response bodies, and API groups such as cra.diagrid.io are the same.
  • The Diagrid CLI's commands and flags. The diagrid command, its subcommands, flags, exit codes, and JSON and YAML output are the same. No command, flag or value was renamed.
  • Your credentials and endpoints. Existing API keys, access tokens and project endpoints keep working.
  • Plans. Only plan names changed. Plan and price IDs are the same.
  • Identifiers that contain catalyst. The console address catalyst.diagrid.io, the catalyst Helm chart, the Diagrid.Aspire.Hosting.Catalyst NuGet package and repositories such as catalyst-quickstarts keep their names until they're renamed at the source.

What you need to do​

Your apps and API clients need no changes. Check these if they apply to you:

  • Update your own material. Replace Catalyst with Diagrid in runbooks, internal docs and script comments, using the What's renamed table.
  • Check scripts that read the CLI's text output or match error text. For example, diagrid whoami now prints Plan: instead of Catalyst Plan:, and control plane API error messages name Diagrid instead of Catalyst. Use JSON or YAML output where a command offers it.
  • Update the control plane API specification URL if a tool downloads it. It's now served at /openapi/diagrid/controlplane; /openapi/catalyst still works and is deprecated.
  • Check the CLI release notes before you upgrade a CLI that runs in a pipeline. The CLI release notes list what changed in each version.
  • Update git remotes of renamed sample repositories with git remote set-url origin <new URL>, if you cloned one. Until then, the redirect keeps them working.