Dash0 review

Dash0 is an OpenTelemetry-native observability platform for software teams. It brings logs, metrics, traces, profiles, events and real-user monitoring data into one place, with the product description saying the signals are stored in your cloud. Teams can query those signals, manage which telemetry they keep, and use Configuration as Code to manage dashboards, rules and settings through editors and release pipelines.

The product also reaches beyond observability. Dash0 describes AI software development insights for monitoring coding agents and connecting production feedback to code, plus production automation for root-cause analysis, fixes and tuning. Those are product claims; the published pricing details do not specify which AI or automation features are included in the Telemetry charges.

The pricing page lists usage-based Telemetry pricing, a 14-day unlimited free trial with no credit card required, and no fixed monthly starting price. It describes monthly billing and lists no annual option.

Dash0’s clearest switching argument is its OpenTelemetry-native approach. Teams already instrumenting with OpenTelemetry can use a platform built around those signals, rather than treating telemetry as a vendor-specific format. In one Reddit thread, a Dash0 user said the move from Datadog also pushed their team toward OpenTelemetry and made them feel they could switch platforms later. That is one user’s view, not a guarantee that every setup will move cleanly.

The product’s breadth may also reduce the need to split basic observability across separate tools. Its feature list covers logs, metrics, traces, profiles, events and RUM, alongside AI development insights and production automation. SignalStore is described as storing OpenTelemetry-native signals in your cloud; SignalControl lets teams select telemetry to keep, with storage costs applying to what they retain.

• Configuration as Code can fit teams that manage dashboards, rules and settings in editors and release pipelines.
• Pricing is metered against ingestion and storage, rather than a published fixed monthly starting price. That makes the bill depend on the signals a team sends and retains.
• One Reddit commenter who switched from Datadog reported paying about half as much and said Dash0 covered their needs, while noting they missed some minor features. Treat that as an individual report, not a general price comparison.

Usage pricing needs close attention: Dash0 charges separately for ingesting and storing several signal types, so sending data and keeping it both affect the bill. According to the pricing page, spans, logs and web events cost $0.060 per million ingested and $0.540 per million stored, with 30-day retention. Metric data points cost $0.020 per million ingested and $0.180 per million stored, with 13-month retention. Synthetic API checks are $0.20 per thousand stored, and session replays are $2.00 per thousand stored; both list 13-month and 30-day retention, respectively.

The listed Telemetry pricing gives rates and retention periods, but no included volume allowance or fixed monthly price. We would not budget from a single headline rate: estimate ingestion and storage separately using your expected signal volume. Agent0 Credits are a separate metered monthly add-on at $0.60 per credit; the published pricing does not state how many credits particular tasks use. The pricing page describes monthly usage pricing and lists no annual billing option. Finally, one Reddit user said Dash0 lacked some minor Datadog features for their needs, a reminder to check feature fit before switching.

Dash0 does not publish a flat monthly entry price or an annual billing option. Its pricing page describes monthly, usage-based billing under one “Telemetry” plan, so there is no published tier-to-tier price jump to compare. Instead, charges stack by signal and by ingestion versus retention: spans, logs and web events cost $0.060 per million ingested plus $0.540 per million stored, with 30-day retention. Metric data points cost $0.020 per million ingested plus $0.180 per million stored, with 13-month retention. Synthetic API checks cost $0.20 per thousand stored, with 13-month retention; session replays cost $2.00 per thousand stored, with 30-day retention. Storage charges are the gotcha: ingestion alone does not represent the bill. Agent0 Credits are an add-on at $0.60 per credit, metered monthly. Dash0 lists a 14-day unlimited free trial with no credit card required. For budgeting, model each signal and retention period; a predictable fixed monthly total is not published.

Dash0’s OpenTelemetry-native approach may reduce dependence on a vendor-specific collection format, and SignalStore stores signals in your cloud. But the published materials do not publish migration tooling, export formats, or an estimate of migration effort for existing dashboards, alert rules, historical data, or agent settings. Configuration as Code lets teams manage dashboards, rules, and configurations in editors and existing release pipelines; portability of every object is not documented.

Before switching, inventory signal volumes and retention needs: Dash0 bills ingestion and storage separately. Check whether your current provider can export the history you need. Before leaving Dash0, confirm export paths and any cloud-storage or query dependencies with the docs or vendor; those specifics are not published here. We have no Reddit posts or comments in the published sources, so we can’t attribute common reasons for leaving to users. The clearest fit risk is pricing: teams that need flat-rate bills or do not want metered ingestion and storage may prefer another platform.