SigNoz Cloud
Estimate- $49 minimum includes usage credit
- Metrics: $0.10/M samples
- Logs and traces: $0.30/GB ingested
Observability cost model
Enter known usage or estimate from infrastructure. The sliders use real-world gaps, so a team with ten hosts and an enterprise platform with thousands can use the same form without losing precision.
Current lowest SaaS estimate
Drag the range or type exact values. Slider spacing is logarithmic where observability usage naturally jumps across orders of magnitude.
33M samples/day. Count billable metric samples, not active series.
750 GB stored for the selected retention period.
60 GB stored for the selected retention period.
Hosts affect Datadog infrastructure and APM style pricing.
Full-access users affect New Relic and Grafana Cloud pricing. Basic dashboard viewers are often free or cheaper.
Use this when finance has infrastructure counts, but not telemetry volumes. The estimator keeps the assumptions visible before applying them.
Bare metal nodes, cloud instances, and Kubernetes worker nodes.
From one startup cluster to fleet-wide regional platform clusters.
Primary databases, replicas, queues, and managed data services.
Instrumented services, workers, jobs, and public APIs.
Average production traffic. Spikes should be modeled by raising this toward peak load.
Retention makes the storage curve visible. This table holds volume constant and changes only days kept.
| Retention | SigNoz | Grafana | New Relic | Datadog | LGTM baseline |
|---|---|---|---|---|---|
| 30 days | $424 | $400 | $690 | $1,262 | $868 |
| 60 days | $505 | $471 | $690 | $1,262 | $875 |
| 90 days | $586 | $542 | $690 | $1,262 | $883 |
| 180 days | $748 | $755 | $690 | $1,262 | $911 |
CloudRaft designs and operates open-source observability platforms for teams that need cost control, retention policy, and production support without giving up Grafana, Prometheus, Loki, Tempo, Mimir, Thanos, or VictoriaMetrics.
Plan infrastructure and storage before usage scales.
Keep high-value signals longer without charging every team separately.
Run telemetry inside your cloud account and security boundary.
Operate the stack with dashboards, alerts, upgrades, and SLOs.