Dash0

Name: Dash0
Brand: Dash0
Rating: 4.8 (41 reviews)

AI NativeLeader

The first full OpenTelemetry-Native Observability tool out there. We make Observability easy for every developer.

Est 2023|Valuation $1B|Raised $154.4M|24 Ref Customers

LinkedIn 17K|Website|Web traffic 68K|FTEs 200|HQ New York, NY

MarketsInfrastructure Monitoring Observability Platform Application Performance Monitoring (APM)

Published Oct 22, 2026

01Common complaints

- If you need ultra-mature “everything included” enterprise features on day one - Datadog and Dynatrace generally win on breadth, integrations, and long-established enterprise references. - If your organization is not committed to OpenTelemetry - Dash0’s model is optimized for OTel. If you prefer vendor-native agents, curated proprietary schemas, or do not want to invest in OTel semantic conventions, Dash0 may not deliver its intended value. - If you need long default retention for logs/traces - Dash0’s public pricing page lists 30-day retention for spans/log records/web events. If you need 90–365+ days as a default without external archival, evaluate vendors (or tiered storage add-ons) that better match that requirement. - If you need a large set of niche integrations immediately - Newer platforms often lag incumbents in long-tail integrations and out-of-the-box content. Validate Dash0’s integration hub against your exact stack. - If you require independently validated ROI benchmarks - Dash0’s most visible ROI claims are vendor-published case studies; if procurement requires independent analyst validation, you may need to rely more on incumbents with deeper third-party coverage. - Current limitations acknowledged by vendor / visible in public sources - Compliance roadmap uncertainty - Dash0’s security page lists ISO 27001, HIPAA, and PCI DSS as “Coming 2026,” implying not all compliance targets are fully achieved yet. - Roadmap / not yet available - HIPAA / PCI DSS “Coming 2026” suggests future availability, but no specific target dates were provided in the accessed page. - Scale limitations - No explicit scale ceilings were found in the accessed sources. - As with all consumption-based observability, scale is bounded by telemetry volume economics and the buyer’s ability to control noisy data. - API limitations and integration constraints - Dash0 offers multiple developer tools (CLI, Terraform provider, Kubernetes operator). Specific API rate limits and SLAs were not found in the sources accessed.

02Why they buy

- Open standards end-to-end (partially validated by product design) - OTel ingest + PromQL querying + Perses dashboards-as-code is a coherent “portability” posture. - Hacker News discussion highlights Dash0’s claim that many vendors accept OTLP but convert into proprietary formats; Dash0 argues it preserves OTel semantic conventions and resource context. - Transparent unit pricing - Dash0’s pricing page provides simple, explicit unit costs across signals and synthetics, plus a trial without credit card. - AI-assisted workflows (Agent0, Log AI) - Agent0 is described as a sandboxed agent that can investigate issues, generate dashboards/alerts, and even generate code fixes, with integrations to systems like GitHub/Linear/MCP. - Log AI focuses on structuring unstructured logs by extracting attributes and severity. - Critical note: These are vendor-described capabilities; independent user validation of outcomes (e.g., MTTR reduction metrics) was not found in accessible sources. - Areas where competitors clearly have advantages - Datadog/Dynatrace - Likely stronger “zero-to-value” auto-discovery, deeper out-of-box content, and larger ecosystems. - Grafana stack - Strong OSS community, broad plugin ecosystem, and optional self-hosting control. - SigNoz - Open-source + self-hosting option can be a decisive advantage for data sovereignty or cost control (at the expense of operational complexity).

03Field reports

