MongoDB Atlas Pricing in 2026: What You Actually Pay

MongoDB Atlas pricing looks simple on the marketing page: a free tier, a cheap shared tier, and dedicated clusters "starting at $0.08/hour." Then your first real invoice arrives and the number is nothing like the sticker. This teardown walks the 2026 rate card, then builds three real 30-day bills so you know what you actually pay before you provision anything.

Correction, September 20, 2026. This teardown originally described three of the four meters on a dedicated cluster as pass-throughs of your own cloud bill: storage "charged per GB-month at your cloud provider's rate," storage billed only "above the included baseline," and backup and egress "charged based on cloud provider rates." None of that is what MongoDB's own documentation says. Atlas publishes its own rate card for each meter, bills customised storage in full rather than only the amount above the tier default, and prices continuous point-in-time backup on AWS at $1.00 to $1.55 per GB-month against $0.14 to $0.19 for plain snapshots. The corrected meters and the rebuilt Cohort B bill are below. Note too that MongoDB's pricing page publishes the smallest dedicated cluster as both "$0.08/hour" and "Starts at $56.94/month," which do not reconcile at 730 hours; $0.08 is a rounded display of $0.078, and the advice on this page rests on the monthly figure MongoDB publishes rather than on the rounded hourly one. Every other figure here was re-checked against MongoDB's pricing page on September 20, 2026 and is unchanged.

What does MongoDB Atlas cost in 2026?

Atlas has three price ladders. Here is the 2026 rate card, pulled straight from MongoDB's own pricing page.

Two things about that table drive almost every "why is my Atlas bill this high" question.

First, dedicated tiers (M10 and up) are priced by RAM and vCPU, not storage. You pick an instance size, and storage rides along on top. Second, the Flex tier is billed hourly ($0.011/hour at the base) but hard-capped at $30/month, so it can never surprise you. Dedicated clusters have no such cap.

The M0-to-M10 cliff nobody warns you about

Here is the gap that catches people. Atlas used to have a gentle staircase: M0 free, then M2 at $9, M5 at $25, then dedicated. MongoDB consolidated the old shared and serverless tiers into a single Flex tier, capped at $30/month and roughly 500 operations per second.

That is fine until your app sustains more than about 500 ops/sec. At that point Flex is maxed out and your only move is a dedicated M10 at roughly $58/month. So the practical ladder in 2026 looks like this:

• $0 (M0, 512 MB, a toy)
• $8 to $30 (Flex, one small production app)
• then a wall
• $58+ (M10 dedicated, 24/7 billing)

There is no $35 or $45 middle rung. The moment you outgrow Flex, your database line item roughly doubles from the $30 cap to $58, and the billing model changes underneath you. That jump, not the raw rates, is what the r/SaaS thread "Hosting MongoDB online for SaaS seems too expensive" is really about. Most of the sticker shock is people provisioning an M10 for a project that would have run all year on Flex for $8.

The real Atlas bill = compute + storage + backup + egress

The hourly instance price is only the first of four meters on a dedicated cluster:

1. Compute (the instance-hours). Firm and predictable: hours in the month times the tier rate.
2. Storage. Take the tier default and storage is already inside the hourly price. Customise it and MongoDB bills the full amount: its docs state that Atlas "charges for the full amount of storage" and "doesn't deduct the cost of the default storage capacity," and work the example of an M10 raised from 10 GB to 50 GB being billed for 50 GB, not for the extra 40.
3. Backup. Snapshot storage is billed per GB per month at MongoDB's own published rates, not your cloud provider's. Plain Cloud Backup on AWS is $0.14 to $0.19 per GB-month, against $0.34 to $0.65 on Azure and $0.08 to $0.12 on Google Cloud. Switch on Continuous Cloud Backup for point-in-time recovery and the meter changes shape: the first 5 GB are free, then AWS bills $1.00 to $1.55 per GB-month across the 5 to 100 GB band, tapering to $0.25 to $0.40 above 500 GB. Backup is not available on M0 and is where a lot of "hidden" dollars live.
4. Egress (data transfer out). Ingress is free, and neither M0 nor Flex is charged for outbound data at all. On a dedicated cluster MongoDB publishes its own band rather than forwarding your cloud bill: on AWS, same-region transfer is $0.00 to $0.01 per GB, different-region is $0.02 to $0.15, and out to the internet is $0.09 to $0.16. Cross-region or public-internet traffic is where this bites.

