
Application Performance Monitoring
Fast & Cost-Effective APM with AI-based sampling. Runs On-Prem with no traces data sent out of your cloud.

Application Performance Monitoring
Fast & Cost-Effective APM with AI-based sampling. Runs On-Prem with no traces data sent out of your cloud.
Enter your usage to get an instant monthly estimate - and see how CubeAPM's on-prem pricing compares.
scrape_interval config.
| Component | Grafana Cloud | CubeAPM |
|---|
| Grafana Cloud | CubeAPM | |
|---|---|---|
| Billing dimensions | 8+ independent meters | $0.15/GB |
| Metrics pricing | Per series (cardinality risk) | Included in $0.15/GB rate |
| Data retention | 14 days free, metered paid | Unlimited included |
| Users | Per-seat above 3 | Unlimited |
| Cardinality risk | Yes - label explosion = bill explosion | No |
| Infrastructure | Grafana-managed SaaS | Runs in your own cloud |
Grafana Cloud pricing is usage-based and spans multiple independent dimensions: metrics series, log and trace ingestion volume, host hours for Kubernetes and Application Observability, database host hours, per-user charges for dashboards and incident management, and test executions for synthetics. Each dimension is billed separately, and changes in any one of them can materially shift your monthly bill without being obvious upfront.
This calculator helps you:
The goal is not to predict an exact bill. Actual charges depend on usage patterns, retention choices, and any volume discounts. But it gives you a realistic cost range based on how Grafana Cloud pricing works in practice.
Grafana Cloud is composable by design: you enable only the products you need and pay for what you use. In practice, as environments grow, costs accumulate across a large number of independent billing units, and the interactions between them are not always intuitive.
Grafana Cloud has three plan tiers:
The $19/month Pro fee is a platform fee. The actual bill grows on top of it as usage scales across each product.
Grafana Cloud charges for metrics based on billable series, not the count of metric names. A single metric with high-cardinality labels generates one series per unique label combination. For example, a metric labelled by Kubernetes pod name across 500 pods creates 500 billable series from a single metric name.
Pricing:
This catches teams off guard because Prometheus scrapers with many targets, Kubernetes environments with per-pod labels, and new exporters can silently add thousands of series as workloads scale.
Grafana Cloud logs are powered by Grafana Loki. Billing is split across three operations per GB ingested:
Free tier includes 50 GB ingested/month with 14-day retention. Pro includes 50 GB/month with 30-day retention, then pay as you go. Extending retention beyond 30 days requires contacting Grafana for custom pricing.
The three-part billing structure means even a simple decision like increasing log verbosity shows up as three separate line items on your invoice.
Grafana Cloud traces (powered by Grafana Tempo) use the same three-part billing structure as logs:
Free tier: 50 GB/month, 14-day retention. Pro: 50 GB/month included, 30-day retention, then pay as you go. Enterprise: custom pricing on annual commit.
Without sampling configured, a service handling high request volume can exceed the 50 GB free tier quickly. Tail-based sampling (keeping traces for errors and high-latency requests only) is the primary lever for controlling trace costs.
Continuous profiling data (powered by Grafana Pyroscope) follows the same pricing as logs and traces:
Free tier: 50 GB/month, 14-day retention. Pro: 50 GB/month included, 30-day retention, then pay as you go. Enterprise: custom pricing on annual commit.
Kubernetes Monitoring is billed by host hours and container hours, not by telemetry volume alone. A host is any physical or virtual OS instance sending observability signals; it is considered active if it has sent a signal in the last 15 minutes.
Pricing:
The $19/month platform fee includes the free tier allotments, then charges apply on top. Telemetry generated by monitored hosts (metrics, logs, traces) is billed separately at standard telemetry rates.
This creates a compound cost structure: each Kubernetes node contributes to host-hour charges AND to telemetry volume charges simultaneously.
Application Observability (APM) is billed per host hour. A host is active if it has sent a signal in the last 15 minutes.
Pricing:
As with Kubernetes Monitoring, host-hour charges for Application Observability stack on top of standard telemetry charges (metrics, logs, traces) generated by those same hosts.
Frontend Observability provides real user monitoring (RUM) and is billed per session. A session is the time a user spends in the application; it ends after 4 hours maximum or 15 minutes of inactivity.
Pricing:
Session counts scale directly with user traffic, so high-traffic web applications can see Frontend Observability costs grow quickly during peak periods.
Database Observability is billed per database host hour. Each database server instance counts as one database host, including individual nodes in a cluster.
Pricing:
Database Observability charges are additive to the telemetry (metrics and logs) those database hosts generate. Running monitoring on 5 database hosts costs roughly $255/month in host-hour charges alone, before accounting for the metrics and logs they produce.
Synthetic monitoring is billed per test execution. One test execution equals a synthetic test running in one probe location for one minute of run time.
Pricing:
To estimate executions: multiply number of probe locations x number of tests x test duration (minutes) x (43,200 / test frequency in minutes). A single test running every minute from 5 locations generates approximately 216,000 executions/month, well above the free tier limit.
Load and performance testing is billed in virtual user hours (VUh). VUh is calculated as: (maximum VUs x test duration in minutes) / 60.
Pricing:
Grafana dashboards are billed per active user. Any user who logs in during the billing month counts as active.
Pricing:
IRM (on-call scheduling, alerting, and incident management) is billed per active IRM user. A user is active if they are included in on-call schedules, receive a page, or create/update an incident during the billing month.
Pricing:
The AI copilot is billed per active AI user. A user is active if they send a message or use an Assistant feature during the billing month.
Pricing:
Most unexpected cost increases come from a recognizable set of patterns:
Grafana Cloud’s Adaptive Metrics feature identifies unused or over-specified time series and recommends aggregating or dropping them. For teams with large Prometheus deployments, this is typically the highest-leverage cost control available. Grafana Labs publishes case studies showing up to 80% reduction in billable series through this feature.
Adaptive Logs identifies frequently ingested log patterns that are rarely queried and recommends filters to drop them before ingestion. Reducing log volume by 30-50% has a direct, proportional impact on the Process, Write, and Retain charges.
Trace volume is directly controlled by sampling at the SDK or collector level. Tail-based sampling (keeping traces for errors and high-latency requests only, rather than randomly) preserves signal while reducing ingested volume more efficiently than head-based sampling.
Kubernetes Monitoring, Application Observability, and Database Observability all bill by active host hours. Limiting monitoring to production namespaces rather than all environments reduces host-hour charges without reducing coverage where it matters most.
Per-user charges for Visualization, IRM, and the AI Assistant grow quietly as more team members are granted access. Periodic audits to deactivate users who no longer need access can reduce user-based costs meaningfully in larger organizations.
The free tier is functional: 10,000 active series, 50 GB each of logs, traces, and profiles, 3 active users, 14-day retention. Routing dev and staging traffic to a separate free-tier workspace keeps those costs entirely out of your primary bill.
The measures above are effective but require continuous attention as systems evolve. High-cardinality labels reappear when new engineers instrument services without billing awareness. Log verbosity creeps back up after debugging sessions. New Grafana Cloud products get enabled by individual teams without FinOps coordination.
At a larger scale, managing observability spend inside a multi-dimensional usage-based model becomes a recurring operational task. This is often when teams begin evaluating whether structural cost controls enforced by architecture better fit their needs than process-based optimization.
The fundamental difference between Grafana Cloud and CubeAPM is not features. It is where the platform runs and how costs are bounded.
Grafana Cloud is a fully managed SaaS platform. All telemetry (metrics, logs, traces, profiles) is shipped to Grafana Labs’ infrastructure and billed based on volume sent, hosts monitored, and users active. Costs grow with telemetry, and telemetry grows with systems.
CubeAPM runs inside your own cloud account (AWS, GCP, Azure) or on-premises infrastructure. Telemetry data never leaves your environment. You pay for the compute and storage you provision in your own cloud, not for usage metered by a SaaS vendor. Cost growth is tied to infrastructure planning, not instrumentation depth.
| Area | Grafana Cloud | CubeAPM |
|---|---|---|
| Deployment | Fully managed SaaS | Self-hosted in your own cloud |
| Pricing model | Per series + per GB (Process/Write/Retain) + per host hour + per user | Per GB ingested (logs, traces, metrics) |
| Cost predictability | Varies across multiple independent dimensions | Stable; tied to infrastructure provisioning |
| Data residency | Grafana Labs infrastructure | Your cloud account; data never leaves |
| Metrics billing | Billable series (cardinality-sensitive) | GB ingested |
| Log and trace retention | 30 days default; custom via Enterprise contract | No retention fees; storage is your own infrastructure cost |
| Per-user charges | $8/user (Visualization), $20/user (IRM), $20/user (AI Assistant) | Unlimited users included |
| Data egress | Telemetry exits your VPC to Grafana; cloud egress applies | Zero egress; CubeAPM runs in-VPC |
| Support | Community (Free), 8x5 email (Pro), custom (Enterprise) | Included with plan |
With CubeAPM, the cost drivers are the infrastructure you provision, your retention choices, and your sampling strategy. There are no per-series charges, no per-user fees, no separate APM licensing, and no data egress costs. Instrumentation decisions are engineering decisions, not billing events.
Grafana Cloud remains a strong choice for teams that want a fully managed experience with no operational overhead, and that are comfortable with usage-based pricing in exchange for not managing infrastructure. The tradeoff is real: CubeAPM requires provisioning and operating infrastructure inside your own account, which has its own cost in engineering time.
The calculator above is designed to help you see both sides of that tradeoff clearly, using your own usage estimates.
Disclaimer: Pricing based on Grafana Cloud public pricing at grafana.com/pricing, verified May 2026. Actual costs vary based on usage patterns, volume discounts, and enterprise contract terms. This calculator is not affiliated with or endorsed by Grafana Labs.