- Important context on review availability - Dash0 is relatively new (publicly launched around November 2024 per press coverage). As a result, major review platforms may have fewer reviews than incumbent observability vendors. - Review platform signals (G2) - G2 lists Dash0 with a high average rating (4.8/5) and shows a review distribution heavily skewed to 5-star reviews, with no 1–2 star reviews visible in the summary panel at time of access. - This distribution may reflect a small sample size and early-adopter bias; it also makes it harder to extract “deal-breaker” negatives from G2 alone. - Community and social signals (Reddit, Hacker News) - Hacker News “Show HN” thread includes skeptical questions about whether Dash0 is meaningfully more “open” than other vendors that accept OTLP, plus operational concerns such as Kubernetes version support for the operator. - In the same thread, Dash0 employees argued that “open” should include avoiding proprietary data formats and ensuring portability of dashboards/alerts via PromQL and Perses. - In Reddit discussions about Dash0 funding, at least one commenter questioned whether Dash0 contributes back to OpenTelemetry; a Dash0-affiliated commenter responded claiming a major code donation to opentelemetry-injector and ongoing maintenance. - Example quotes (positive / supportive) - From Dash0’s customer case study (vendor-published): - “Dash0 has allowed us to cut our observability spend in half compared to New Relic’s trajectory, delivering the same visibility with significantly greater cost-efficiency.” (Bonhams case study) - From G2’s positioning/summary content (platform-provided): - G2 describes Dash0 as “OpenTelemetry Native” with “simple, transparent pricing” and “resource-centric monitoring.” (This is not an end-user quote, but reflects how the profile is presented.) - Example quotes (critical / skeptical) - From Hacker News discussion: - A commenter challenged unclear minimum Kubernetes version support and suggested the operator dependencies looked “bleeding edge,” pushing Dash0 to document support more clearly. - From the same HN thread, a user asked whether Dash0 is essentially “a new UI + storage layer for otel,” highlighting a common buyer concern: differentiation vs other OTLP-ingesting vendors. - Why customers chose Dash0 over alternatives (themes in accessible sources) - Transparent, usage-based pricing with explicit unit costs and no base platform fee (positioned as a response to “bill shock”). - Open standards portability (PromQL + Perses) as a hedge against lock-in. - OTel-native model (resource-centric navigation and semantic conventions) as a product differentiator. - Why some customers left for competitors (churn reasons) - Direct churn narratives are limited in accessible sources. - A common pattern in community conversations about observability tools is that incumbents (Datadog/Grafana/New Relic/Dynatrace) still have broader integration ecosystems and “enterprise completeness,” and that newer entrants can be missing specific features needed by mature orgs. - Deal-breakers and reasons customers didn’t purchase - Limited direct “failed deal” write-ups were found. - Probable deal-breakers inferred from community skepticism: - Teams that don’t want to invest in OpenTelemetry instrumentation/collector management may still prefer proprietary “one agent” experiences. - Organizations requiring long log retention (beyond 30 days) without separate archival may find Dash0’s default retention insufficient unless extended options exist. - Bonhams case study (vendor-published) - Dash0 reports a Bonhams migration evaluation across renewing New Relic vs Grafana Cloud vs Dash0, and claims “50% savings” vs New Relic’s trajectory. - Critical evaluation - The “50% savings” claim is vendor-published and not independently verified in the sources accessed. - The case study does not (in the accessible snippet) fully disclose methodology (data volume assumptions, workload mix, retention periods, included/excluded modules, contract discounts), which are material to validating observability cost comparisons.

04Best fit

- Company sizes - Best fit likely: - 20–500 employees with modern cloud-native workloads - Mid-market to enterprise teams that have an SRE/platform function and are actively managing observability spend - Possible but less proven: - Very large enterprises (2,000+ employees) where incumbent vendor breadth and procurement comfort dominate - Industries and verticals - Software/SaaS, fintech, marketplaces, and any microservices-heavy environment where tracing + logs + metrics correlation is essential. - Roles and personas - Decision makers - VP Engineering, Head of Platform, SRE Manager, DevOps leadership - Security/Compliance stakeholders for SOC 2 / ISO requirements - End users - SREs/on-call engineers - Backend engineers troubleshooting latency/errors - Platform engineers managing instrumentation standards - Pain points addressed - Vendor lock-in concerns (dashboards/alerts tied to proprietary tooling) - “Bill shock” / inability to forecast observability costs - Fragmented tools for logs/metrics/traces - Qualification criteria (great fit) - Strong preference for OpenTelemetry as the standard - Existing PromQL investment and desire to reuse rules/alerts - Willingness to manage telemetry hygiene (sampling, noise filtering) - Deal disqualifiers (poor fit) - Teams wanting a proprietary “install one agent and get everything” approach with minimal OTel expertise - Use cases requiring very long retention for traces/logs as a built-in default - Organizations requiring a long history of third-party audits/reviews beyond what a young vendor can provide publicly

