Skip to main content

Dapr Ops Dashboard Plans and Support

Dapr Ops Dashboard is available for free. Teams running Dapr in production can add paid support for higher, configurable limits and Dapr open source support. Use this page to see what is included, how limits are enforced, and where to go for additional capacity.

Dapr Ops Dashboard Free

The Free plan carries the full Dapr Ops Dashboard feature set, including cluster advisories, advisory reports, custom alert rules, notification channels, the Kubernetes operator, managed certificates, and custom Dapr profiles. It has no time limit, and support is provided through the community.

Sign up now ↗

Need higher limits or a pricing quote for paid support? Reach out to sales@diagrid.io.

Feature comparison and limits

Use the table below to compare how the Free plan and paid support handle pricing, user access, resource quotas, data retention, and networking throughput.

Free PlanPaid SupportDetails
PricingFreeCapacity based
Plan DurationUnlimitedYearly contract
Maximum Clusters Allowed1020 1Represents the number of connected Dapr Kubernetes clusters. Production and non-production clusters have separate allowances: 5 and 5 on Free, 10 and 10 with paid support.
Users Limit2020 1Role-based access control applies on every plan.
API Keys Allowed520 1API keys are required for Kubernetes operator, non-interactive CLI, and querying Metrics API.
Single Sign-OnNot AvailableAvailableOne SSO connection per organization. Available on request for organizations that need it.
Architecture ConsultationsNot AvailableAvailableCan be included as part of the contract.
Dapr OSS SupportCommunityAvailableCan be included as part of the contract. See Dapr support page for details.
Dapr Ops Dashboard SupportCommunity1-hour response timeSee Dapr Open Source for paid support details.
SLANo SLA99%
Applications
Maximum Applications (per cluster)250250 1An 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)10001000 1
Components (per cluster)10001000 1
Configurations (per cluster)10001000 1
Subscriptions (per cluster)10001000 1Does not include programmatic subscriptions.
Resiliency Policies (per cluster)10001000 1
Metrics
Metric Series1M10M 2On the Free plan, latency histogram series are dropped before storage, so latency percentiles are unavailable.
Alert Rules25 custom rules100 custom rules 2
Alert Channels1020 2Webhook and email channels are available on every plan.
Data RetentionFor data collected see Security page for details.
Metrics7 days30 daysHigher limits available for production clusters upon request.
Alert Notifications5 days5 daysIncludes logs, metrics, and advisory alert notifications.
Audit LogsAvailable3 monthsAudit logs are readable on every plan.
Networking
Unique Log Entries (per hour)20800 2Represents the rate at which unique log entries are ingested and displayed in Dapr Ops Dashboard.
Unique Metrics (per hour)10KUnlimited 2Represents the rate at which metrics are ingested and displayed in Dapr Ops Dashboard.
HTTP API requests/min per IP3060Represents the rate of requests to Dapr Ops Dashboard Console API
GRPC API requests/min per IP3060Represents the rate of requests from Dapr Ops Dashboard agent to Dapr Ops Dashboard API
Metrics API requests/min per IP3060Represents the rate of requests to Metrics API from Dapr Ops Dashboard Console or 3rd party monitoring tool
Logs API requests/min per IP3060Represents the rate of requests to Log API used by Dapr Ops Dashboard Console and Dapr Ops Dashboard agent.
note
  • Unless stated otherwise, all limits are enforced at the organization level.
  • 1 Limits are set according to your support contract.
  • 2 With paid support, limits can be increased upon request. Contact sales@diagrid.io for details.

FAQs

How are application limits determined and enforced?
Applications exceeding the specified limits are not monitored or managed by Dapr Ops Dashboard. 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. Dapr Ops Dashboard 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?
Dapr Ops Dashboard manages applications and resources up to the defined limits and ignores the rest. Going over limits for metrics or networking can cause degraded experiences. Paid support comes with customizable limits, so email sales@diagrid.io to request higher quotas.