Conductor Plans and Limits
Conductor provides two plan types to accommodate individuals and teams developing with Dapr. The plan determines the features, capabilities, and limits of your Dapr Kubernetes cluster connections. Use this page to see what each plan includes, how limits are enforced, and where to go for additional capacity.
Plan offerings
Conductor supports two plan experiences, beginning with an Enterprise trial for every new account.
Conductor Enterprise
All new sign-ups begin with a 30-day trial of Conductor Enterprise, giving full access to Conductor’s features and support. Designed for organizations and teams running Dapr in production, it offers advanced functionality and higher, configurable limits across multiple clusters.
Conductor Free
After the trial ends, users automatically transition to Catalyst Online unless they choose to upgrade. This plan is ideal for individual developers working on small-scale Dapr applications within a Kubernetes environment, offering a basic feature set for development and testing.
Need help selecting the right plan or getting a pricing quote? Reach out to sales@diagrid.io.
Feature comparison and limits
Use the table below to compare how each plan handles pricing, user access, resource quotas, data retention, and networking throughput.
| Free Plan | Enterprise Trial | Enterprise Plan | Details | |
|---|---|---|---|---|
| Pricing | Free | Free for 30 days | Capacity based | See pricing page for details. |
| Plan Duration | Unlimited | 30 days | Yearly contract | |
| Maximum Clusters Allowed | 1 | 1 | Unlimited | Represents the number of connected Dapr Kubernetes clusters. |
| Users Limit | 1 | 5 | Unlimited | Free plan doesn't include RBAC for users. |
| API Keys Allowed | 0 | 10 | Unlimited | API keys are required for Kubernetes operator, non-interactive CLI, and querying Metrics API. |
| Single Sign-On | Not Available | Not Available | Available | Can be included as part of the contract. |
| Architecture Consultations | Not Available | Not Available | Available | Can be included as part of the contract. |
| Dapr OSS Support | Community | Community | Available | Can be included as part of the contract. See Dapr support page for details. |
| Conductor Support | Community | Enterprise Support | 1-hour response time | See Conductor support page for details. |
| SLA | No SLA | No SLA | 99% | |
| Applications | ||||
| Maximum Applications (per cluster) | 20 | 100 | 250 1 | An application represents an app and its associated Dapr sidecar running on a Kubernetes cluster. See below for details on how this is counted. |
| Actor Types (per cluster) | 20 | 1000 | 1000 1 | |
| Components (per cluster) | 20 | 1000 | 1000 1 | |
| Configurations (per cluster) | 20 | 1000 | 1000 1 | |
| Subscriptions (per cluster) | 20 | 1000 | 1000 1 | Does not include programmatic subscriptions. |
| Resiliency Policies (per cluster) | 20 | 1000 | 1000 1 | |
| Metrics | ||||
| Metric Series | 10K | 1M | 10M 2 | Latency metrics are not included in Catalyst Online. |
| Alert Rules | Default rules only | 100 custom rules | 100 custom rules 2 | Custom rules not included in Free Plan. |
| Alert Channels | 1 | 5 | 20 2 | Webhook and email channels not included in Free Plan. |
| Data Retention | For data collected see Security page for details. | |||
| Metrics | 12 hours | 7 days | 7 days | Higher limits available for production clusters upon request. |
| Alert Notifications | 12 hours | 7 days | 7 days | Includes logs, metrics, and advisory alert notifications. |
| Audit Logs | Not Available | 30 days | 3 months | |
| Networking | ||||
| Unique Log Entries (per hour) | 20 | 200 | 500 2 | Represents the rate at which unique log entries are ingested and displayed in Conductor. |
| Unique Metrics (per hour) | 10K | 1M | 10M 2 | Represents the rate at which metrics are ingested and displayed in Conductor. |
| HTTP API requests/min per IP | 30 | 30 | 60 | Represents the rate of requests to Conductor Console API |
| GRPC API requests/min per IP | 30 | 30 | 60 | Represents the rate of requests from Conductor agent to Conductor API |
| Metrics API requests/min per IP | 30 | 30 | 60 | Represents the rate of requests to Metrics API from Conductor Console or 3rd party monitoring tool |
| Logs API requests/min per IP | 30 | 30 | 60 | Represents the rate of requests to Log API used by Conductor Console and Conductor agent. |
note
- Unless stated otherwise, all limits are enforced at the organization level.
- 1 Limits are set according to your enterprise plan contract.
- 2 For Conductor Enterprise, limits can be increased upon request. Contact sales@diagrid.io for details.
FAQs
What is the feature difference between Conductor plans?
For information on the feature set for each Conductor plan, refer to the comparison breakdown here on the [website](https://www.diagrid.io/conductor)
How are application limits determined and enforced?
Applications exceeding the specified limits are not monitored or managed by Conductor. Selection is based on alphabetical order of the `dapr.io/app-id` annotations, with the top applications within the plan's limit being chosen. The same approach is applied to Dapr resources and metrics associated with the selected applications. Resources exceeding these limits are not tracked. Application replicas do not count toward limits, but each replica generates unique metrics and logs that do count toward metric limits.
How are networking limits enforced?
Networking limits control the amount of data transmitted or requested within a specific time period. When these limits are exceeded, network requests are rejected, which can degrade the experience (for example, outdated metrics or missing data). Stay below the thresholds noted in the table above to avoid disruptions.
How are metrics limits calculated and enforced?
Metrics limits are set at the organization level and cover series across all clusters, the control plane, and applications. Conductor prioritizes the control plane and whatever applications it manages. Metrics beyond the limit are not recorded or included in datasets, resulting in missing points or stale graphs.
How can the number of metrics be reduced?
Metric volume depends on the number of applications, features in use, and Dapr configuration. Lower the cardinality by following Dapr’s metrics guidance: https://docs.dapr.io/operations/observability/metrics/metrics-overview/.
What is the effect of connecting a Dapr Kubernetes cluster running more applications than my plan limits allow?
Conductor manages applications and resources up to the defined limits and ignores the rest. Going over limits for metrics or networking can cause degraded experiences. Upgrade to Enterprise for customizable limits, or email sales@diagrid.io to request higher quotas.
What happens when the Conductor Enterprise trial period ends?
At the end of the 30-day trial, the organization automatically transitions to Catalyst Online unless you upgrade. Features and data not included in Catalyst Online are deleted, but you continue using Conductor with the Free-plan limits.