Randoli vs New Relic: a New Relic alternative with unlimited users
Same signals. Without the per-seat tax.
Pricing at a glance, typical telemetry volume
| Cluster | New Relic (est.) | Randoli |
|---|---|---|
| 25 nodes (200 vCPU) | ~$5,700/mo | $1,799/mo (Grow) |
| 50 nodes (400 vCPU) | ~$11,000/mo | $3,999/mo (Scale) |
Randoli's price stays the same as telemetry volume grows.
See the full pricing comparison ↓Where it actually differs
Per-seat pricing
No seats. Every engineer on the team has full access. Headcount growth doesn't add a line to the bill. Only the infrastructure you monitor does.
Full Platform users priced substantially higher than Basic users. As engineering teams grow, the seat cost compounds on top of data ingestion. Two billing axes instead of one.
Data ingestion model
$0 ingestion. Telemetry is processed locally in your cluster. No GB meter. Add verbosity during an incident without budget approval or bill anxiety.
Data priced per GB ingested beyond the free tier. Data Plus adds 90-day retention but increases the per-GB rate. More instrumentation coverage means a higher baseline cost.
Data ownership
Raw logs and traces never leave your cluster. Sensitive telemetry stays in your environment under your access controls and retention policies.
All telemetry sent to New Relic's cloud (NRDB). Powerful query capabilities, but raw data lives in their infrastructure under their retention defaults.
Pricing predictability
One flat monthly price and unlimited users. Know your bill from your typical vCPU alone. No surprises from data spikes or team growth.
Total cost depends on GB ingested × user tier × user count. Any axis growing independently changes the bill. Forecasting requires modeling all three dimensions.
The numbers
Volume assumption: Nodes are assumed to be 8 vCPU / 32 GiB, a common general-purpose production size, with about 0.75 GB of logs and 125,000 trace spans per vCPU per day (600 GB and 100 M spans a day per 100 nodes). New Relic estimates use $0.40 per GB ingested beyond 100 GB (logs, traces and metrics) and Pro Full Platform users at $349, about one per 22 vCPU, the same model as the pricing calculator. Rates checked November 16, 2026. Randoli figures are the flat monthly price of the plan that covers the nodes' typical vCPU, with the whole platform included.
By telemetry volume
Randoli's price is set by cluster size, not by how much telemetry you send. These tables hold the cluster fixed and vary the telemetry, so the Randoli column does not change.
Grow plan, 25 nodes (200 vCPU)
| Telemetry volume | New Relic (est.) | Randoli |
|---|---|---|
| 0.5× typical volume75 GB of logs and 12.5M spans a day | ~$4,600/mo | $1,799/mo (Grow plan) |
| Typical volume150 GB of logs and 25M spans a day | ~$5,700/mo | $1,799/mo (Grow plan) |
| 2× typical volume300 GB of logs and 50M spans a day | ~$7,800/mo | $1,799/mo (Grow plan) |
| 4× typical volume600 GB of logs and 100M spans a day | ~$12,000/mo | $1,799/mo (Grow plan) |
Scale plan, 50 nodes (400 vCPU)
| Telemetry volume | New Relic (est.) | Randoli |
|---|---|---|
| 0.5× typical volume150 GB of logs and 25M spans a day | ~$8,900/mo | $3,999/mo (Scale plan) |
| Typical volume300 GB of logs and 50M spans a day | ~$11,000/mo | $3,999/mo (Scale plan) |
| 2× typical volume600 GB of logs and 100M spans a day | ~$15,200/mo | $3,999/mo (Scale plan) |
| 4× typical volume1.2 TB of logs and 200M spans a day | ~$23,600/mo | $3,999/mo (Scale plan) |
Also included in the Randoli price: Kubernetes cost management, security posture and the Raiya SRE agent, with unlimited users. The New Relic estimates cover telemetry only.
By cluster size
The same typical volume at different cluster sizes.
| Scenario | New Relic (est.) | Randoli |
|---|---|---|
| ~$5,700/mo | $1,799/mo (Grow plan) | |
Randoli: 25 nodes × 8 vCPU = 200 vCPU typical usage → Grow plan (up to 300 vCPU), a flat $1,799/mo with the whole platform included and no overages. New Relic (est.): illustrative, based on that vendor's published rate card at the volume in this scenario. See the assumption note above. | ||
| ~$11,000/mo | $3,999/mo (Scale plan) | |
Randoli: 50 nodes × 8 vCPU = 400 vCPU typical usage → Scale plan (up to 800 vCPU), a flat $3,999/mo with the whole platform included and no overages. New Relic (est.): illustrative, based on that vendor's published rate card at the volume in this scenario. See the assumption note above. | ||
| ~$21,700/mo | $3,999/mo (Scale plan) | |
Randoli: 100 nodes × 8 vCPU = 800 vCPU typical usage → Scale plan (up to 800 vCPU), a flat $3,999/mo with the whole platform included and no overages. New Relic (est.): illustrative, based on that vendor's published rate card at the volume in this scenario. See the assumption note above. | ||
| ~$30,100/mo | $3,999/mo (Scale plan) | |
Randoli: 100 nodes × 8 vCPU = 800 vCPU typical usage → Scale plan (up to 800 vCPU), a flat $3,999/mo with the whole platform included and no overages. New Relic (est.): illustrative, based on that vendor's published rate card at the volume in this scenario. See the assumption note above. | ||
| Quote-based | Enterprise (custom pricing) | |
Randoli: 200 nodes × 8 vCPU = 1,600 vCPU typical usage → above 800 vCPU, Enterprise: custom capacity, multi-year terms and private offers. New Relic (est.): pricing is quote-based, so no figure is shown. See the assumption note above. | ||
Illustrative estimates based on published rate cards and typical usage patterns, not a quote.
In short
Randoli charges one flat monthly price sized by typical vCPU, with unlimited users and no ingestion charge, and processes telemetry in your cluster.
New Relic bills per GB ingested plus per-user seats, so cost grows with both data and headcount.
New Relic's unified platform and NRDB query engine are strong; Randoli suits teams that don't want adding engineers or log verbosity to be a cost decision.
Why teams switch
New Relic's unified telemetry platform is genuinely well-designed. The shift to consumption-based pricing made it more accessible for smaller teams, and NRDB is a powerful query engine. The friction emerges when you model growth: every new engineer who needs full access adds to the seat cost, and every new data source or higher retention period adds to the ingestion cost. The two meters compound independently.
Teams that consolidate onto Randoli most often cite the same thing: a pricing model where growing the engineering team or adding log verbosity during a critical incident isn't a cost decision. When observability tooling requires budget negotiation to use fully, it gets used partially.
