Limits and Restrictions
Conductor provides two plan types based to accomodate individuals and teams developing with Dapr. The plan you choose determines the features, capabilities, and limits of your Dapr Kubernetes cluster connections. This page guides you through the available plan offerings and their associated quotas and limits.
Plan offerings
- Conductor Free: This plan is designed for individual developers working on small-scale Dapr applications within a Kubernetes environment. It offers a basic set of features suitable for development and testing.
- Conductor Enterprise: Aimed at organizations and teams managing and operating Dapr applications in a production environments. The Enterprise plan includes the features of the Free plan, with more advanced operations functionality and higher, adjustable limits to support organizational needs.
For individual experimentation and early development, start with the Free plan. For teams looking to run Dapr in a production environment, start with the Enterprise trial. Should you require assistance in selecting the appropriate plan or need a pricing quote, reach out to us at sales@diagrid.io.
Feature comparison and limits
The table below is a comparison of features and limits between the Conductor plans.
| Free Plan | Enterprise Trial | Enterprise Plan | Details | |
|---|---|---|---|---|
| General | ||||
| 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 support page for details. |
| Conductor Support | Community | Enterprise Support | 1-hour response time | See 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 the Free Plan. |
| 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 page | |||
| 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. |
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
Q: What is the feature difference between Conductor plans?
For information on the feature for each Conductor plan, refer to the Conductor documentation.
Q: 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 dapr.io/app-id annotation, with the top applications within the plan's limit being chosen. This approach is similarly applied to Dapr resources and metrics associated with the selected applications.
Resources exceeding these limits are not tracked by Conductor. Note that while application replicas don't count towards limits, they do contribute to metric limits, as each replica generates unique metrics and logs.
Q: How are metrics limits calculated and enforced?
Metrics limits are set at an organizational level, encompassing metric series across all clusters, control plane, and applications. Conductor prioritizes metrics from the control plane and the applications it manages. Metrics exceeding the set limits are not recorded or included in Conductor datasets. This may result in missing data points or outdated metrics graphs.
Q: How can the number of metrics be reduced?
The volume of metrics generated by a Dapr cluster varies based on the number of applications, the features utilized, and the Dapr configuration. Adjusting Dapr to a lower metric cardinality, as outlined in the Dapr documentation, can help in reducing metric reporting.
Q: 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. This can lead to a degraded user experience, resulting in outdated metrics views or a lack of data. Managing these limits effectively is essential to avoid such issues and maintaining a continuous data flow.
Q: What is the effect of connecting a Dapr Kubernetes cluster running more applications than my plan limits allow?
Conductor will manage applications and resources within the established limits and ignore the excess workloads and resources. Exceeding these limits in terms of metrics and networking can lead to a degraded user experience. In such situations, it's recommended to upgrade to the Enterprise plan, which offers customizable limits. To increase quotas in the Conductor Enterprise plan contact sales@diagrid.io.
Q: What happens when the Conductor Enterprise trial period ends?
Following the conclusion of the trial period, a 7-day grace period is granted for data retention. After this period, all data, including the organization and user account, is permanently deleted. Subsequently, you have the option to sign up for the Free plan.