This doc explains our original product-based pricing model. For more on pricing and user-related changes, see Overview of changes.
Overview of original pricing
New Relic has two pricing models: a newer usage-based pricing model (sometimes referred to as New Relic One pricing), and our original pricing model. Our original pricing model is based on subscriptions to specific products, like APM, Mobile, and Infrastructure. Over time, all our customers will be converted to the newer pricing model. To understand more about pricing model changes, see Overview of pricing changes.
For accounts on original pricing, this doc includes:
Explanation of how our original pricing model works
How to manage subscription and billing settings
Annual vs monthly pricing models
Here are the differences between billed-annually and billed-monthly plans:
Pricing plans
Details
Annual (best price)
New Relic charges your credit card each month for a year for a committed number of hosts or compute units. You can increase this amount at any time, and charges will adjust with the next monthly bill. Your account will automatically renew at the end of the year unless you change your subscription.
Early termination, downgrade, or decrease in service: Unless your order form states otherwise, you will be charged at the level and quantity of service ordered until the end of the then-current term if you cancel or downgrade to a lower level of service or fewer hosts during your commitment year.
Monthly (no commitment)
New Relic charges your credit card each month for a specified number of hosts or compute units. The account Owner can change the credit card number. To edit billing settings, use the Billing UI. Adjustments to billing settings will take effect for the next billing period.
Your account automatically renews each month unless you change your subscription. You can cancel service or downgrade to a lower level of service without penalty.
APM and infrastructure: Compute-unit vs host-based pricing
APM offers a choice between two pricing models: compute unit (CU) based pricing and host-based pricing. New Relic Infrastructure offers only CU-based pricing. This section shows how both options are calculated, and explains what "host" means in these pricing contexts:
CU-based pricing is available for these New Relic products:
With CU-based pricing, your monthly price is determined by the size of the host (computing power and memory) running New Relic and the number of hours it connects to New Relic during the month. If a host is connected to New Relic at any time during an hour, that hour counts towards the CU calculation.
Each host is counted separately for each New Relic account the host reports data to. For example, if you have a parent account with two children accounts, each running applications on the same host for 3,000 CUs in a given month, the usage for the parent account will be 6,000 CUs.
For APM, CU-based pricing is the best choice if you have many cloud-based dynamic computing resources. For this reason, CU-based pricing is sometimes referred to as cloud pricing.
CUs are calculated as follows:
The maximum size of a given host (CPUs + GB RAM) is capped at 16.
Examples:
If a host has 2 CPU cores, 2GB RAM, and connects to New Relic for one hour (or less than one hour), it consumes 4 CUs.
If a host has 2 CPU cores, 2GB RAM, and connects to New Relic for an entire month (750 hours used as standard month size), it consumes 3,000 CUs.
You can purchase blocks of CUs to be consumed on a monthly basis. The total number of CUs purchased monthly is calculated by adding up the estimated CU consumption for all hosts for the month. There is no month-to-month rollover of unused CUs. Also, New Relic does not charge by JVMs, containers (such as Docker or Cloud Foundry), or application instances--it charges by the hosts running those containers or application instances.
Price points vary, depending on the New Relic product and subscription level. You can view CU-based account usage from the New Relic UI.
Tip
Pricing for your APM account can be either CU-based or host-based. New Relic Infrastructure uses only CU-based pricing.
With host-based pricing, New Relic charges based on the number of equivalent hosts used in a month. One equivalent host is defined as: a host connected to New Relic for 750 hours (750 hours used as standard month size). If a host is connected to New Relic at any time during an hour, that hour counts towards the host calculation.
These hours can be divided across multiple hosts. For example, you might have three hosts that are each connected to New Relic for 250 hours during one month: these hours would add up to equal one equivalent host.
Each host is counted separately for each New Relic account the host reports data to. For example, if you have a parent account with two child accounts, each running applications on the same single host for 750 hours in a given month, the usage for the parent account will be 2 equivalent hosts.
Once connected to New Relic, hosts are distinguished by their unique hostnames. A host is connected to New Relic when the language agent is active and is deployed on the host. New Relic does not charge by containers (such as Docker or Cloud Foundry), JVMs, or application instances; it charges by the hosts running those containers or application instances.
New Relic APM gives you a choice between host-based pricing and CU-based pricing. Host-based pricing is ideal if you have mainly static environments, consisting of hosts you manage in your own data center.
To understand how New Relic computes both host-based pricing and CU-based pricing, it's important to understand how the word host is used. A host can be one of the following:
A physical machine is a hardware-based device with dedicated physical resources, including memory, processing, and storage. Each machine has its own OS which applications run on.
A virtual machine (VM) is the software implementation of a physical machine that executes programs like a physical machine. One or more virtual machines can run on a physical machine. Each virtual machine has its own OS and allocated virtual machine resources such as RAM and CPU.
A cloud instance is a type of virtual machine that is run in the public cloud. In this context, virtual machines and cloud instances are different from Java Virtual Machines (JVMs) and containers.
For New Relic's pricing calculation purposes, a month is defined as 750 hours.
Prorated billing
If you upgrade your subscription partway through your billing period, you will be subject to a prorated charge for the higher level of service over the remainder of your billing period. This will be invoiced or charged to your credit card when the upgrade is submitted. You will be notified about this charge as part of the subscription change process.
If you have questions, contact your New Relic account representative. If you need to report billing issues, contact New Relic's Billing Department.
Manage subscription and billing settings
Important
Note that as of July 30 2020, we have a newer pricing model. To learn more, see Overview of pricing.
The account Owner can perform many subscription self-service functions directly from the user interface: