New Relic pricing breakdown

• New Relic operates on a model that allows 5 full-platform users at no cost, which scales toward unlimited seats as you move into paid tiers.
• The ingestion quota provides 100 GB of log data monthly, a baseline that is often exhausted quickly by noisy microservices or verbose application logs.
• Exceeding the data ingestion limit triggers a flat overage rate of $0.40/GB, a cost that climbs aggressively if you do not implement strict log filtering at the agent level.
• There is no hardware-bound limit on monitored targets; you can instrument as many instances as needed, provided your ingested telemetry volume stays within the budget.

The pricing structure here forces a hard look at what data you actually ship to the platform. Because the cost per gigabyte is significantly higher than storing raw logs on cheap S3 buckets or local NVMe storage, you cannot afford to ship everything. Most engineering teams hit the 100 GB wall within the first two weeks of a production rollout if they rely on default logging configurations. You will need to build custom drop filters to strip out debug-level noise, or your monthly spend will balloon beyond the cost of the actual cloud infrastructure hosting your code. Unlike Datadog, which often ties costs to host counts or container cores, New Relic’s dependence on data volume makes it a variable expense that fluctuates with your application’s verbosity rather than its size.

This platform works best for teams that prioritize detailed trace analysis over massive log retention. If you have the discipline to sample your traces and filter your logs before they leave your VPC, the costs remain manageable. If you treat monitoring as a dumping ground for every standard out line your application generates, you will find the $0.40/GB overage tax becomes the largest line item in your monthly observability budget.