Region and Cloud Provider Price Differentials for Atlas

Parent: Atlas Cost Planning: Region Pricing, Estimation, Scheduled Scaling and Competitor TCO · Published reference · snapshot 2026-10-19 · skill mongodb-operations-expert/references/atlas-cost-planning-region-pricing-estimation-scheduled-scaling-and-competitor-tco.md · viability 3.30 / 5 (research)

↓ Facts as markdown all context files

Atlas prices differ by cloud provider (AWS, Azure, Google Cloud) and by region: the Atlas docs state that the provider and region choice affects the cost of a cluster, and the pricing page quotes dedicated-tier base prices for one reference region per provider (AWS us-east-1, Azure eastus2, Google Cloud us-central1) while only Online Archive lists rates region by region. Backup storage, data transfer (cheapest within a region, dearest across providers or to the Internet) and multi-region nodes also vary by provider and region. The pack holds 85 source-anchored units from 5 sources (4 hosts) across 9 facets, mostly measures and facts.

These notes link each claim to its source. Some citations identify archived research reports that are no longer hosted on this site. A published reference means the content is available; it does not certify independent review or accuracy.Read the editorial policy and follow the sources before relying on a claim.

Definitions

Atlas docs state that the choice of cloud provider and region affects cluster cost. For multi-region clusters, cost depends on the number and location of additional regions; the creation UI shows the tier cost for the Preferred Region only, and the Cluster Overview shows the true total. [source]
The cost for Cloud Backups is calculated per GB per month. Rates vary between cloud providers and between regions within a given cloud provider. [source]
_[1] Based on Virginia (eastus2) region._ [source] — Search nodes footnote, Azure
Atlas tabulates data transfer costs daily. Pricing varies by cloud provider and by the region of the source and destination nodes. This page describes sources of data transfer costs, pricing by provider, and strategies to reduce costs. [source]
Atlas supports deploying clusters onto Amazon Web Services, the Google Cloud Platform, and Microsoft Azure. The choice of cloud service provider and region or regions for the Atlas project affects the cost of running a Atlas cluster. [source]
_[2] Based on N-Virginia (us-east-1) region. This price includes the default (minimum) storage size. Cost varies if storage is customized._ [source] — AWS dedicated-tier footnote
_[2] Based on Virginia (eastus2) region. This price includes the default (minimum) storage size. Cost varies if storage is customized._ [source] — Azure dedicated-tier footnote
_[2] Based on Iowa (us-central1) region. This price includes the default (minimum) storage size. Cost varies if storage is customized._ [source] — Google Cloud dedicated-tier footnote

Structure and components

- **Cluster tier and type:** The selected tier is the foundational cost driver. Higher tiers provide more dedicated resources and capabilities. - **Cloud provider and region:** Costs vary slightly across AWS, Google Cloud, and Azure, and between different geographic regions. - **Data storage:** Includes the size of your data and indexes. - **Data transfer (networking):** Charges mainly apply to data moving out of your Atlas cluster (egress) or between different regions/cloud providers. Inbound data transfers are typically free. Free and Flex tiers are not charged for outgoing data. - [source] — Atlas FAQ: cost drivers

How it works

Multi-region cluster costs depend on the number of and location of additional regions selected. When creating a cluster, Atlas displays the cluster tier cost based on only the Preferred Region of the cluster. You can see the total cost of running the cluster in the Cluster Overview. [source]
Depending on the choice of cloud service provider, Atlas provides customization options for cluster storage capacity and the speed of that storage. If you add capacity or speed, you incur additional costs on top of the base cost. For multi-region clusters, the per-cluster cost, including any selected customizations, is relative to the Preferred Region. The Cluster Overview box shows your overall charges. [source] — Provider-dependent storage and IOPS options
Cross region data transfer when you copy your backups to another region. [source] — Additional Backup Copies
Incrementality is determined by your cluster's cloud service provider. To compute the cost for Cloud Backups, Atlas obtains the raw metric data from the cloud providers and calculates the total size of all snapshots based on the region where it stores the snapshot and the amount of storage used per month. [source] — Billing uses snapshot storage region
If Atlas must retain more than one snapshot, Atlas stores the new snapshot in the same region as the cluster's current backup node. Atlas continues using that backup node for snapshots and snapshot storage. [source]
If you have fast disk pre-warming enabled for an M40+ cluster hosted on AWS, Atlas may temporarily provision a higher performance AWS storage volume when replacing a node or provisioning an additional node. This reduces how long the Cloud-based initial sync takes. [source] — AWS only, M40+
Atlas adds the cost of the higher performance disk to your regular storage costs in your monthly Atlas bill. You may notice a higher storage cost than expected in your Atlas bill in months where Atlas provisions or replaces a node on an M40+ AWS cluster. [source] — AWS only, M40+
When you switch your cluster from Gen1 to Gen2, your cluster may have a higher IOPS rate than the baseline included with your storage capacity. After switching to Gen2, we recommend you adjust your storage capacity and IOPS rate independently to fit your workload and optimize your costs. To learn more, see Change a Cluster's Generation. [source] — Gen1 to Gen2 switch

