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.
Read Processing Unit (
Read operations to the database.
You are charged one
The price for each million
Write Processing Unit (
Write operations to the database.
You are charged one
$1.25 per million.
Logical document and index storage.
Two daily snapshots are included for free.
Restore from Backup
The time required to restore your serverless instance.
Data transfer as part of the backup and restore process is charged separately.
$2.50 per restore hour.
Data transfer to and from the database.
If your data transfer costs are a significant portion of your bill, see How to Reduce Data Transfer Costs.
During the preview period, data transfer costs may be updated to account for the source and destination regions of a transfer.
Read Processing Unit Pricing¶
The price for each million (M)
RPUs depends on volume of reads
that day. Prices are in cascading tiers:
The first 5 million
The next 20 million
The next 50 million
If an application uses 31 million
RPUs in a day, the price for
RPUs is $7.70.
- $0.30/M for the first 5 million ($1.50).
- $0.25/M for the next 20 million ($5).
- $0.20/M for the last 6 million ($1.20).
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: