Billing is at the organization level while preserving visibility into
usage in each project.

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.

The Atlas Live Migration Service is a free service hosted and
operated by MongoDB to help users migrate existing MongoDB databases to
MongoDB Atlas. All incoming data transfers to an Atlas cluster
are also free.
Learn more
about migrating to Atlas.

To filter by invoice status, click the Status drop-down
and select the status to filter by:

Pending - invoices still pending payment.

Free - invoices with a total charge of $0.00.

Successful - invoices that are paid.

To filter by invoice date, set the From or To
date inputs to the required date range. Leaving From
blank sets the lower date boundry to the organization’s creation date.
Leaving To blank sets the upper date boundry to the
current date.

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.

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.

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.

Atlas measures storage speed as maximum 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-IOPSSSD. 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.

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:

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.

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 also runs 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.

Configuring LDAP User Authentication and Authorization for a
project enables the feature for all clusters in the project.
Configuring Encryption at Rest via customer KMS for a project
allows enabling/disabling the feature on per cluster basis

Atlas charges for each replica set in a cluster. For a replica set
deployment, the backup costs are the cost to backup data for the
replica set. For a sharded cluster deployment, Atlas sums the cost
to backup the data for each shard replica set and the config server
replica set.

Atlas charges for the network transfer costs of restoring a
snapshot. See Data Transfer for more information on how
Atlas charges for network data.

The backup cost for continuous backups is per GB per month
(US$2.50 / GB / month) as specified on the Atlas pricing page. The
monthly rate is annualized and then divided by 365 to arrive at a
Daily Backup Rate per GB. The first 1 GB of backup data is free.

Monthly backup costs are primarily based on the size per-gigabyte of
the data to back up. This size is roughly equivalent to the
uncompressed size of all documents and all indexes for all the
databases backed up.

To retrieve the size in gigabyte of the documents and indexes for a
given database, you can issue the
db.stats() method and sum the
dataSize and indexSize fields.

The backup cost for Cloud Provider Snapshots is the
total size of all snapshots per GB per month. The rate per
GB depends on the region of the cluster. For multi-region
clusters, the snapshot storage location depends on the
location of the replica set member targeted for snapshots.
The rate per GB therefore depends on the region of the
targeted replica set member at the time of the snapshot.

AWS Cloud Provider Snapshots
supports incremental snapshots, where a new snapshot saves
only the data that changed after your most recent snapshot.
For example, a cluster with 10GB of data and 3 snapshots
may require less than 30GB of total snapshot storage
depending on how data changed between snapshots.

If the existing snapshot storage volume becomes invalid,
Atlas creates a new snapshot storage volume in the same
region as the cluster’s current primary and takes a full-copy
snapshot. Atlas continues using that primary and its
AWS region for snapshots
and snapshot storage. This may result in a higher invoice for
the few days required to re-establish incremental snapshots.
The cost per GB for snapshot storage may also change
depending on the region of the new snapshot target.
For more information on how Atlas manages snapshot
storage, see Cloud Provider Snapshots.

When restoring a cluster using a manual download via HTTPS,
Atlas also charges per-hour that the download link remains
active. Contact MongoDB Support for more information.
From the Atlas project or cluster view, click
Support in the left-hand navigation bar.

The backup cost for cloud provider snapshots is the total
size of all snapshots per GB per month. The rate per GB
depends on the region of the cluster. For multi-region
clusters, the rate per GB depends on the cluster’s preferred
region.

Example

For a three member replica set deployed to the Azure
useast2 region (Virginia, USA) with three snapshots of
10, 20, and 30GB respectively, Atlas charges US$20.40.

(10GB*US$0.34)+(20GB*US$0.34)+(30GB*US$0.34)

Note

The US$0.34 rate per GB is specific to the
Azureuseast2 region at the
time of writing. Atlas displays the most current
cost per GB for the cluster’s selected region during
cluster configuration.
See Create a Cluster or Modify a Cluster
for more information on cluster configuration.

When restoring a cluster using a manual download via HTTPS,
Atlas also charges per-hour that the download link remains
active. Contact MongoDB Support for more information.
From the Atlas project or cluster view, click
Support in the left-hand navigation bar.

If you have questions on Cloud Provider Snapshot backup sizing and
pricing, please contact Atlas support by clicking
Support from the left-hand navigation of the Atlas UI.

Lowering snapshot frequency or lowering snapshot retention lowers the
cost per gigabyte. Increasing the snapshot frequency or the snapshot
retention increases the cost per gigabyte. To modify the snapshot
frequency or retention for a cluster, see
Snapshot Schedule.

The cost of backups is dependent on the region of the replica set
member targeted for snapshots. Modifying the
region configuration for your cluster may reduce the cost per
gigabyte for snapshot storage. You can change regions by
scaling the cluster.

MongoDB Stitch applications may incur data transfer and compute costs
for each application in a project. If you have Stitch applications in
your organization, your invoice includes these costs as a line item.
See Stitch Billing for
more information.

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

To retry the payment, click Billing, then
Usage 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.