Parameters and configuration

Atlas measures storage speed as maximum IOPS. Each Atlas cluster tier offers a default storage speed that is included in the cluster's per-hour cost. The choice of cloud service provider and cluster affects the available storage speed customization options and the cost of selecting a custom storage speed. [source] — Provider-dependent storage speed options
Gen2 Dedicated clusters have a baseline minimum IOPS based on the cluster's disk storage. The charges from Atlas for Gen2 cluster storage capacity include the baseline minimum IOPS for that disk size. On top of the baseline minimum IOPS, you can provision Extended Standard IOPS for Gen2 Dedicated clusters. Atlas charges separately for Extended Standard IOPS you provision beyond the baseline IOPS. To learn more about your cluster's baseline minimum IOPS rate, see Extended Standard IOPS. [source] — Gen2 dedicated clusters
All clusters use SSD persistent disks with fixed maximum IOPS based on the cluster storage capacity. The maximum IOPS increases as storage capacity increases. The cost of the increased maximum IOPS is included in the cost of the increased storage capacity. To learn more about the Google Cloud persistent disks, see Persistent Disks. [source] — Google Cloud persistent disks

How-to and procedures

Modify the backup policy to reduce the number of snapshots automatically copied to additional regions [source] — Cost-reduction option
- Avoid queries that re-read client data or re-write existing cluster data. - Use query projections to only retrieve necessary fields. - Deploy applications in the same cloud region as the Atlas cluster. - Enable network compression in client drivers to reduce data volume. [source] — Atlas FAQ: ways to cut data transfer
Source write queries from your Highest Priority Region whenever possible. For more information on region priorities, see Electable Nodes for High Availability. [source]
Ensure that queries originate from the same cloud region and provider as your cluster whenever possible. [source]
Ensure read queries use the preference "nearest." [source]

Measurements and reference values