05The pitch

- What the product does (core value proposition in objective terms) - Dash0 is a cloud observability platform built around the OpenTelemetry (OTel) data model, intended to unify logs, metrics, and traces in a single product with alerting, dashboards, service mapping, website monitoring, and synthetic monitoring. It positions itself as “OpenTelemetry-native” and emphasizes portability via open standards (OTel ingest, PromQL querying, Perses dashboards-as-code). - Dash0 also includes AI-assisted features branded as Agent0 (copilot/agent workflows for troubleshooting and asset generation) and Log AI (automatic log pattern extraction and attribute enrichment). - Target market and market positioning - Primary target buyers appear to be cloud-native engineering organizations (SRE, platform, DevOps, backend engineering) already standardizing on OpenTelemetry or planning a migration away from proprietary instrumentation. - Market positioning is “Datadog/Dynatrace-class experience” with a stronger emphasis on open standards and more predictable, usage-based pricing. - Company background (founding year, HQ, key leadership) - Dash0 is described as founded in 2023, led by founder/CEO Mirko Novakovic (previously associated with Instana). Public databases and press coverage consistently list Novakovic as CEO/founder. - HQ is not consistently stated in the sources accessed for this report; Dash0’s public policies include a US mailing address, but this does not necessarily confirm operational headquarters. - Funding and growth: investment rounds, acquisitions, estimated customer count/revenue if public - Seed funding of $9.5M led by Accel (with Dig Ventures participation) was reported at launch coverage. - Multiple outlets and community posts reference a $110M raise at a $1B valuation (often described as 2026 “unicorn” funding news). This appears widely reported, but this report did not verify the press release directly from Dash0’s own newsroom beyond the link shown on the pricing page navigation. - Public customer count / ARR is not provided in the accessible sources; Dash0 does have a “Customers” section on its site, but this report did not extract a full customer list. - Pricing model with specific tiers and costs where available - Dash0 uses consumption-based pricing (single plan rather than feature-gated tiers). - Public list prices (monthly billing) on Dash0’s pricing page: - Metric data points: $0.20 per million; 13 months retention - Spans or span events: $0.60 per million; 30 days retention - Log records: $0.60 per million; 30 days retention - Web events: $0.60 per million; 30 days retention - Synthetic API check runs: $0.20 per thousand; 13 months retention - Agent0 credits: $0.60 per credit - Dash0 offers a 14-day unlimited free trial with no credit card required. - Total cost of ownership considerations (implementation, training, hidden costs) - Implementation costs - Dash0 is designed to ingest OTel data via OTLP directly, via an OpenTelemetry Collector, and via a Kubernetes operator (open-source) for “getting your data in without much effort.” This can reduce vendor-specific agent rollout work, but still requires OTel instrumentation/collector configuration effort (which many teams find non-trivial). - Training costs - Dash0’s “PromQL for everything” and Perses dashboards-as-code may reduce retraining for teams already invested in Prometheus tooling. - Teams not proficient in PromQL or OTel semantic conventions may face a ramp-up period. - Hidden/adjacent costs - Like any SaaS observability platform, exporting telemetry can add cloud egress/network costs and requires governance (data sampling, log filtering, cardinality control). Dash0 claims built-in cost controls (budget limits, spam filters, cost forecasting), but the effectiveness depends on real-world telemetry hygiene. - Key competitors in the space (list 4-6 direct alternatives) - Datadog - Dynatrace - Grafana Cloud (LGTM stack managed) - New Relic - Honeycomb - SigNoz (open-source / self-hosted OTel-centric alternative)

Get a comprehensive analysis of Dash0 including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →