Skip to main content

nRF Cloud plans

This page explains plans (subscriptions to services) in nRF Cloud. Depending on the number of devices associated with your team, as well as your service needs, there are suitable plans for service access and billing.

Plans

Plans are associated with a single team. For example, you might manage an Enterprise account but create a second free plan team for other development projects.

nRF Cloud offers services according to three plans:

nRF Cloud plan pricing

The nRF Cloud portal has the most up-to-date pricing information.

Developer

The Developer plan is free to use. You are on this plan when you create a new nRF Cloud account. This type is suitable for developers with small-scale workflows and a small number of devices.

The Developer plan includes the following team-wide service allowances each month:

  • 10 devices of any type
  • 500 requests for Location Services across all devices
  • 50 over-the-air firmware update job executions:
    • An execution is a deployment attempt to a single device.
    • A job execution counts toward this limit when you deploy the update job. Executions are canceled if they exceed the limit.
  • 3000 stored messages

Pro

The Pro plan is for commercial teams with fewer than 2000 devices. It offers access to services based on the number of requests made to nRF Cloud services. See Managing your nRF Cloud account and plan for more information on service charges.

Enterprise

The Enterprise plan is for commercial teams managing 2000 or more devices. To learn more about service charges and limits, see Managing your nRF Cloud account and plan.

Contact Nordic Semiconductor Sales under the Sales related questions tab to ask about setting up an nRF Cloud Enterprise account.

Service limits

Service costs and request limits depend on your team's plan. API limits largely apply to the free Developer plan, except for limits on Location Services.

If API operations in your team begin to fail, verify that you have not exceeded your plan limits from the Dashboard. See Managing your nRF Cloud plan for instructions.

Once you reach your plan's limits, REST API operations for that service return a 400 error with an nRFCode of 40005 unless you allow overage fees. These requests do not resolve.

Attempting a request over MQTT that exceeds your plan limit does not return an error message. The message is dropped, and the request does not resolve.

note

Developer plan limits for specific services apply to the entire team. Pro and Enterprise limits for Location Services apply to individual devices.

Messages

nRF Cloud temporarily stores messages between your devices and nRF Cloud. One operation, such as a Location Services GNSS request, can generate multiple messages as the device and nRF Cloud communicate. A FOTA operation can generate several messages as the device and server both request and update their statuses.

If you use the MQTT operation m/d/${deviceId}/d2c/bulk to bundle messages, each message in the bundle still counts toward the stored messages limit.

You can retrieve messages associated with a specific device over REST or MQTT.

note

Messages associated with Location Services and FOTA are excluded from the total message count and billing. You are charged for the requests or jobs, but not for messages associated with them.

Location Services limits

The following monthly limits for Pro and Enterprise plans apply to Location Services requests by a single device:

  • A-GPS, P-GPS, MCELL and Wi-Fi: 200 requests to each service
  • SCELL: 1000 requests

Requests over this limit resolve but result in overage fees. If you forbid overage fees, nRF Cloud will refuse excessive requests. See Managing your nRF Cloud account and plan for more information.

Location data is stored for six months.

Billing

Billing is calculated monthly based on your plan and service usage. The billing period resets on the first of each calendar month. Service limits also reset on the first of the month.

See the guide to Managing your nRF Cloud account and plan for more information on setting up and managing payment methods.

Downgrading

Downgrading your account takes effect at the rollover to the next billing period. This means that you are responsible for charges according to your use of nRF Cloud services for the rest of that billing period.

For example, if you initiate a downgrade on the seventh of the month, you can still access services until the end of the month. You will receive an invoice for use of services until the downgrade takes effect.