Serverless Instance Costs
Serverless instances are in a preview release and do not support some Atlas features at this time.
To learn more, see Serverless Instance Limitations.
Serverless instances offer pay-per-operation pricing, meaning that you only pay for the Processing Units consumed by your database operations and storage consumed by your data and indexes. You do not need to specify a cluster size since serverless instances seamlessly scale to accommodate changes in workload traffic.
Serverless instances may be more cost effective for applications with low or intermittent traffic. To learn more about serverless instances and use cases, see Choose a Database Deployment Type.
Usage Costs
Name | Description | Price |
|---|---|---|
Read Processing Unit ( RPU) | Read operations to the database. You are charged one If a document exceeds 4KB or an index exceeds 256B, Atlas
covers each excess chunk of 4KB or 256B with an additional
| The price for each million RPUs decreases based on volume
of reads in a day, starting at $0.30 per million RPUs.
[1]
See Read Processing Unit Pricing for details. |
Write Processing Unit ( WPU) | Write operations to the database. You are charged one If a document and index exceed 1KB, Atlas covers each excess
chunk of 1KB with an additional | $1.25 per million. [1] |
Storage | Logical document and index storage. | $0.25 per GB per month, prorated and billed per day. |
Backup | Daily snapshots. | Two daily snapshots are included for free. |
Restore from Backup | The time required to restore your serverless instance. Important Data transfer as part of the backup and restore process is charged separately. | $2.50 per restore hour. |
Data Transfer | Data transfer to and from the database. Tip If your data transfer costs are a significant portion of your bill, see How to Reduce Data Transfer Costs. | $0.015 per Important During the preview period, data transfer costs may be updated to account for the source and destination regions of a transfer. |
| [1] | (1, 2, 3) RPU and WPU prices are presented per million, but you are
only charged for the amount you use. For example, WPUs
cost $1.25 per million; using 500,000 would cost $0.63. The same is
true for data transfer: you're only charged for the amount you
transfer. |
Read Processing Unit Pricing
The price for each million (MM) RPUs depends on volume of reads
that day. RPUs start at 0 each day. Prices are in cascading
tiers:
Tier | Description | Price |
|---|---|---|
0-5 MM RPUs | The first 5 million RPUs in a day. | $0.30/MM |
5-25 MM RPUs | The next 20 million RPUs in a day. | $0.25/MM |
25-75 MM RPUs | The next 50 million RPUs in a day. | $0.20/MM |
75+ MM RPUs | All subsequent RPUs in a day. | $0.15/MM |
If your application uses 31 million RPUs in a day, Atlas
charges you $7.70:
- $0.30/MM for the first 5 million ($1.50).
- $0.25/MM for the next 20 million ($5).
- $0.20/MM for the last 6 million ($1.20).
If that usage is typical for a day, your application costs approximately $231 per month ($7.70 per day x 30 days).
In another example, if your application uses 0.5 million RPUs
in a day, Atlas charges you $0.15:
- $0.30/MM for the first 0.5 million ($0.15).
If that usage is typical for a day, your application costs approximately $4.50 per month ($0.15 per day x 30 days).
Payment Methods
An unexpected, significant increase in serverless instance usage could result in an expensive invoice. Use billing alerts to monitor usage.
You can pay for serverless instances with:
- A payment method added through the Atlas console,
- an Atlas subscription, or
- Atlas credits.