Billing Alerts and Budget Controls
Parent: Atlas Billing Mechanics and Cost Visibility · Published reference · snapshot 2026-10-19 · skill mongodb-operations-expert/references/atlas-billing-mechanics-and-cost-visibility.md · viability 4.05 / 5 (research)
↓ Facts as markdownall context files
Atlas billing alerts are notification-only: they are created on the Organization Alerts page (or the Project Alerts page for project-level conditions) by choosing Target = Billing, with conditions such as credit card about to expire, amount billed yesterday, current bill for a project or the organization, and daily, weekly or monthly gross-spend or billing change; thresholds are USD amounts or percentages, and the sources document no setting that stops or pauses spend at a billing threshold. The one built-in cost ceiling they describe is the Flex cluster tier, priced at $8 to $30 per month and capped at $30 per month. This pack draws on 5 source pages across 2 host labels and covers definitions, mechanism, parameters, how-to, examples, measures, problems and comparisons.
These notes link each claim to its source. Some citations identify archived research reports that are no longer hosted on this site. A published reference means the content is available; it does not certify independent review or accuracy.Read the editorial policy and follow the sources before relying on a claim.
Definitions
- Billing alerts are created from the Organization Alerts page by choosing Target = Billing. Conditions offered: Credit card is about to expire; Amount billed yesterday is above; Current bill for any single project is above; Current bill for the organization is above; Organization gross spend daily, weekly and monthly change is above. [source]
- You can use billing alerts to help manage your billing quotas. Billing alerts notify a designated person when a bill has exceeded a USD limit, or when a credit card is about to expire. [source]
- The following alert conditions apply to Atlas billing. You can configure billing alerts from the Atlas UI at the organization level or the project level. [source]
How it works
- Dollar-threshold conditions take a USD amount. The 'current bill' conditions (single project, organization) are organization-only, count the monthly total, and reset when the current pending invoice closes. 'Amount billed yesterday' ignores credits applied for that day and applies to both organizations and projects. [source]
- Gross-spend change alerts fire on a percentage increase versus the prior period (previous day, previous 7 days, previous 30 days). The organization variants are configured on the Organization Alerts page; the project variants (daily and weekly billing change) on the Project Alerts page. [source]
- Raised if the organization or project's last daily amount billed exceeds your configured threshold. Atlas does not account for any credits applied for the previous day when calculating the billed amount. [source]
- Raised if the credit card on file is about to expire. The alert is triggered at the beginning of the month that the card expires. Atlas enables this alert when a credit card is added for the first time. [source]
- Raised if the organization's daily gross spend has increased by more than your configured threshold percentage compared to the previous day. [source]
- Raised if the organization's weekly gross spend has increased by more than your configured threshold percentage compared to the previous 7 days. [source]
- Raised if the organization's monthly gross spend has increased by more than your configured threshold percentage compared to the previous 30 days. [source]
- Raised if the project's daily billing has increased by more than your configured threshold percentage. [source]
- Raised if the project's weekly billing has increased by more than your configured threshold percentage. [source]
- Raised if the project's monthly billing has increased by more than your configured threshold percentage. [source]
- Raised if the monthly total for any project within the organization exceeds your configured threshold for all projects. When the current pending invoice closes, this alert resets. [source]
- Raised if the monthly total for the organization exceeds your configured threshold. When the current pending invoice closes, this alert resets. [source]
- Flex clusters scale with your usage. If you use additional operations/sec, MongoDB charges you based on the following pricing tiers. [source]
Parameters and configuration
- Managing all organization alerts needs the Organization Owner role; Organization Billing Admin has limited authorization to manage billing alerts. Project alerts need Project Owner or Project Alerts Manager. [source]
- Billing alert recipients: by default Organization Owners and Billing Admins. If a Billing Email Address is set and 'Only send invoice emails to the Billing Email Address' is unchecked, alerts go to that address plus Owners and Billing Admins; if checked, to the billing address only. [source]
- Billing alerts can be delivered through Atlas Organization roles, Atlas User, Email, Mobile (SMS), Slack, PagerDuty, Datadog, VictorOps, Opsgenie and Microsoft Teams. The 'send if condition lasts at least' and 'resend after' options are not available for billing alerts, which are event-based. [source]
- If you leave the Billing Email Address blank, Atlas sends billing alerts to the Organization Owners and Billing Admins. [source]
- If you specify a billing email address and uncheck Only send invoice emails to the Billing Email Address, Atlas sends billing alerts to the billing email address, Organization Owners, and Billing Admins. [source]
- This alert condition applies to organizations only. Configure it from the Organization Alerts page. [source]
- This alert condition applies to projects only. Configure it from the Project Alerts page. [source]
- The [`Organization Billing Admin`](https://www.mongodb.com/docs/atlas/reference/user-roles.md#mongodb-authrole-Organization-Billing-Admin) role grants a limited authorization to manage billing alerts. [source]
- The send if condition lasts at least and resend after options are available only for [Host alerts](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#std-label-host-alerts). These options are not available for event-based alerts such as Cloud Backup alerts, Auto-scaling alerts, billing alerts, or other non-host alert types. [source]
- By default, Atlas sends billing alerts to the Organization Owners and Billing Admins. [source]
- If you specify a billing email address and check the box for Only send invoice emails to the Billing Email Address, Atlas send billing alerts to the billing email address only. [source]
How-to and procedures
- To configure billing alerts, click Organization Alerts in the Organization view. Set up consumption alerts to track how much a project or team is spending. You’ll be notified via email whenever your specific trigger is set off. [source]
- 1. In Atlas, go to the Organization Alerts page. [source]
- 1. In Atlas, go to the Project Alerts page. [source]
- To estimate your monthly Flex cluster cost, find your cluster's current operations per second (ops/sec) usage. Then, compare that value against the tiers in the preceding table. [source]
- Type the email address to which Atlas should send billing alerts. [source]
- Compare the ops/sec value from the Opcounters chart against the tiers in the Usage Cost Summary table to estimate your marginal and total monthly cost. Your usage can vary throughout the month, so you might move between tiers as your workload changes, as the following examples show. [source]
Examples and snippets
- Your workload runs less than 100 ops/sec for 20 days, and then bursts up to 250 ops/second for 5 days. Then, for another 3 days, the workload bursts to 500 ops/second. [source]
- | Usage | Cost | | --- | --- | | Your workload runs less than 100 ops/sec for 20 days. | $0.011/hour * 24 hours * 20 days = $5.28 | | The workload bursts up to 250 ops/second for 5 days. | $0.0288/hour * 24 hours * 5 days = $3.46 | | The workload bursts to 500 ops/second for another 3 days. | $0.0411/hour * 24 hours * 3 days = $2.96 | | **Total Usage Charge** | **$5.28 + $3.46 + $2.96 = $11.70** | [source]
- Your workload runs less than 100 ops/sec for 5 hours. It bursts up to 410 ops/second for 10 hours, followed by 9 hours at 150 ops/second. After these 24 hours, you delete the cluster. [source]
- | Usage | Cost | | --- | --- | | Your workload runs less than 100 ops/sec for 5 hours. | $0.011 hourly base cost * 5 hours = $0.055 | | The workload bursts up to 410 ops/second for 10 hours. | $0.0411/hour * 10 hours = $0.41 | | The workload drops to 150 ops/second for another 9 hours. | $0.0205/hour * 9 hours = $0.18 | | You delete the cluster. | (no charge) | | **Total Usage Charge** | **$0.055 + $0.41 + $0.18 = $0.65** | [source]
- Your workload runs less than 100 ops/sec for 25 days, and then bursts up to 200 ops/second for 5 days. [source]
- | Usage | Cost | | --- | --- | | Your workload runs less than 100 ops/sec for 25 days. | $0.011/hour * 24 hours * 25 days = $6.60 | | The workload bursts up to 200 ops/second for 5 days. | $0.0205/hour * 24 hours * 5 days = $2.46 | | **Total Usage Charge** | **$6.60 + $2.46 = $9.06** | [source]
Measurements and reference values
- Atlas Flex clusters are the one built-in cost ceiling: priced at $8 to $30 per 30 days and capped at $30 per month, billed hourly, from 5 GB storage and 100 ops/sec base up to 500 ops/sec. [source]
- All amounts billed are in USD (United States Dollars). [source]
- As a user of an Atlas Flex cluster, you pay between $8 and $30 for 30 days of usage. As for all Atlas clusters, the Flex cluster tier follows a pay-as-you-go model billed hourly. [source]
- Flex clusters are capped at $30 per month. You pay a monthly base price, which includes: [source]
- | Tier (ops/second) | Marginal Monthly Cost | Effective Discount | Total Monthly Cost | Total Hourly Cost | | --- | --- | --- | --- | --- | | 0 - 100 (Base) | $8.00 | 0% | $8.00 | $0.0110 | | 100 - 200 | $7.00 | 12.5% | $15.00 | $0.0205 | | 200 - 300 | $6.00 | 25% | $21.00 | $0.0288 | | 300 - 400 | $5.00 | 37.5% | $26.00 | $0.0356 | | 400 - 500 | $4.00 | 50% | $30.00 | $0.0411 | [source]
Problems, failure modes and limitations
- Atlas billing alerts only notify. A MongoDB community moderator stated in April 2023 that no feature stops services when a billing threshold is reached and suggested a feature request; the current docs describe alert conditions only and list no spend-limit setting. [source]
- The billing docs frame alerts as 'Billing Quota Management': they notify a designated person when a bill exceeds a USD limit or a credit card is about to expire. [source]
- There currently isn’t a feature where services are stopped upon hitting a certain billing threshold. In saying so, you can submit a feature request in our Feedback engine. [source]
- Atlas triggers a sub-second cooldown period on each connection before resuming that connection's operations. If the operation queue exceeds the operations per second limit, operations might wait in the queue for more than a second. [source]
- I would like MongoDB to consider an optional cost cap (limit) setting that will prevent resources from getting used if the cap for the month is reached. The application would receive an error when the cap is reached. This would prevent a runaway application from running up huge charges. [source]
- At the end of the paying organization's billing period, simultaneous charges for daily subscription uplift and an unmet minimum could trigger daily maximum billing alerts. [source]
Comparisons and alternatives
- | Tier | Cost | Best For | | --- | --- | --- | | Free cluster (`M0`) | No cost | Learning MongoDB, prototyping, and other workloads that fit within the [Atlas Free Cluster Limits.](https://www.mongodb.com/docs/atlas/reference/free-shared-limitations.md#std-label-atlas-free-tier) | | Flex cluster | $8 to $30 per month, based on usage | Development, testing, and low-traffic production workloads that need modern database features such as MongoDB Search, MongoDB Vector Search, and Atlas Stream Processing, without managing dedicated infrastructure. | | Dedicated cluster (`M10+`) | Starts at $60 per [source]
- Suppose Atlas migrated your `M2` or `M5` cluster to a Flex cluster. Before the migration, this cluster billed at a flat monthly rate. Now, your cost depends on your workload's ops/sec usage instead of a fixed price. [source]
- The pricing tiers in the Usage Cost Summary table apply only up to 500 operations/second. Above that point, Flex clusters enforce a separate hard limit rather than a higher pricing tier. [source]
Related concepts
- Flex cluster cost cap — is a instance of Billing Alerts and Budget Controls
- gross spend change — is a part of Billing Alerts and Budget Controls
- Organization Alerts page — is a part of Billing Alerts and Budget Controls
- Flex clusters — is a related of Billing Alerts and Budget Controls
- Amount billed yesterday — is a part of Billing Alerts and Budget Controls
- alert roles — is a part of Billing Alerts and Budget Controls
- alert recipients — is a part of Billing Alerts and Budget Controls
- pending invoice reset — is a part of Billing Alerts and Budget Controls
- event-based alert — is a part of Billing Alerts and Budget Controls
- notify only — is a problem of Billing Alerts and Budget Controls
- unexpected charge — is a problem of Billing Alerts and Budget Controls
Children
- Admin API alert configurations for billing events
- Flex cluster spend ceiling
- Project-level billing change alerts (frontier)
Frontier under this node: Project-level billing change alerts