New Relic prices on data ingest and user access, with cardinality limits that can affect aggregated metrics at higher scale. Kloudfuse runs inside your cloud and prices on one axis: telemetry ingested.
The biggest differences come down to how the platform is deployed, how usage is priced, and what happens as data volume and complexity grow.
Basic users are free and unlimited. Full platform users — the ones who get APM, infrastructure, browser and synthetics — are $349 each per month on Pro and $549 on Enterprise, billed at the highest type held in that calendar month.
New Relic bills on ingested gigabytes, so a label explosion does not produce a surprise invoice. It produces a limit: 100,000 unique time series per metric by default, and 15 million total cardinality per account per day.
There is no self-hosted, on-premises, in-VPC or BYOC option. Three regions are available — US, EU and Japan — and data cannot be moved between them after the account is created.
| Data ingest | $0.40 per GB | $0.60 on Data Plus; first 100 GB a month included |
|---|---|---|
| Core user | $49 per user / month | Limited platform access |
| Full platform user | $349–$549 per user / month | Pro to Enterprise, billed at the highest type held that calendar month |
| Hosts | Included | Unlimited hosts on all tiers |
| Extended retention | $0.05 per GB ingested | Per additional 30 days, charged on ingest volume rather than stored volume |
New Relic list pricing, August 2026. View current pricing →
Where the data plane runs, what each meter charges for, and what each platform will and will not do. Where a vendor does not publish something, the table says so.
| New Relic | Kloudfuse | |
|---|---|---|
| Where it runs | ||
| Data plane location | SaaS only. US, EU and Japan regions; region is fixed at account creation and data cannot be transferred between them. No self-hosted, on-prem or BYOC option. | Inside your VPC. Ingest, storage, query engine and the AI runtime all deploy into your own cloud account, writing to your object storage under your keys. Only metadata reaches Kloudfuse. |
| AWS, GCP and Azure | Yes. AWS · GCP · Azure | Yes. AWS · GCP · Azure |
| Drop-in migration from their agent | Not published. Their own agent | Yes. Datadog and OpenTelemetry agents accepted |
| What it costs | ||
| What you are billed on | Two axes: ingested gigabytes, and seats. Hosts are unlimited, which removes the per-host problem — but the seat charge scales with how many engineers you want looking at production. | One axis: terabytes ingested, across every signal. Storage and compute land on your own cloud bill because the platform runs in your account. |
| High cardinality | Not priced on cardinality — capped by it. 100,000 unique time series per metric (raisable to 1M); 15M total account cardinality per day (raisable to 200M via the Advanced Compute add-on). At the limit, aggregated data is turned off for the rest of the UTC day. | No cardinality premium, no active-series cap, no per-custom-metric charge. Adding a label does not change the bill. |
| Retention | Short by default: APM, browser, infrastructure processes and distributed traces all 8 days on Original, 98 on Data Plus. Extending costs $0.05 per GB ingested per 30 additional days. | Your bucket, your lifecycle policy. Long retention is a storage decision rather than a pricing tier. |
| Your data | ||
| Sampling | No documented default forced-sampling target. Distributed tracing sampling behaviour is not published in detail. | No forced sampling. Full fidelity across metrics, logs, traces, events, RUM and profiles. |
| Every signal in one store | Yes. One telemetry database | Yes. One data lake |
| Log pattern reduction at ingest | Not published. Not published as an ingest control | Yes. Fingerprinting at ingest |
| Works with existing Grafana dashboards | Partly. Via Prometheus and PromQL | Yes. Kfuse datasource |
| Portability | NRQL and the New Relic agents. OpenTelemetry is accepted and APM Hybrid Agents add OTel API compatibility, but dashboards and alerts are New Relic-shaped. | Built on OpenTelemetry, with Grafana-compatible dashboards through the Kfuse datasource and support for TraceQL and PromQL. Your data stays in your object storage. Your instrumentation and dashboards remain portable and independent of Kloudfuse. |
| AI | ||
| Agents and assistants | New Relic Autopilot (renamed from SRE Agent), plus intelligent root cause analysis and an agent builder. Runs in New Relic’s environment; New Relic AI is explicitly outside the FedRAMP boundary. | Dexter runs inside your boundary, on the model you choose, including a local one. Prompts and completions stay inside the boundary. A human stays in control. |
| Inference inside your own boundary | No. New Relic AI is SaaS-hosted | Yes. Dexter runs in your VPC |
| Security and compliance | ||
| Government and regulated | FedRAMP Moderate, authorised 2 March 2020. Several services are excluded from the boundary, including New Relic AI, Pixie and CodeStream. FedRAMP High and DoD IL4 were announced as a commitment on 23 June 2026, with no published target date. | The data plane runs inside whatever boundary you have already had authorised. FIPS 140-3 validated cryptography (CMVP #5186, #5209); FedRAMP-targeted installations run with EBS encryption. |
| SOC 2 Type II | Yes. Type II | Yes. Type II |
| HIPAA | Yes. Enterprise + Data Plus + BAA | Partly. In progress |
| FIPS-validated cryptography | Partly. 140-2, US and EU regions | Yes. 140-3 · CMVP #5186, #5209 |
| Data residency | Partly. US, EU or Japan, fixed at signup | Yes. Structural — your own VPC |
YesPartlyNoNot published
Per-GB is the better of the two axes, and unlimited hosts is a real advantage over a host count. The complication is the second axis: ingest is predictable, while the seat bill scales with how many engineers you want looking at production — the opposite of what you want as an on-call rota grows.
Aggregated data is switched off for the remainder of the UTC day. Raw data continues to be ingested, so nothing is lost permanently, but pre-computed aggregates stop — which means the dashboards and alerts built on them go quiet at exactly the moment a cardinality spike suggests something is wrong. Pruning rules take effect immediately and are the documented mitigation.
Yes, on both sides. New Relic accepts OTel, and so does Kloudfuse — which is the point: if your instrumentation is OTel, the platform underneath it becomes a choice you can revisit rather than a decision you are stuck with.
That is the intent, and Core Compute is marketed as unlimited full-platform access without user licence fees. It is documented as Preview, and the per-CCU rate for Core Compute is not published — only Advanced Compute has a public price, at $0.606 per CCU. Until that rate is published, the model cannot be costed in advance.
New Relic, New Relic Autopilot and NRQL are trademarks of New Relic, Inc. Kloudfuse is not affiliated with, endorsed by or sponsored by New Relic.
Run Kloudfuse against your own telemetry, in your own cloud, and see what a single correlated view does to your mean time to resolution.