Skip to main content

Operating Catalyst

Diagrid Catalyst is a centralized platform for running durable workflows, AI agents, MCP servers, and Dapr applications in production, built on the open-source Dapr runtime. As an operator, you deploy it into your own infrastructure — any cloud or on-premises — and run it as a shared, governed platform for your teams.

Operating Catalyst spans two levels:

  • Platform operations — install and configure Catalyst, manage regions, identity, and access, and create projects for teams.
  • Project operations — configure resources, operate workloads, and observe applications, workflows, and agents within a project.

Install and set up Catalyst platform​

As a platform engineer, you stand up Catalyst for the organization: you install and configure the platform on your own infrastructure — provisioning Kubernetes clusters, integrating with your cloud, and connecting it to your observability backend — and set up user identities and access. You then create isolated projects and hand them to teams.

  1. 1
    Choose how to host Catalyst — compare Catalyst Cloud, Enterprise Dedicated, Self-Hosted, and Air-Gapped, then configure it for Azure, AWS, or GCP.
  2. 2
    Set up regions — create the data-plane locations that host your projects.
  3. 3
    Create projects for teams — give each team, environment, or application an isolated project with its own endpoints.
  4. 4
    Set up identity and access — invite users, assign roles, and create API keys for automation.

Operate workflows and agents in a project​

Projects provide isolated identities, resources, policies, and observability boundaries for teams and environments. Inside a project, you connect your applications and agents, configure their backing infrastructure, and lock them down with access policies and secrets — then operate your workflows and agents at runtime, and observe and troubleshoot everything in one place.

Connect with App IDs

Register each workload with its own identity, API token, runtime spec, autoscaling, and health checks.

Connect to backing infrastructure

Connect applications to state stores, message brokers, secret stores, and external services, with secret extraction and resiliency policies.

Enable managed services

Turn on Catalyst-hosted Pub/Sub, Key/Value, and Workflow stores per project, with no infrastructure to provision.

Manage secrets

Use transparent secret extraction, or bring your own AWS Secrets Manager, Azure Key Vault, or HashiCorp Vault.

Operate workflows

Search, diagnose, and act on durable workflow instances — pause, resume, terminate, raise events, or purge.

Operate agents

Inspect running AI agents, review executions and tool calls, and recover failed or stalled runs.

Observe workloads

Track every workload with metrics, API logs, the apps graph, and OpenTelemetry tracing — no instrumentation required.

Automate with the CLI and APIs​

Every task above is scriptable. Manage Catalyst resources as code with declarative management (diagrid apply and export over YAML in Git), drive the same surface from the diagrid CLI, or call the Catalyst APIs directly for GitOps, CI/CD, and custom tooling.

Next steps​

Last updated on