On this page
The cluster tier dictates the memory, storage, and IOPS specification for each data-bearing server  in the cluster.
You might see different values depending on your selected cloud provider and region.
Shared clusters are economical clusters for getting started with MongoDB and for low-throughput applications. These clusters deploy to a shared environment with access to a subset of Atlas features and functionality. For complete documentation on shared cluster limits and restrictions, see Atlas M0 (Free Cluster), M2, and M5 Limitations.
M0 clusters are free sandbox replica set clusters. You can deploy
M0 cluster per Atlas project. You can
M0 free cluster to an
M2+ shared cluster at any time.
M5 clusters are low-cost shared clusters.
These clusters provide the following additional features and
functionality compared to
- Atlas deploys MongoDB 4.4 for all
Shared Clusters (
M5). However, Shared Clusters do not support all functionality in MongoDB version 4.4 and later. See Atlas M0 (Free Cluster), M2, and M5 Limitations for details.
Atlas supports shared cluster deployment in a subset of Cloud Providers and Regions. Atlas greys out any shared cluster tiers not supported by the selected cloud service provider and region. For a complete list of regions that support shared cluster deployments, see:
Dedicated Clusters for Low-Traffic Applications¶
M20 cluster tiers support development environments and low-traffic
These clusters support replica set deployments only, but otherwise provide full access to Atlas features and functionality.
M20 cluster tiers on AWS and Azure run on
burstable performance infrastructure.
Dedicated Clusters for High-Traffic Applications¶
M30 and higher cluster tiers support production environments with
high traffic applications and large datasets.
These clusters support replica set and sharded cluster deployments with full access to Atlas features and functionality.
Some clusters have variants, denoted by the ❯ character. When you select these clusters, Atlas lists the variants and tags each cluster to distinguish their key characteristics.
NVMe Storage on AWS Clusters¶
For applications hosted on AWS which require low-latency and high-throughput I/O, Atlas offers storage options using locally attached ephemeral NVMe SSDs. The following cluster tiers have an NVMe option, with the size fixed at the cluster tier:
Clusters with NVMe storage use Cloud Backups for backup. You can't disable backup on NVMe clusters. If you want to use hourly backups, Atlas limits backups on NVMe clusters to once every 12 hours.
NVMe clusters use a hidden secondary node consisting of a provisioned volume with high throughput and IOPS to facilitate backup.
You can't pause an NVMe cluster.
NVMe clusters auto-scale to the next higher tier when 90% of the available storage space is consumed, and the migration requires an initial sync.
Free, Shared, and Dedicated Cluster Comparison¶
The following table highlights key differences between an
Tier cluster, an
M5 shared cluster, and an
M10+ dedicated cluster.
Free Cluster (
Shared Cluster (
Dedicated Cluster (
Storage (Data Size + Index Size)
10 - 4000 GB
MongoDB Version Support
4.0, 4.2, 4.4
Metrics and Alerts
Global Region Selection
Atlas supports deploying
Atlas supports deploying
Yes, including queryable backups
Yes, for clusters using an
BI Connector for Atlas
For a complete list of M0 free cluster, M2, and M5 limitations, see Atlas M0 (Free Cluster), M2, and M5 Limitations.
|||For replica sets, the data-bearing servers are the servers hosting the replica set nodes. For sharded clusters, the data-bearing servers are the servers hosting the shards. For sharded clusters, Atlas also deploys servers for the config servers; these are charged at a rate separate from the cluster costs.|