Billing¶
On this page
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.
Note
The Cluster Overview box does not display data transfer costs.
See also
View or Download your Current or Past Invoices¶
Atlas invoices at the orgainzation level. Charges are typically posted the next day.
Atlas displays the current charges for the Atlas organization as Usage This Month: in the top-right corner of the organization view. Click details to view the Billing Overview of the organization. Alternatively, from the Atlas UI view of the organization, click Settings, then Billing Overview.
To view all invoices for an Atlas organization:
- In the Context dropdown, select the desired organization.
- Click Settings in the left-hand navigation bar.
- Click the Payment History tab.
The Payment History tab supports filtering 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.
To view charges and payments for a specific invoice, click the link for the invoice shown in the Invoice Date column.
To download charges and payments for a non-pending invoice, click one of the invoice format buttons in the Download As column.
To configure the payment method and billing profile for an organization, or to view the most recent and pending charges for an organization, access the organization’s Billing Overview.
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.
- Outgoing data transfer between the originating MongoDB Atlas node and:
- 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.
Advanced Security¶
Atlas supports Encryption at Rest via customer KMS and LDAP User Authentication and Authorization in Atlas projects and clusters.
Excluding MongoDB Atlas Enterprise and MongoDB Atlas Platinum customers, Atlas charges a 45% uplift to the cost of each cluster with LDAP User Authentication and Authorization and/or Encryption at Rest via customer KMS enabled.
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
Database Auditing¶
Atlas supports database auditing. See Set up Database Auditing for details.
Excluding MongoDB Atlas Enterprise and MongoDB Atlas Platinum customers, Atlas charges a 30% uplift in the hourly cost of all dedicated clusters for projects using Database Auditing.
Backup¶
The Atlas Fully Managed Backup Service supports Continuous Backups and Cloud Provider Snapshots. Each backup method has its own cost calculations and considerations.
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.
Continuous Backups¶
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 1GB 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 rate is based on your having 28 snapshots at steady state:
- The six-hour snapshots are kept for two days;
- The daily snapshots for one week,
- The weekly snapshots for one month,
- The monthly for one year.
Adding that up, you get 8 + 5 + 3 + 12 = 28 snapshots. We adjust the backup rate daily based on the following formula:
Changing the snapshot frequency or retention period affects the base rate per GB. See Snapshot Schedule and Snapshot Schedule for more information.
Example
For a three-member replica set with 30GB of data, Atlas charges US$72.50 each month (using the default backup rate).
(30GB - 1GB) × US$2.50 = US$72.50
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 (using the deafault backup rate).
((30GB - 1GB) × US$2.50) × 3) + ((5GB - 1GB) × US$2.50) = US$227.50
Cloud Provider Snapshots¶
- Azure
- AWS
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
Azure useast2 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.
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.
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 the Monthly Rate¶
- Continuous Backups
- 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.
- Cloud Provider Snapshots
- 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.
BI Connector for Atlas¶
Excluding MongoDB Atlas Enterprise and MongoDB Atlas Platinum customers, if BI Connector for Atlas is enabled for your cluster:
- The billing rate for the BI Connector for Atlas will be described in the Cluster UI as a daily uplift on the cost of the associated cluster. You can view the rate when deploying your cluster or by modifying your cluster.
- BI Connector for Atlas has a sustained-usage pricing. That is, the daily rate is charged only up to a maximum for the month.
Stitch for Atlas¶
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.
Billing Overview¶
Billing is at the organization level. All projects within an organization share the same billing settings.
To view and edit billing information, select the organization, click Settings, then click the Billing Overview tab.
Payment Method¶
Use the Edit Payment Method dialog to edit the following information for your organization:
Billing Address associated with the credit card.
Note
Atlas uses the Invoice Address defined in your Billing Profile, if any, if you select Same as Invoice Address.
Credit Card information.
The VAT Tax ID Number if required. See VAT ID Number for more information.
Atlas will not charge VAT unless your billing or invoice address is in a country that is a member of the EU and:
- There is no VAT ID Number entered.
- Your VAT ID Number is not valid.
- Your company’s billing or invoice address is in Ireland.
Coupon or Activation Code allows you to enter the activation code that you received from our sales team. For details see: Apply Prepaid Credit
Billing Profile¶
Use the Edit Billing Profile dialog to edit the following information for your organization:
- Billing Email Address for the organization. Atlas emails the organization’s invoices to this address. If the address is not set, invoices are emailed to all members of the organization.
- An optional Invoice Address that is separate from the Billing Address set in the Payment Method.
- The VAT Tax ID Number for the organization if required. See VAT ID Number for more information.
Atlas will not charge VAT unless your billing or invoice address is in a country that is a member of the EU and:
- There is no VAT ID Number entered.
- Your VAT ID Number is not valid.
- Your company’s billing or invoice address is in Ireland.
VAT ID Number¶
If your organization’s billing or invoice address is in a country that is a member of the European Union, add your VAT ID number on the Payment Method or the Billing Profile dialog.
Atlas only displays the VAT Tax ID Number field beneath the address entry if you select a country other than the United States.
Atlas will not charge VAT unless your billing or invoice address is in a country that is a member of the EU and:
- There is no VAT ID Number entered.
- Your VAT ID Number is not valid.
- Your company’s billing or invoice address is in Ireland.
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. |
Apply Prepaid Credit¶
When you buy prepaid credits from our sales team, we send you an email message containing an activation code. To apply the code to your account:
- Select your organization from the Context drop-down list at the top of the left column of the screen.
- Click Settings.
- Click the Billing Overview tab on the settings screen.
- Click Apply Credit and enter the activation code.
You can also add the activation code on the Edit Payment Method dialog box by clicking on the Edit button next to Payment Method.
Note
- If you do not add your activation code within the first 30 days of use, we will charge the credit card associated with the account. Credit card charges are non-refundable.
- If you believe you’ve lost your activation code, create a support ticket.
- If you do not have prepaid credits and would prefer to pay this way, please contact our sales team at: https://www.mongodb.com/lp/contact/sales.