Same signals. Without the unit math.
Dynatrace's DPS model spans host units, log ingest units, and DEM units that each accrue separately and compound as you add capabilities. Randoli's rate is one number per host, per hour. Adding logs, traces, or AI incident response doesn't change the unit type or add a new meter.
Where it actually differs
Pricing model
Flat per-host rate. One number per host, per hour, not a basket of unit types that each accrue separately. Logs, traces, metrics, and AI all included.
Davis Platform Services (DPS) spans host units, log ingest units, DEM units, and more. Each feature consumes from the same pool at different rates. Predicting consumption requires understanding how each unit type burns.
Agent & instrumentation
OTel-native. No proprietary agent. Your instrumentation uses standard OpenTelemetry and works with any OTel-compatible backend, not just Randoli.
OneAgent is a proprietary instrumentation layer. Deep auto-instrumentation is a genuine strength, but migrating to a different backend means re-instrumenting your applications.
Data ownership
Raw telemetry stays in your cluster. No egress required. Local processing keeps sensitive data in your environment under your control.
Telemetry sent to Dynatrace's cloud (or Dynatrace Managed, which adds your own operational overhead). Raw data lives in their environment.
Pricing predictability
Host count determines your bill. Easy to model ahead of a deployment. No surprises from feature adoption.
DPS units make it harder to predict the cost impact of new features. Enabling session replay, synthetics, or log monitoring each changes the consumption rate differently.
Log monitoring
Logs stream through the same real-time pipeline as everything else. No separate unit type to track for log volume.
Logs consume their own priced DPS unit, on top of host and other unit types already accruing independently.
The numbers
Volume assumption: ~300 GB logs/day and ~50 M trace spans/day per 100 hosts. Dynatrace estimates based on published DPS rates for Full-Stack Monitoring with log ingest. Randoli at $0.04/host/hour.
| Scenario | Dynatrace (est.) | Randoli |
|---|---|---|
| ~$3,000/mo | ~$1,440/mo | |
Randoli: $0.04/host/hr × 50 hosts × ~730 hrs/mo ≈ ~$1,440/mo Dynatrace (est.): illustrative, based on that vendor's published rate card at the volume in this scenario — see the assumption note above. | ||
| ~$11,500/mo | ~$5,760/mo | |
Randoli: $0.04/host/hr × 200 hosts × ~730 hrs/mo ≈ ~$5,760/mo Dynatrace (est.): illustrative, based on that vendor's published rate card at the volume in this scenario — see the assumption note above. | ||
| ~$16,000+/mo | ~$5,760/mo | |
Randoli: $0.04/host/hr × 200 hosts × ~730 hrs/mo ≈ ~$5,760/mo Dynatrace (est.): illustrative, based on that vendor's published rate card at the volume in this scenario — see the assumption note above. | ||
| Quote-based | ~$14,400/mo (volume discounts available) | |
Randoli: $0.04/host/hr × 500 hosts × ~730 hrs/mo ≈ ~$14,400/mo Dynatrace (est.): illustrative, based on that vendor's published rate card at the volume in this scenario — see the assumption note above. | ||
Illustrative estimates based on published rate cards and typical usage patterns, not a quote. Confirm current numbers before publishing.
Why teams switch
Dynatrace's Davis AI is a genuinely powerful causal analysis engine. Auto-instrumentation through OneAgent covers applications with minimal manual effort, and the topology-aware root-cause analysis is one of the strongest in the market. The friction appears at procurement: DPS pricing is difficult to forecast, contracts are negotiated, and teams that want to expand coverage (adding logs, enabling session replay, running synthetic monitors) often discover the consumption impact only after the fact.
Teams that switch most commonly cite two things: the desire for OTel-native instrumentation without proprietary agent lock-in, and the need for a pricing model they can model independently without a sales conversation. Randoli's flat per-host rate makes both possible.