In those reference regions, M30 (8 GB RAM, 2 vCPU) lists at $0.54/hr on AWS, $0.51/hr on Azure and $0.44/hr on GCP; M50 lists at $2.00, $1.95 and $1.66/hr; M10 is $0.08/hr on all three. GCP is the cheapest at M30 and above, roughly 18% below AWS at M30. [source]
Data transfer costs for downloading the snapshot over the public Internet or for downloading the snapshot over private endpoints for Atlas clusters on AWS or Azure with private endpoints. These costs vary by cloud provider and region. To learn more, see Private Endpoint Billing. [source] — Restore downloads; AWS and Azure private endpoints
Atlas states most customers spend under 10% of budget on data transfer; mitigations are co-locating apps in the cluster's region and provider and using nearest read preference for unavoidable cross-region reads. [source]
Real-world bills tend to surprise teams who only scoped the hourly instance rate. Consider a common SaaS setup: one M10 cluster for development and staging (~$57/month) and one M30 for production (~$190/month), both on AWS us-east-1. Add backup storage at roughly $0.14/GB for 40 GB ($5.60/month) plus modest cross-region data transfer, and you’re already at $260–$280/month before any support plans or additional Atlas features. Scale to an M50 production cluster with a global multi-region deployment and Atlas Search enabled, and $1,000+/month is realistic. [source] — Third-party example, AWS us-east-1
| Region | Data Storage[1] | Time Series Data Storage[2] | Archival Access[3] | Data Process[4] | | --- | --- | --- | --- | --- | | US East (N. Virginia) | 0.001578 | 0.0032 | 0.0010000 | $5 per TB Processed | | US West (Oregon) | 0.001578 | 0.0032 | 0.0010000 | " | | Canada (Central) | 0.001715 | 0.00348 | 0.0011000 | " | | South America (Sao Paulo) | 0.002779 | 0.005634 | 0.0014000 | " | [source] — Online Archive rates by region, AWS Americas
| Region | Data Storage[1] | Time Series Data Storage[2] | Archival Access[3] | Data Process[4] | | --- | --- | --- | --- | --- | | US East (N. Virginia) | 0.001578 | 0.0032 | 0.0009 | $5 per TB Processed | | South America (Sao Paulo) | 0.002798 | 0.005599 | 0.0014 | " | [source] — Online Archive rates by region, Azure Americas
| Region | Data Storage[1] | Time Series Data Storage[2] | Archival Access[3] | Data Process | | --- | --- | --- | --- | --- | | US Central (Iowa) | 0.001348 | 0.002695 | 0.0008 | $5 per TB Processed | [source] — Online Archive rates by region, Google Cloud Americas
| Cluster Tier | Storage (GB) | RAM (GB) | vCPUs | Base Price[1] | | --- | --- | --- | --- | --- | | S20 | 106 GB | 4 GB | 2 vCPUs | $0.12/hr | | S30 | 213 GB | 8 GB | 4 vCPUs | $0.24/hr | | S40 | 426 GB | 16 GB | 8 vCPUs | $0.48/hr | | S50 | 855 GB | 32 GB | 16 vCPUs | $0.99/hr | | S60 | 1710 GB | 64 GB | 32 vCPUs | $1.77/hr | | S70 | 2564 GB | 96 GB | 48 vCPUs | $2.50/hr | | S80 | 3420 GB | 128 GB | 64 vCPUs | $3.26/hr | [source] — Search nodes, AWS, High CPU
| Cluster Tier | Storage (GB) | RAM (GB) | vCPUs | Base Price[1] | | --- | --- | --- | --- | --- | | S30 | 53 GB | 8 GB | 1 vCPUs | $0.11/hr | | S40 | 106 GB | 16 GB | 2 vCPUs | $0.21/hr | | S50 | 213 GB | 32 GB | 4 vCPUs | $0.43/hr | | S60 | 426 GB | 64 GB | 8 vCPUs | $0.89/hr | | S80 | 855 GB | 128 GB | 16 vCPUs | $1.68/hr | | S90 | 1710 GB | 256 GB | 32 vCPUs | $3.12/hr | | S100 | 2564 GB | 384 GB | 48 vCPUs | $4.40/hr | | S110 | 3420 GB | 512 GB | 64 vCPUs | $5.87/hr | [source] — Search nodes, AWS, Low CPU
| Cluster Tier | Storage (GB) | RAM (GB) | vCPUs | Base Price[1] | | --- | --- | --- | --- | --- | | S20 | 128 GB | 4 GB | 2 vCPUs | $0.14/hr | | S30 | 337 GB | 8 GB | 4 vCPUs | $0.27/hr | | S40 | 362 GB | 16 GB | 8 vCPUs | $0.57/hr | | S50 | 674 GB | 32 GB | 16 vCPUs | $1.15/hr | | S60 | 1348 GB | 64 GB | 32 vCPUs | $2.22/hr | [source] — Search nodes, Google Cloud, High CPU
| Cluster Tier | Storage (GB) | RAM (GB) | vCPUs | Base Price[1] | | --- | --- | --- | --- | --- | | S30 | 128 GB | 8 GB | 2 vCPUs | $0.16/hr | | S40 | 337 GB | 16 GB | 2 vCPUs | $0.24/hr | | S50 | 337 GB | 32 GB | 4 vCPUs | $0.43/hr | | S60 | 337 GB | 64 GB | 8 vCPUs | $0.87/hr | | S70 | 674 GB | 96 GB | 12 vCPUs | $1.24/hr | | S80 | 674 GB | 128 GB | 16 vCPUs | $1.79/hr | | S90 | 1348 GB | 256 GB | 32 vCPUs | $3.45/hr | [source] — Search nodes, Google Cloud, Low CPU
| Cluster Tier | Storage (GB) | RAM (GB) | vCPUs | Base Price[1] | | --- | --- | --- | --- | --- | | S20 | 80 GB | 4 GB | 2 vCPUs | $0.15/hr | | S30 | 161 GB | 8 GB | 4 vCPUs | $0.30/hr | | S40 | 322 GB | 16 GB | 8 vCPUs | $0.62/hr | | S50 | 644 GB | 32 GB | 16 vCPUs | $1.27/hr | | S60 | 1288 GB | 64 GB | 32 vCPUs | $2.29/hr | | S70 | 1932 GB | 96 GB | 48 vCPUs | $3.23/hr | | S80 | 2576 GB | 128 GB | 64 vCPUs | $4.22/hr | [source] — Search nodes, Azure, High CPU
| Cluster Tier | Storage (GB) | RAM (GB) | vCPUs | Base Price[1] | | --- | --- | --- | --- | --- | | S40 | 80 GB | 16 GB | 2 vCPUs | $0.23/hr | | S50 | 161 GB | 32 GB | 4 vCPUs | $0.47/hr | | S60 | 322 GB | 64 GB | 8 vCPUs | $0.98/hr | | S80 | 644 GB | 128 GB | 16 vCPUs | $1.87/hr | | S90 | 1288 GB | 256 GB | 32 vCPUs | $3.48/hr | | S100 | 1932 GB | 384 GB | 48 vCPUs | $4.92/hr | | S110 | 2576 GB | 512 GB | 64 vCPUs | $6.55/hr | | S130 | 3865 GB | 672 GB | 96 vCPUs | $9.83/hr | | S135 | 4080 GB | 672 GB | 104 vCPUs | $11.71/hr | [source] — Search nodes, Azure, Low CPU
| Data Processed | Data Transferred and Returned | | --- | --- | | $5 per TB with a 10MB minimum per query | Data transfer costs are based on the rates set by your cloud service provider | [source] — Data Federation: transfer billed at cloud-provider rates
| Cluster Tier | Storage[1] | RAM | vCPU | Base Price[2] | | --- | --- | --- | --- | --- | | M10 | 10–128 GB | 2 GB | 2 vCPUs[3] | $0.08/hr[4] | | M20 | 20–256 GB | 4 GB | 2 vCPUs[3] | $0.20/hr | | M30 | 40–512 GB | 8 GB | 2 vCPUs | $0.54/hr | | M40 | 80 GB–1 TB | 16 GB | 4 vCPUs | $1.04/hr | | M50 | 160 GB–4 TB | 32 GB | 8 vCPUs | $2.00/hr | | M60 | 320 GB–4 TB | 64 GB | 16 vCPUs | $3.95/hr | | M80 | 750 GB–4 TB | 128 GB | 32 vCPUs | $7.30/hr | | M140 | 1–4 TB | 192 GB | 48 vCPUs | $10.99/hr | | M200 | 1.5–4 TB | 256 GB | 64 vCPUs | $14.59/hr | | M300 | 2–4 TB | 384 GB | 96 vCPUs | $21.85/h [source] — Dedicated tiers, AWS, us-east-1 base prices
| Cluster Tier | Storage[1] | RAM | vCPU | Base Price[2] | | --- | --- | --- | --- | --- | | M10 | 8–128 GB | 2 GB | 1 vCPU[3] | $0.08/hr[4] | | M20 | 16–256 GB | 4 GB | 1 vCPU[3] | $0.19/hr | | M30 | 32–512 GB | 8 GB | 2 vCPUs | $0.51/hr | | M40 | 64 GB–1 TB | 16 GB | 4 vCPUs | $0.99/hr | | M50 | 128 GB–4 TB | 32 GB | 8 vCPUs | $1.95/hr | | M60 | 128 GB–4 TB | 64 GB | 16 vCPUs | $3.73/hr | | M80 | 256 GB–4 TB | 128 GB | 32 vCPUs | $7.42/hr | | M200 | 256 GB–4 TB | 256 GB | 64 vCPUs | $13.65/hr | | M300 | 512 GB–4 TB | 384 GB | 48 vCPUs | $16.63/hr | | M400 | 512 GB–4 TB | 432 GB | 64 vCP [source] — Dedicated tiers, Azure, eastus2 base prices
| Cluster Tier | Storage[1] | RAM | vCPU | Base Price[2] | | --- | --- | --- | --- | --- | | M10 | 10–128 GB | 1.7 GB | 0.5 vCPUs[3] | $0.08/hr[4] | | M20 | 20–256 GB | 3.75 GB | 1 vCPUs[3] | $0.19/hr | | M30 | 40–512 GB | 8 GB | 2 vCPUs | $0.44/hr | | M40 | 80 GB–1 TB | 16 GB | 4 vCPUs | $0.86/hr | | M50 | 160 GB–4 TB | 32 GB | 8 vCPUs | $1.66/hr | | M60 | 320 GB–4 TB | 64 GB | 16 vCPUs | $3.29/hr | | M80 | 750 GB–4 TB | 128 GB | 32 vCPUs | $6.13/hr | | M140 | 1-4 TB | 192 GB | 48 vCPUs | $9.54/hr | | M200 | 1.5–4 TB | 256 GB | 64 vCPUs | $12.96/hr | | M250 | 1.75–4 TB | 320 GB | 80 vCPU [source] — Dedicated tiers, Google Cloud, us-central1 base prices
| Cluster Tier | Storage (GB) | RAM (GB) | vCPUs | Base Price[1] | | --- | --- | --- | --- | --- | | S40-S | 421 GB | 16 GB | 2 vCPUs | $0.25/hr | | S50-S | 843 GB | 32 GB | 4 vCPUs | $0.52/hr | | S60-S | 1687 GB | 64 GB | 8 vCPUs | $0.94/hr | | S80-S | 3375 GB | 128 GB | 16 vCPUs | $1.89/hr | | S90-S | 6750 GB | 256 GB | 32 vCPUs | $3.76/hr | [source] — Search nodes, AWS, Storage-Optimized
| Region | Data Storage[1] | Time Series Data Storage[2] | Archival Access[3] | Data Process[4] | | --- | --- | --- | --- | --- | | Asia Pacific (Mumbai) | 0.001716 | 0.003432 | 0.0010000 | $5 per TB Processed | | Asia Pacific (Singapore) | 0.001716 | 0.003432 | 0.0010000 | " | | Asia Pacific (Sydney) | 0.001716 | 0.003432 | 0.0011000 | " | | Asia Pacific (Tokyo) | 0.001716 | 0.003432 | 0.0009250 | " | | Asia Pacific (Seoul) | 0.001716 | 0.003432 | 0.000875 | " | [source] — Online Archive rates by region, AWS Asia Pacific
| Region | Data Storage[1] | Time Series Data Storage[2] | Archival Access[3] | Data Process[4] | | --- | --- | --- | --- | --- | | Europe (Frankfurt) | 0.001681 | 0.003407 | 0.0010750 | $5 per TB Processed | | Europe (Ireland) | 0.001578 | 0.0032 | 0.0010000 | " | | Europe (London) | 0.001647 | 0.00334 | 0.0010500 | " | [source] — Online Archive rates by region, AWS Europe/Middle East
| Region | Data Storage[1] | Time Series Data Storage[2] | Archival Access[3] | Data Process[4] | | --- | --- | --- | --- | --- | | Europe (Netherlands) | 0.002 | 0.003334 | 0.001 | $5 per TB Processed | [source] — Online Archive rates by region, Azure Europe
| Region | Data Storage[1] | Time Series Data Storage[2] | Archival Access[3] | Data Process | | --- | --- | --- | --- | --- | | Europe (Belgium) | 0.001348 | 0.002695 | 0.0008 | $5 per TB Processed | [source] — Online Archive rates by region, Google Cloud Europe
Enabling Additional Backup Copies for your cluster, and using additional storage in other regions. For example, if you copy all of your backups to one additional region, you pay for approximately twice the storage: an amount for your standard backup, and approximately the same amount for your copies stored in the other region (storage costs vary by region). [source] — Additional Backup Copies; storage costs vary by region
You back up 400 GB of data from a cluster in an AWS region with a $0.14 per month Cost per GB, yielding a cost of $56.00. [source] — Docs worked example, AWS region
| Tier (ops/second) | Total Hourly Cost | Total Monthly Cost[1] | | --- | --- | --- | | 0 - 100 (Base) | $0.0110 | $8.00 | | 100 - 200 | $0.0205 | $15.00 | | 200 - 300 | $0.0288 | $21.00 | | 300 - 400 | $0.0356 | $26.00 | | 400 - 500 | $0.0411 | $30.00 | [source] — Flex tiers; pricing page lists the same table for all three providers
For exports over AWS PrivateLink connections, Atlas charges $0.01 per hour to maintain the connection. Atlas includes the $0.01 per GB data processing charge for AWS PrivateLink in the base $0.125 per GB export price. [source] — Export over AWS PrivateLink
_[1]Data transfer costs are not included in the above pricing._ [source] — Stream Processing footnote: data transfer billed separately
Data transfers – Pricing is based on usage for M10 and larger instances. It costs $0.01 per GB for same-region transfers, $0.02 per GB for cross-region transfers, and $0.09 per GB for data you send to the internet. [source] — Third-party figures, AWS-style rates
| Region | Data Storage[1] | Time Series Data Storage[2] | Archival Access[3] | Data Process[4] | | --- | --- | --- | --- | --- | | US East (Ohio) | 0.001578 | 0.0032 | 0.0010000 | " | | US West (N. California) | 0.001784 | 0.00362 | 0.0011000 | " | [source] — Online Archive rates by region, AWS Americas (more regions)
| Region | Data Storage[1] | Time Series Data Storage[2] | Archival Access[3] | Data Process[4] | | --- | --- | --- | --- | --- | | Asia Pacific (Hong Kong) | 0.001715 | 0.00348 | 0.0010000 | " | | Asia Pacific (Osaka-Local) | 0.001715 | 0.00348 | 0.0009250 | " | | Asia Pacific (Seoul) | 0.001715 | 0.00348 | 0.0008750 | " | [source] — Online Archive rates by region, AWS Asia Pacific (more regions)
| Region | Data Storage[1] | Time Series Data Storage[2] | Archival Access[3] | Data Process[4] | | --- | --- | --- | --- | --- | | Europe (Paris) | 0.001647 | 0.00334 | 0.0010500 | " | | Europe (Stockholm) | 0.001578 | 0.0032 | 0.0010000 | " | | Europe (Milan) | 0.001647 | 0.00334 | 0.0010000 | " | | Middle East (Bahrain) | 0.001715 | 0.00348 | 0.0011000 | " | [source] — Online Archive rates by region, AWS Europe (more regions)
Atlas charges $0.125 per GB of data exported to the AWS S3 bucket, Azure Blob Storage Container, or Google Cloud Storage bucket in addition to the data transfer cost incurred from the cloud service itself. Atlas compresses the data before exporting. To estimate the amount of data being exported, add up the dataSize of each database in your cluster. This total should correspond to the uncompressed size of your export, which would be the maximum cost incurred from Atlas for the data export operation. [source] — Data export to cloud storage
| Stream Processor Tier | vCPU | RAM | Bandwidth | Max Parallelism | Cost Per Hour[1] | | --- | --- | --- | --- | --- | --- | | SP2 | 0.25 | 512 MB | 50 Mbps | 1 | $0.06 to $0.08 | | SP5 | 0.5 | 1 GB | 125 Mbps | 2 | $0.11 to $0.17 | | SP10 | 1 | 2 GB | 200 Mbps | 8 | $0.19 to $0.30 | | SP30 | 2 | 8 GB | 750 Mbps | 16 | $0.39 to $0.62 | | SP50 | 8 | 32 GB | 2500 Mbps | 64 | $1.56 to $2.49 | [source] — Stream Processing tiers, AWS; cost per hour is a range
| Stream Processor Tier | vCPU | RAM | Bandwidth | Max Parallelism | Cost Per Hour[1] | | --- | --- | --- | --- | --- | --- | | SP2 | 0.25 | 512 MB | 50 Mbps | 1 | $0.06 to $0.07 | | SP5 | 0.5 | 1 GB | 125 Mbps | 2 | $0.11 to $0.14 | | SP10 | 1 | 2 GB | 200 Mbps | 8 | $0.19 to $0.27 | | SP30 | 2 | 8 GB | 750 Mbps | 16 | $0.39 to $0.55 | | SP50 | 8 | 32 GB | 2500 Mbps | 64 | $1.56 to $2.18 | [source] — Stream Processing tiers, Azure
| Stream Processor Tier | vCPU | RAM | Bandwidth | Max Parallelism | Cost Per Hour[1] | | --- | --- | --- | --- | --- | --- | | SP2 | 0.25 | 512 MB | 50 Mbps | 1 | $0.055 to $0.061 | | SP5 | 0.5 | 1 GB | 125 Mbps | 2 | $0.11 to $0.12 | | SP10 | 1 | 2 GB | 200 Mbps | 8 | $0.19 to $0.21 | | SP30 | 2 | 8 GB | 750 Mbps | 16 | $0.39 to $0.43 | | SP50 | 8 | 32 GB | 2500 Mbps | 64 | $1.56 to $1.72 | [source] — Stream Processing tiers, Google Cloud
Queries from on-premises environments into Atlas, across cloud providers, or between continents on the same cloud provider incur the greatest data transfer costs. [source] — Highest-cost transfer paths
Backups – Pricing starts at $0.14 per GB per month, depending on the size of your datafiles on the disk. [source] — Third-party guide