Not one of those three meters is a pass-through of your own cloud bill. MongoDB publishes a rate card for each, which is exactly why the calculator sticker and your invoice diverge. Plan for the sticker plus roughly 20 to 30 percent once storage, a short backup window and a little egress are layered on, and treat that as a floor rather than a ceiling. Continuous backup is the meter that scales fastest: MongoDB's own worked example prices 115 GB of snapshots and oplog at $106.25 a month, which is more than an M20's entire compute line.

Three real 2026 monthly bills

Rates are abstract. Bills are not. Here are three cohorts running the same numbers.

Cohort A: the indie side project

A solo builder with a live app doing about 50 ops/sec and 3 GB of data. This sits comfortably inside Flex's base band.

• Flex base: $8.00/month
• Storage: inside the 5 GB included
• Data transfer: not charged on Flex

30-day bill: about $8. If traffic occasionally bursts toward 150 ops/sec, the usage meter lifts it toward $15. It never exceeds $30. This is the cohort that should never touch a dedicated cluster.

Cohort B: the growing SaaS

A real production app that needs a replica set and sustained throughput above Flex's ceiling. Smallest sensible option is an M10.

• M10 compute: MongoDB publishes this as $56.94/month (the $0.08/hour on the card is a rounded display of $0.078)
• Storage: 25 GB provisioned. Because that is a customised figure, Atlas bills all 25 GB, not the 15 GB above the 10 GB default
• Backup with a 7-day PITR window: that is continuous backup, so the first 5 GB are free and the rest bills at $1.00 to $1.55 per GB-month on AWS. Even a modest 15 GB of snapshots and oplog is $10 to $15
• Egress: a few dollars for a normal API workload

30-day bill: roughly $75 to $85, versus the $58 sticker. Effective overage above the headline number: about 29 percent. Nothing here is a hidden fee; it is four meters instead of one.

Cohort C: the scaling app

A busier app that has outgrown 2 GB of RAM. The working set no longer fits, so queries hit disk and latency climbs. The fix is more RAM, which means M30.

• M30 compute: $0.54/hr times 730 hours = $394.20/month
• Storage: 80 GB provisioned, meaningful GB-month charge
• Backup with a longer retention window: tens of dollars
• Egress: real traffic, real transfer

30-day bill: roughly $450 to $500. The lesson buried in this cohort: on dedicated Atlas you scale by RAM, because the price ladder is a RAM ladder. Going from M10 to M30 is a 6.7x compute jump ($58 to $394) for 4x the RAM. If your problem is storage rather than RAM, you are on the wrong axis and overpaying.

Why dedicated clusters cost more than you expect

Flex is usage-based and idles cheaply. Metered platforms like Railway bill per second, so an idle service costs a fraction of its ceiling. A dedicated Atlas cluster does the opposite. M10 and up bill for all 730 hours in the month whether or not a single query runs. A staging M10 left on over a quiet weekend still costs the full $58/month at 3 AM with zero traffic.

You can pause a dedicated cluster for up to 30 days, but paused clusters still incur storage charges and auto-resume when the window ends. This is the single most common source of "surprise" Atlas bills: non-production clusters provisioned as dedicated and then forgotten. The same trap shows up on any always-on managed service, which is why the Supabase pricing teardown makes the same point about compute that never sleeps.

MongoDB Atlas vs the alternatives

Atlas is not the only way to run MongoDB-compatible data in 2026.

Vantage's DocumentDB-vs-Atlas breakdown walks a large-instance example at $3.95/hour, which is $2,844 for a 720-hour month. The honest read: at small scale, Atlas Flex undercuts DocumentDB (which has no free tier); at large scale the comparison depends entirely on instance choice and reserved commitments. Compatibility is not the same as being MongoDB, so test your queries before switching for price alone.

Five ways to lower your Atlas bill

1. Stay on Flex until you genuinely exceed 500 ops/sec sustained. The $8 base band covers more real apps than people assume. Do not jump to a dedicated cluster for a project Flex can carry.
2. Scale RAM, not storage. Dedicated tiers are priced by RAM and vCPU. If your working set fits in 2 GB, you stay on M10. Buying M30 to hold cold data you rarely query is the classic overpay.
3. Pause or downgrade non-production clusters. Dev and staging do not need dedicated 24/7. Run them on Flex or pause them, since M10+ bills around the clock.
4. Keep app servers in the same cloud region as the cluster. Egress is a pass-through; cross-region and public-internet traffic is where a quiet API bill turns loud.
5. Tune backup retention, and check whether you need continuous backup at all. The PITR window drives oplog size, and on AWS continuous backup bills $1.00 to $1.55 per GB-month in its first paid band against $0.14 to $0.19 for plain snapshots. That is roughly a sevenfold difference on the same data. A 7-day window costs less than a 35-day one, and most apps do not need the longer horizon.