Serverless Instance Costs
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 Cluster Type.
Note
Expiration operations
triggered by TTL Indexes might generate
RPUs and WPUs . The volume of these additional processing
units typically incurs only a small fee relative to your overall
costs.
Usage Cost Summary
Operation pricing varies between cloud providers and geographic regions. All operations are billed per day.
Name | Description | Price |
|---|---|---|
Read Processing Unit ( | Read operations to the database. Atlas calculates RPUs based on the number of read operations, document bytes read (in 4KB increments), and index bytes read (in 256 byte increments) per operation. RPUs are calculated on a daily basis and start at 0 each day. | The price for each million |
Write Processing Unit ( | Write operations to the database. Atlas calculates WPUs based on document bytes and index bytes written (up to 1KB). If a document and index exceed 1KB, Atlas covers each excess chunk of 1KB with an additional WPU. Atlas calculates WPUs on a daily basis and WPUs start at 0 each day. | Range from $0.90 to $2.20 per million |
Storage | Logical document and index storage. This value includes the number of bytes of all uncompressed BSON documents stored in all collections, plus the bytes stored in their associated indexes. | Range from $0.20 to $0.70 per |
Continuous Backup | Point-in-Time backups triggered by write events. | Range from $0.20 to $0.60 per |
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. | Range from $2.50 to $6.00 per restore hour. |
Data Transfer | Data transfer to and from the database. [1] If your data transfer costs are a significant portion of your bill, see How to Reduce Data Transfer Costs. |
|
| [1] | (1, 2, 3) RPU and WPU prices are presented per million, but you are
only charged for the amount you use. For example, if WPUs
cost $1.25 per million in your region; 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 (M) RPUs depends on volume of reads
that day. RPUs start at 0 each day. Prices are in cascading
tiers:
Tier | Description | Price |
|---|---|---|
0-50 M | The first 50 million | $0.09 to $0.22/M |
50-550 M | The next 500 million | $0.05 to $0.11/M |
550 M-20.55 B | The next 20 billion | $0.01 to $0.03/M |
20.55+ B | All subsequent | Free |
Example
If your application uses 560 million RPUs in a day, in a region
with prices of $0.10/M, $0.06/M, and $0.02/M by tier, Atlas
charges you $35.20:
$0.10/M for the first 50 million ($5.00).
$0.06/M for the next 500 million ($30.00).
$0.02/M for the last 10 million ($0.20).
If that usage is typical for a day, your application costs approximately $1056 per month ($35.20 per day x 30 days).
In another example, if your application uses 0.5 million RPUs
in a day in the same region, Atlas charges you $0.05:
$0.10/M for the first 0.5 million ($0.05).
If that usage is typical for a day, your application costs approximately $1.50 per month ($0.05 per day x 30 days).
Payment Methods
Warning
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.