Problems, failure modes and limitations

Customers with existing deployments in legacy regions can continue to access their data, but new archives cannot be created in these regions. [source] — Online Archive, AWS legacy regions

Comparisons and alternatives

Tier shapes are not identical across providers: M10 is 2 vCPU/2 GB on AWS, 1 vCPU/2 GB on Azure and 0.5 vCPU/1.7 GB on GCP at the same $0.08/hr list price, and the GCP M20 has 3.75 GB RAM vs 4 GB elsewhere. Price per hour alone is not like-for-like. [source]
M30+ Dedicated clusters on AWS or Google Cloud are available in cluster generations Gen1 or Gen2. Gen1 clusters have IOPS, storage, and costs that differ from Gen2 clusters of the same cluster class. [source] — AWS and Google Cloud only
For multi-region deployments, costs are higher than single-region clusters, as they require multiple nodes across regions and incur additional replication and data transfer charges, rather than following a fixed starting price. [source] — Third-party guide
Multi-region clusters — These carry a premium over single-region equivalents even at identical instance sizes [source] — Third-party guide

Facts and statements

A third-party guide says AWS us-east-1 is typically among the lowest-cost regions and quotes $0.01/GB same-region and $0.02/GB cross-region transfer plus $0.09/GB Internet egress; these are generic AWS-style figures, not Atlas-published rates. [source] — Third-party claim, not Atlas-published
Pricing varies by cloud provider and region (with AWS us-east-1 typically among the lowest-cost options), and does not include additional charges such as backups, data transfer, or optional Atlas features. [source] — Third-party claim, not Atlas-published
Export Logs to External Services routes through the Atlas control plane in AWS us-east-1 regardless of cluster region or provider, so clusters elsewhere pay cross-region or inter-cloud transfer on top of Internet egress. [source]
The public Atlas pricing page quotes dedicated-tier base prices for a single reference region per provider: AWS N. Virginia (us-east-1), Azure Virginia (eastus2), GCP Iowa (us-central1). Prices include default storage and change if storage is customized. [source]
Atlas data-transfer pricing varies by cloud provider and by the region of source and destination nodes. Transfers rank from cheapest to costliest: same region/zone, cross-region within a provider, then out to the Internet or another provider. Inbound data is free; multi-region clusters can have higher transfer costs. [source]
Cloud Backup storage is billed per GB per month with rates that vary between providers and between regions within a provider (docs example: $0.14/GB-month for an AWS region); continuous-backup snapshot/oplog rates are likewise tabulated by provider and region. [source]
Export Logs to External Services routes log traffic through the Atlas control plane in AWS us-east-1, regardless of your cluster's region or cloud provider. If your cluster is not in AWS us-east-1, you incur cross-region or inter-cloud data transfer charges in addition to Internet egress costs. [source]
Push Logs to AWS S3 exports logs directly from the data node to an S3 bucket in the cluster's region. Standard Internet egress costs apply. [source]
M40, M50, M60, M80, M200, and M400 cluster tiers support Non-Volatile Memory Express Solid State Drives (NVMe SSDs) storage for AWS. These are dedicated clusters and automatically scale up to the next higher tier once 90% of available storage is used. These clusters are available in the Americas, Europe, and Asia Pacific regions. You can’t pause an NVMe cluster. [source] — NVMe tiers, AWS regions
Multi-region clusters might have higher data transfer costs depending on the number and location of additional regions, as well as the number of clusters deployed to each region. [source]
M60, M80, M200, M300, M400, and M600 dedicated clusters support NVMe on Microsoft Azure. See the availability zones here and here. You won’t be able to pause an NVMe cluster. [source] — NVMe tiers, Azure
- Fluctuations in usage - Configuration adjustments - Auto-scaling behavior - New features - Cloud provider price changes [source] — Atlas FAQ: further factors over time
MongoDB hosts and operates the free Atlas Live Migration Service to help you migrate existing MongoDB databases to MongoDB Atlas. MongoDB doesn't charge for any incoming data transfers to an Atlas cluster. Learn more about migrating to Atlas. [source] — Inbound transfer free
AWS instance type, AWS region, consumption, and other factors, like data transfer and backup policy, will also affect your MongoDB spend on AWS. [source] — Third-party guide
Select your cloud provider to view the applicable data transfer costs. [source] — Rates shown per selected provider
Precisely how much you’ll spend will depend on your cluster configuration (Azure instance types, size, region, vCPU, and RAM), Availability Zone, and usage. Here are the available MongoDB cluster tiers on Azure to give you an idea: [source] — Third-party guide, Azure tiers
Data egress — Charges accumulate whenever data crosses a region or cloud boundary, and scale quickly with read-heavy workloads [source] — Third-party guide
(4) Cross Region: - Cross region replicas incur data transfer charges on top of consumption-based charges [source] — IBM community post

