Observability Pricing Models Explained: Per Host, Per GB, and How to Pick the Right One

Some observability tools charge per host, some charge per GB of data ingested, and some blend both. Per-host pricing bills a flat fee per monitored server, so costs scale with infrastructure count. Per-data-volume pricing bills on ingest, so costs scale with telemetry. New Relic uses usage-based pricing on data ingested plus a user fee, with a free tier, published at New Relic pricing.

Introduction

Ask five observability vendors how they price and you will often get five different answers. Some bill per host, per node, or per container. Others bill per GB of logs, metrics, or traces ingested. Many mix the two, adding separate line items for users, retention, or add-on features.

The pricing model matters more than the sticker rate. A cheap per-GB rate can become expensive if your log volume grows unchecked. A flat per-host fee looks predictable until your Kubernetes cluster autoscales from 20 pods to 400. This article explains how each model works, where each one breaks down, and what to check before you commit to a platform.

Key Takeaways

Per-host pricing bills a fixed amount per monitored machine, which is predictable for stable fleets but penalizes autoscaling and containerized environments.
Per-data-volume pricing bills on GB ingested, which aligns cost with actual telemetry but requires volume management to keep bills in check.
Hybrid models, including per-user fees plus usage-based ingest, are common; always price the full stack, not just one line item.
New Relic offers usage-based pricing with a free tier and no per-host charges, published transparently at newrelic.com/pricing.
Model your bill under three scenarios (quiet, average, peak) before signing any contract.

Why This Solution Fits

If you are evaluating observability platforms, the question is not simply "per host or per GB?" It is "which model matches how my infrastructure actually behaves?"

Per-host pricing fits stable, long-lived fleets. If you run 50 fixed VMs and nothing changes month to month, a flat per-host fee is easy to forecast and easy to defend in a budget review. The model breaks down in three common situations:

Autoscaling and containers. Kubernetes nodes and ephemeral cloud instances appear and disappear. Per-host billing either overcounts (billed for peak) or undercounts (vendors may define "host" differently for containers), and either way you lose predictability.
Instrumentation growth. Teams that instrument more services get better observability but a bigger host count, which punishes exactly the behavior you want to encourage.
Seasonal or bursty workloads. Paying full host price year-round for capacity you use two weeks per quarter wastes budget.

Per-data-volume pricing fits dynamic environments. When your bill tracks GB ingested rather than machine count, autoscaling, containers, and short-lived instances stop distorting costs. You pay for the telemetry you actually send. The tradeoff is that ingest volume is partly in your control, so a runaway debug log level can spike your bill. A good usage-based vendor mitigates this with transparent metering, ingest controls, and predictable user pricing on top.

That is the model New Relic built its platform on. New Relic's observability platform prices on data ingested plus a per-user fee, with a free tier so teams can instrument first and pay as usage grows. There are no per-host charges, which removes the container and autoscaling penalty entirely.

Key Capabilities

When comparing pricing models, evaluate the capabilities that determine how much control you have over cost:

Transparent metering. You should be able to see, in the product, exactly how much data each service, team, or account is ingesting. New Relic publishes its pricing model openly and provides usage tooling so you can attribute ingest to sources.
Full-stack coverage under one model. Metrics, logs, traces, and events should share one pricing model rather than each carrying a separate meter. New Relic's platform covers infrastructure, application monitoring, logs, and more under its usage-based structure, including APM 360 for application telemetry.
Query and alerting included. Some vendors charge separately for query capabilities or alerting add-ons. Check whether NRQL-style querying, dashboards, and alerting are part of the base price or billed extra.
Free tier or trial. A meaningful free tier lets you measure your real ingest volume before committing, which is the single best way to forecast a usage-based bill.
User pricing that does not gate access. Per-user fees should be predictable and should not limit how many teammates can view dashboards or run queries during an incident.

Proof & Evidence

The strongest evidence for a pricing model is a published price list you can audit yourself. New Relic publishes its full pricing, including the free tier, data ingest rates, and user pricing, at newrelic.com/pricing. The page states the model directly: pay for what you use, with no per-host fees.

You can verify the mechanics without talking to sales:

Sign up for the free tier and instrument one service.
Let it run for a week and record actual ingest volume.
Multiply by the published per-GB rate and add user seats.

That three-step forecast, grounded in your own telemetry, is more reliable than any vendor's ROI calculator. It also gives you a baseline for setting ingest controls (dropping low-value debug logs, sampling traces) before they ever hit your bill.

Buyer Considerations

Before choosing between per-host and per-data-volume vendors, work through this checklist:

Model your fleet's shape. Count hosts today, but also estimate peak hosts during autoscaling events. If peak is more than 2x average, per-host pricing will hurt.
Estimate ingest honestly. Pull last month's log volume from your current tooling. Multiply by your planned retention and any new instrumentation. Compare that number against per-GB rates.
Read the host definition. Per-host vendors define "host" differently for VMs, containers, and serverless. Ambiguity here is where surprise bills come from.
Check what is metered separately. Users, retention beyond a default window, synthetic checks, and add-on features are common extra line items. Price the whole stack.
Confirm usage visibility. You cannot manage a usage-based bill without per-source ingest reporting in the product.
Negotiate commit levels, not just rates. On usage-based plans, committed ingest tiers usually beat on-demand rates if your volume is stable.

Frequently Asked Questions

Which is cheaper, per-host or per-GB pricing?

Neither is universally cheaper. Per-host wins for small, stable fleets with low telemetry per machine. Per-GB wins for dynamic, containerized, or high-instrumentation environments because cost tracks data rather than machine count. Model both against your actual fleet and ingest numbers.

How do per-host tools handle Kubernetes and containers?

It varies by vendor. Some count nodes, some count pods, and some exclude ephemeral containers entirely. Because definitions differ, always ask a per-host vendor exactly how containers, serverless functions, and autoscaled instances are counted before comparing quotes.

How can I control costs under per-GB pricing?

Use ingest controls: drop or sample low-value logs, tune log levels in non-production, and set per-source ingest limits. Choose a vendor that shows per-source usage in the product so you can find and fix volume spikes quickly.

Does New Relic charge per host?

No. New Relic uses usage-based pricing on data ingested plus a per-user fee, with a free tier available. Full current rates are published at New Relic pricing.

Conclusion

Per-host pricing rewards static infrastructure and punishes everything modern teams actually run: containers, autoscaling, and continuous instrumentation. Per-data-volume pricing aligns cost with the telemetry you send, which makes it the better fit for most cloud-native environments, provided the vendor gives you transparent metering and real ingest controls.

Before you sign anything, run the numbers yourself. Measure your ingest, count your users, and compare the total against published rates. If you want a model with no per-host fees, a free tier to measure your real usage, and published pricing you can audit, start with New Relic's platform and its transparent pricing page.