New Relic Free pricing & rate limits

• New Relic operates on a consumption-based model where the base cost is not public, pushing teams to negotiate custom contracts once they exceed the $0.00/mo baseline for the free tier.
• The entry-level package includes a fixed 100 GB of monthly log ingestion, which is sufficient for small microservices but creates a hard ceiling for high-verbosity applications.
• Monitoring is decoupled from host counts, allowing for Unlimited monitored targets, which is a departure from the per-node licensing seen with older tools like AppDynamics.
• The platform provides 1 full-access user seat in the base configuration, requiring additional spend as your engineering headcount grows.

The pricing structure shifts the focus from hardware footprint to data volume. Because you are not paying per CPU core or per container, the cost becomes a direct function of your logging intensity. In environments running on AMD EPYC or ARM instances, where compute is cheap, it is easy to accidentally inflate your bill by shipping verbose debug logs to the New Relic backend. Once you exhaust the 100 GB limit, the overage costs are significant enough to warrant aggressive log filtering at the agent level. Many teams find that the lack of per-host limits is beneficial when autoscaling groups, but the lack of transparent pricing makes it difficult to forecast costs before an unexpected spike in throughput occurs.

This platform serves engineering teams that need deep visibility into distributed traces and complex application dependencies without worrying about the number of nodes in their cluster. It is most effective for organizations that have the engineering discipline to manage log retention policies and filter out noise before data reaches the ingestion pipeline. If your infrastructure generates massive amounts of telemetry, you will spend more time managing your data volume than you would with a fixed-price provider.