Navigation

Billing

Billing is at the organization level. All projects within an organization share the same billing settings.

Atlas charges by the hour for your MongoDB clusters. Atlas tabulates costs daily and displays your current monthly costs in the upper right corner. To view line-item charges, click the details link to go to the invoice.

As you create or modify a cluster, you can compare the costs of different options before applying them. Atlas displays the costs, except for data transfer, in a Cluster Overview box.

Note

The Cluster Overview box does not display data transfer costs.

Cloud Service Provider and Region

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.

Multi-region cluster costs depend on the number of and location of additional regions selected. When creating a cluster, Atlas displays the instance size cost based on the Preferred Region of the cluster. You can see the total cost of running the cluster in the Cluster Overview.

Instance Size

Atlas provides different instance sizes. Each instance size has a default RAM capacity, storage capacity, and maximum storage speed. The cost of the instance’s per-hour charge includes these default values. Atlas uses the selected instance size when deploying all the data-bearing [1] servers in your cluster.

Depending on the choice of cloud service provider, Atlas provides customization options for instance 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-instance cost, including any selected customizations, is relative to the Preferred Region. The Cluster Overview box shows your overall charges.

Storage Capacity

Atlas charges for storage capacity differently depending on whether you use the instance default or specify a custom storage capacity. If you use the default, storage is included in the instance’s per-hour cost. If you customize, Atlas charges for the entire amount of storage, not the difference from the default size.

For example, if the instance default is 80 GB and if you increase storage to 100 GB, the change in cost is the charge for 100 GB. If you then increase storage to 120 GB, the change in cost is the charge for 20 GB.

Note

Increasing storage capacity can change the max IOPS available with each Custom Storage Speed.

Custom Storage Speed

Atlas measures storage speed as maximum Input/Output Operations Per Second (IOPS). Each Atlas instance type offers a default storage speed that is included in the instance’s per-hour cost. The choice of cloud service provider and instance size affects the available storage speed customization options, as well as the cost of selecting a custom storage speed.

AWS
For most instance types, you can increase storage speed from Standard to Fast or Fastest, which affects costs. Selecting a custom speed changes both IOPS and the type of storage used. The storage type changes from a general-purpose SSD to a provisioned-IOPS SSD. For more information on storage types, see Amazon EBS Volume Types.
GCP
All instances use SSD persistent disks with fixed maximum IOPS based on the instance 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. For more information on the GCP persistent disks, see Persistent Disks.
Azure
All instances use premium SSD disks with fixed maximum IOPS based on the 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. For more information on the Azure Premium disks, see High-performance Premium Storage and managed disks for VMs.

Data Transfer

Atlas data transfer costs depend on the cloud service provider where you deployed the cluster. Multi-region clusters may have higher data transfer costs depending on the number and location of additional regions, as well as the number of instances deployed to each region.

Atlas tabulates data transfer costs daily.

AWS

Atlas charges for data transfer between the Atlas server and another server. Data transfer charges include traffic between cluster nodes, including an outgoing transfer from the source node and an incoming transfer to the destination node within the same AWS region. Charges for data transfer increase as follows, from lowest to highest:

  • Data transfer between the originating MongoDB Atlas server and a server in the same AWS region.
  • Data transfer between the originating MongoDB Atlas server and a server in a different AWS region.
  • Data transfer between the originating MongoDB Atlas server and a server not in an AWS region.
GCP

Atlas charges for outgoing data transfers from an Atlas server to another server. Incoming data transfers to an Atlas server are free. Data transfer charges for a Atlas cluster are as follows, from lowest to highest:

  • Outgoing data transfer between the originating MongoDB Atlas node and:
    • a server that is in the same region but not in the same zone, or
    • a server where both the originating MongoDB Atlas node and the destination server are in different regions in the United States of America.
  • Outgoing data transfer between the originating MongoDB Atlas node and:
    • a server in a different continent, or
    • a server in the same continent (excluding USA) but a different region, or
    • a server or machine not in a GCP data center.
Azure
Atlas charges for outgoing data transfer from an Atlas server to another server or machine not in the same region. Incoming data transfers to a Atlas server are free. Data transfer charges for an Atlas cluster depend on the geographic location of the source server.

Number of Servers

Atlas charges the instance cost and data storage cost for each data-bearing server [1] in your cluster. For a replica set, the number of data-bearing servers equals the replication factor. For a sharded cluster, the number of data-bearing servers equals the replication factor multiplied by the number of shards.

If you enable sharding, Atlas will also run three config servers in addition to your data-bearing servers. Your selections for instance size and data storage do not affect the costs of the config servers. Config servers are charged at a separate rate. Their cost is reflected in the cost of the cluster.

Backup

For each replica set in a cluster, Atlas charges US$2.50 / GB / month to store backup data. The first 1GB of backup data is free.

Atlas discounts the cost of backup data storage if the frequency of snapshots is reduced. To modify the backup schedule for a cluster, see Modify Backup Schedule.

Note

Backup data consists of your logical data and indexes on that data.

Example

For a three-member replica set with 30GB of data, Atlas charges US$72.50 each month.

(30GB - 1GB) × US$2.50 = US$72.50

For sharded clusters, Atlas sums the cost of backup data for each shard replica set and the config server replica set.

Example

A sharded cluster with 3 shards contains 90GB of data, with each shard containing 30GB of data each. The config server replica set contains 5GB of data.

For this sharded cluster, Atlas charges US$227.50 per month.

((30GB - 1GB) × US$2.50) × 3) + ((5GB - 1GB) × US$2.50) = US$227.50

Billing Information

Billing is at the organization level. All projects within an organization share the same billing settings.

To access billing information, for the organization, click Settings, then Billing Overview.

Note

Billing Profile allows you to set an optional Invoice Address that is separate from the Billing Address set in the Payment Method.

If you set an Invoice Address, you have the option to use this address for the Billing Address by selecting same as Invoice Address in the Payment Method screen.

Retry a Failed Payment

If you receive notification of a failed payment, click Settings, then Billing Overview, and check that your Payment Method is correct.

To retry the payment, click Settings, then Payment History. On the line for the failed payment, click Retry.

[1](1, 2) 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 instance costs.