Skip to main content

Managed services

Diagrid-managed services are backing infrastructure that Diagrid provisions, runs, scales, and patches for you inside your project boundary. Your workloads consume them through the standard Dapr building-block APIs (state, pub/sub, workflow), in the same way they would consume a bring-your-own component.

If you are new to Diagrid's identity model, IDs are the per-workload identities that components and managed services bind to.

What "managed" means​

With a component you bring your own Redis, Postgres, Kafka, or Vault; you own the connection string, credentials, capacity planning, and upgrades. With a managed service Diagrid owns all of that. You enable the service on the project, and it is immediately available to every workload in that project. Diagrid generates and maintains the underlying component on your behalf, so you do not author YAML or rotate credentials for it.

Managed services are intentionally opinionated: one instance per project, one set of capacity limits, and fixed component names where one is needed.

The catalog​

📣Managed Pub/Sub

Diagrid-hosted message broker for publish/subscribe messaging. Default component name: pubsub.

🗂️Managed KV

Diagrid-hosted state store for key-value workloads, transactions, and queries. Default component name: kvstore.

🔁Managed Workflow Store

Diagrid-hosted state store tuned for durable workflow execution, history, and timers. Wired implicitly to your project's workflow apps; there is no user-facing component name to reference.

Each service implements the same Dapr API contract as its BYO counterpart, so application code that targets the Dapr State or Pub/Sub SDK works against either without modification.

Two apps using managed servicesDiagridOrders appBilling appOrders IDManaged Pub/SubBilling IDManaged KV
Two apps using managed servicesThe orders app writes to managed KV and publishes to managed Pub/Sub; the billing app receives the messages.

Managed vs bring-your-own​

DimensionManaged serviceBring-your-own component
ProvisioningManaged Pub/Sub and Managed KV are enabled per project with one CLI flag; the Managed Workflow Store is on by default. No infrastructure to stand up.You provision the underlying store or broker and supply its connection details.
CredentialsNone to manage. Diagrid handles internal authentication.You supply connection strings and secrets; Diagrid extracts sensitive fields into a managed secret store.
Component nameFixed for Managed Pub/Sub (pubsub) and Managed KV (kvstore); the Managed Workflow Store is wired implicitly and has no user-facing name.You choose the name, the type (e.g. state.postgresql, pubsub.kafka), and any number of instances per project. Only one component per project can set actorStateStore to true, and none can while the Managed Workflow Store is enabled.
Capacity ceilingFixed per-project limits. See Plans & Support.Bounded by the infrastructure you provisioned.
ScopingManaged Pub/Sub and Managed KV are provisioned as real components (pubsub, kvstore) with an empty scopes field, so every app can use them by default; you can later restrict them like any BYO component. The Managed Workflow Store is wired implicitly and is not scopable.Restricted to the apps listed in the component's scopes. See Components.
Typical useDevelopment, demos, small-to-medium production workloads, workflows.Production workloads with existing infrastructure, strict tenancy isolation, or capacity beyond the managed tier.
MigrationPoint your app at the new component's name in place of pubsub or kvstore: a configuration change if the name comes from configuration, a code change if it is written in the code. A project has one workflow store, so your own store replaces the managed one rather than adding a second. Diagrid still keeps a record of each run, including its input and output, in a database it manages, for search and the console. The record stays in the data plane. If you run the region yourself, that database is yours. See Migrating to your own infrastructure.The reverse: point your app at pubsub or kvstore. For workflows, remove the actorStateStore component, then turn the Managed Workflow Store back on.

Lifecycle​

How provisioning works​

Managed Pub/Sub and Managed KV are opt-in: they are set when the project is created and cannot be added afterwards, from either the CLI or the Diagrid Web Console. The Managed Workflow Store is on by default for every new project in a region that supports workflows, and can be turned on or off later. To run workflows on a store of your own instead, see Use your own workflow store. Once enabled, the service appears as a normal component bound to every app in the project. See Manage managed services for the exact commands.

How scaling works​

Each managed service has a fixed per-project capacity ceiling. Diagrid handles internal scaling, upgrades, and patching within that ceiling, so there are no instance counts, replicas, or autoscaler thresholds to tune. Workloads that approach the ceiling should migrate to a BYO component.

Retention​

  • Managed Pub/Sub. Messages are retained per topic up to a size cap (50 MB per topic by default) with no time-based expiry. Within that window, subscribers can read at their own pace; once a topic exceeds the size cap, the oldest messages roll off in Kafka-style log order.
  • Managed KV. Values are persisted until you delete them or until their TTL expires. The store supports the full Dapr State API, including transactions and queries.
  • Managed Workflow Store. Execution state, history, and timers are retained for the lifetime of each workflow instance, until you purge the instance.

See Plans & support for the current size limits.

Access scoping​

Managed services live at the project level: enabling one makes it available to every app in that project by default. The two storage services that surface as components (Managed Pub/Sub and Managed KV) ship with an empty scopes field, which Diagrid interprets as "every app"; you can later restrict access using the standard component-update flow described in Components. The Managed Workflow Store is wired implicitly and stays project-wide.

Cross-project access is never granted. A managed service in one project is not reachable from apps in another project; the project boundary is the unit of isolation.

Limits and quotas​

Managed services are sized for development and small-to-medium production workloads. The ceilings for each plan are listed in Plans & support; in a dedicated or BYOC region the ceiling depends on the storage capacity allocated to the region during installation.

What's next​