Related concepts

price — is a related of Region and Cloud Provider Price Differentials for Atlas
AWS — is a instance of Region and Cloud Provider Price Differentials for Atlas
region — is a related of Region and Cloud Provider Price Differentials for Atlas
data transfer — is a part of Region and Cloud Provider Price Differentials for Atlas
cloud provider — is a related of Region and Cloud Provider Price Differentials for Atlas
dedicated tier — is a hyponym of Region and Cloud Provider Price Differentials for Atlas
reference region — is a part of Region and Cloud Provider Price Differentials for Atlas
per GB — is a measure of Region and Cloud Provider Price Differentials for Atlas
hourly rate — is a measure of Region and Cloud Provider Price Differentials for Atlas
M30 — is a instance of Region and Cloud Provider Price Differentials for Atlas
Online Archive — is a part of Region and Cloud Provider Price Differentials for Atlas
multi-region cluster — is a part of Region and Cloud Provider Price Differentials for Atlas
Search nodes — is a part of Region and Cloud Provider Price Differentials for Atlas
cloud backup — is a part of Region and Cloud Provider Price Differentials for Atlas
IOPS — is a measure of Region and Cloud Provider Price Differentials for Atlas
Vector Search nodes — is a part of Region and Cloud Provider Price Differentials for Atlas
Stream Processing — is a part of Region and Cloud Provider Price Differentials for Atlas
co-locate — is a part of Region and Cloud Provider Price Differentials for Atlas
snapshot distribution — is a part of Region and Cloud Provider Price Differentials for Atlas
Export Logs to External Services — is a instance of Region and Cloud Provider Price Differentials for Atlas

Children

Atlas PrivateLink regional endpoint rates (frontier, viability 2.70 / 5, below research gate)
Multi-region cluster cost premium (frontier, viability 3.05 / 5, below research gate)
Backup storage rates by region (frontier, viability 2.45 / 5, below research gate)

Frontier under this node: Atlas PrivateLink regional endpoint rates (2.70), Backup storage rates by region (2.45), Multi-region cluster cost premium (3.05)

← the whole tree · 3D view· how to read this page