Billing

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

Atlas pricing page

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 desired organization in the Context menu, then click Billing.

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 Credit Purchased from MongoDB Sales.

Billing Profile

Use the Edit Billing Profile dialog to edit the following information for your organization:

• Billing Email Address for the organization. Atlas sends 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 a notification that a payment failed, verify your Payment Method is correct:

1. Select the desired organization in the Context menu.
2. From the left-hand navigation pane, click Billing.
3. Verify that your Payment Method is correct.

To retry the payment:

1. From the Billing page, click the Usage History tab.
2. Locate the row with the failed payment and click Retry.

Customers in the European Economic Area (EEA) may experience payment failures due to Strong Customer Authentication (SCA), a European regulatory requirement. To learn how to authenticate a credit card and comply with SCA, see Strong Customer Authentication (SCA).

[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 cluster costs.

Apply Credit Purchased from MongoDB Sales

When you buy credit from MongoDB Sales, MongoDB sends you an email containing an activation code. You can apply this credit to your Atlas invoice balance. To apply the code to your account:

1. Select your organization from the Context drop-down list at the top of the left column of the screen.
2. Click Billing.
3. Click Apply Credit and enter the activation code.

To add the activation code on the Edit Payment Method dialog box, click Edit next to Payment Method.

Note

• If you do not add your credit activation code within the first 30 days of use, we charge the credit card associated with the account. Credit card charges are non-refundable.
• If you lost your activation code, create a support ticket in Atlas. To start a support ticket, click Support in the left-hand navigation.
• If you would prefer to pre-pay for your Atlas account using credit instead of receiving and paying invoices, please contact the sales team.

Alternative Payment Methods

For alternative payment methods, please contact the sales team for assistance.

Live Migrate Your Data to Atlas

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.

View or Download Your Invoices

Atlas invoices at the organization level. Charges are typically posted the next day.

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.

View or Download Your Current Invoice

Atlas displays the current charges for your Atlas organization as Usage This Month: in the top-right corner of the organization view. Click details to view the current invoice for your organization.

Alternatively:

1. In the Context dropdown, select the desired organization.
2. Click Billing in the left-hand navigation bar.
3. From the Billing Overview view, click View Invoice.

To download charges and payments for your current invoice, click one of the invoice format buttons on the right side of the invoice view. You can download the invoice in PDF, TXT, and CSV formats.

View or Download Past Invoices

To view all invoices for your Atlas organization:

1. In the Context dropdown, select the desired organization.
2. Click Billing in the left-hand navigation bar.
3. Click the Usage History tab.

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 an invoice, click one of the invoice format buttons in the Download As column. You can download invoices in PDF, TXT, and CSV formats.

Filter Past Invoices

The Usage History tab supports filtering by invoice status and date.

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.

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

Cluster Tier

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

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.

Storage Capacity

Atlas charges for storage capacity differently depending on whether you use the cluster default or specify a custom storage capacity. If you use the default, storage is included in the cluster’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 cluster 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 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, as well as the cost of selecting a custom storage speed.

AWS

For most cluster 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 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. For more information on the GCP persistent disks, see Persistent Disks.

Azure

All clusters 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 clusters deployed to each region.

Atlas tabulates data transfer costs daily.

Note

Atlas does not charge for data transfer on M0 Free Tier and M2/M5 shared clusters.

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.

How to Reduce Data Transfer Costs

The vast majority of Atlas customers spend less than 10% of their budget on data transfer. If you are spending significantly more, some of these optimizations may reduce your data transfer costs:

• Check all applications and processes that access your data for inefficiencies. Ensure that queries do not:

  • Re-read data that already exists on the client.
  • Re-write existing data to your cluster.

• Ensure that queries originate from the same cloud region and provider as your Atlas cluster whenever possible.

  When cross-region queries are necessary:

  • Ensure read queries use the preference “nearest.”
  • Source write queries from your Highest Priority Region whenever possible. For more information on region priorities, see Electable Nodes for High Availability.

• Use the Aggregation Framework to preprocess your data before you transfer it. For example, you can project document fields using the $project aggregation stage to reduce the size of a document before you transfer it.

• Ensure that your client driver is using wire protocol compression to communicate with MongoDB (Atlas will always use compression for intra-cluster communication). For more information on configuring your driver, refer to your Driver’s Documentation.

Note

Queries from non-cloud environments into Atlas, across cloud providers, or between continents on the same cloud provider incur the greatest data transfer costs.

Number of Servers

Atlas charges the cluster 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 cluster tier 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 Backup 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 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.

copy

db.stats(1024*1024*1024).dataSize + db.stats(1024*1024*1024).indexSize

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:

copy

backupRatePerMonth = $1.25 + snapshotAtSteadyState/28 * $1.25

Changing the snapshot frequency or retention period affects the base rate per GB. See Snapshot Schedule for more information.

Examples

• 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

• 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 default backup rate).

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

Cloud Provider Snapshots

• AWS
• Azure

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 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 Tutorial: Create a New 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 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 is 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.

Support Plan

If you have an upgraded support plan, the total support cost for the month is listed in the Summary section of your invoice. Support cost line items are listed in the Details section.

Atlas Data Lake (Beta)

Atlas Data Lake incurs costs for the amount of data scanned and returned by the service.

Total Data Scanned

Atlas charges for the total number of bytes that Data Lake scans from your AWS S3 buckets, rounded up to the nearest megabyte. Atlas charges $5.00 per TB of scanned data, with a minimum of 10 MB or $0.00005 per query.

You can use partitioning strategies and compression in AWS S3 to reduce the amount of data scanned.

Total Data Returned

Atlas charges for the total number of bytes returned by Data Lake. This total is the sum of the following data transfers:

• The number of bytes transferred between Data Lake service nodes
• The number of bytes transferred from Data Lake to the client

Returned data is billed as outlined in the Data Transfer Fees section of the Atlas pricing page. The cost of data transfer depends on the Cloud Service Provider charges for same-region, region-to-region, or region-to-internet data transfer.

Strong Customer Authentication (SCA) Changes

SCA is a new European regulatory requirement to reduce fraud and make online payments more secure. All payment service providers are required to build additional authentication into their checkout flow once SCA goes into effect. Customers in European Economic Area (EEA) may be required to authenticate their credit cards depending on the card’s issuer, starting September 14, 2019. If your credit card issuer requires authentication, review the following Authentication Process to continue paying for MongoDB Atlas seamlessly with a credit card.

Marketing emails will be sent out to affected customers announcing the policy change and the steps necessary to comply with SCA.

Authentication Process

The following sections cover different ways to authenticate your credit card to comply with Strong Customer Authentication.

Build a Paid Cluster as a New User

New Atlas users who do not have a payment method saved can authenticate a new credit card when paying for a cluster on the Create a Cluster page. To learn more, see Create a New Cluster.

Edit Payment Method

Existing users can edit their Payment Method to authenticate a new credit card or reauthenticate an existing credit card to comply with SCA:

1. Select the desired organization in the Context menu.
2. From the left-hand navigation pane, click Billing.
3. Locate the Payment Method section on the right-hand side, then click the Edit.
4. Update the Billing Address associated with the credit card and enter the Credit Card information.

Once you update your credit card information and authenticate, you will be automatically charged for all existing failed payments.

Failed Payment Email

Atlas sends an email after a payment failure with a link to your invoices. Existing users can authenticate a credit card when retrying a failed payment. To retry the failed payment from the failed payment email:

1. Follow the link in the failed payment email.
2. Click the Invoice Date of the failed invoice.
3. Under the Payments section, click Retry next to the failed payment.

Retry Failed Payment

Existing users can authenticate a credit card when retrying a failed payment. To retry the failed payment from within Atlas:

1. Select the desired organization in the Context menu.
2. From the left-hand navigation pane, click Billing.
3. Click the Usage History tab.
4. Click the Invoice Date of the failed invoice.
5. Under the Payments section, click Retry next to the failed payment.

Contact Support

Contact support for further assistance.

←   Highlighting FAQ  →

© MongoDB, Inc 2008-present. MongoDB, Mongo, and the leaf logo are registered trademarks of MongoDB, Inc.