MongoDB Atlas Pricing 2026: Free, Flex and Dedicated

MongoDB Atlas costs nothing on the M0 free cluster, $8 to $30 a month on Flex, and from $56.94 a month on a Dedicated M10 cluster, the entry point for production features such as continuous backup and private networking. Every paid tier bills by the hour with a monthly invoice, so a cluster you delete halfway through the month bills only the hours it ran.

Prices below were read on October 19, 2026 on MongoDB's pricing page (AWS tab, default storage) and in the Atlas billing docs for Flex costs and cluster configuration costs. MongoDB says prices vary slightly between AWS, Google Cloud and Azure and between regions, so treat these as the US list rates, not a quote.

Toolradar data: in the managed databases category on Toolradar, the software directory we run, MongoDB Atlas is listed as an alternative to 13 other tools, second among the 24 managed databases tracked as of October 2026. Only one of the 24 is cross-shopped more often, which is why its pricing gets compared so much. The product record is MongoDB Atlas on Toolradar.

Tier	Price	Storage	Best for
Free (M0)	$0	512 MB	Learning, demos, a course project
Flex	$0.011 an hour base, capped at $30 a month	5 GB	Development, testing and low-traffic apps
Dedicated M10	$0.08 an hour, $56.94 a month	10 GB to 128 GB	Small production apps and pre-production
Dedicated M30	$0.54 an hour	40 GB to 512 GB	The first tier with dedicated vCPUs, for production traffic
Atlas Infinite	$0.09 an hour, public preview	Up to 128 TB per HA shard	AI-scale workloads on M10 and above

How Atlas bills: hours, tiers and the meters around them

The cluster tier is the foundation of the bill, and it is metered hourly. You pick a tier, Atlas counts the hours it exists, and the invoice arrives monthly. That makes short-lived clusters cheap: a load-test cluster that lives for a day costs a day of its hourly rate, not a month.

Around the tier sit the lines that surprise people. MongoDB's own list of cost drivers names the cloud provider and region, storage beyond the default, data transfer out of the cluster, backups, and add-ons such as Search nodes, Stream Processing and support subscriptions. Inbound transfer is typically free; egress and cross-region traffic are not.

One storage rule catches teams who resize. The configuration docs say that if you raise a cluster's storage, Atlas charges for the full amount, not the increment. An M10 raised from its default storage to 50 GB bills all 50 GB, so a resize should be sized against real data, not a guess.

The hourly figures on the pricing page are rounded. Multiply M10's listed hourly rate by the 730 hours in a month and you get $58.40, while the page prints a lower monthly figure for the same tier, so monthly estimates built from the hourly column run slightly high. That is the safe direction for a budget.

The free M0 cluster: what you get and where it stops

M0 is free forever, with 512 MB of storage, 32 MB of sort memory and up to 100 operations per second. It runs on shared RAM and vCPU, and MongoDB positions it for learning and exploring rather than production.

The free cluster limits page adds the rules that matter once real users arrive. You get one free cluster per project, 500 connections, and 10 GB in plus 10 GB out of data transfer per rolling 7-day window. Past the throughput or transfer limit, Atlas throttles the network with a cooldown rather than sending a bill.

The other trap is inactivity. A free cluster with zero connections for 30 days pauses automatically, and MongoDB advises exporting data before a long quiet spell. That suits a demo; it does not suit a webhook receiver that only wakes once a quarter.

If you need several free databases across vendors for side projects, the free database hosting list ranks the options that never bill, and cloud free tiers compared sets M0 next to the other providers' allowances.

Flex: a $30 ceiling, priced by throughput

Flex trades guesswork for a cap: the base rate covers 0 to 100 operations per second, and the bill has a hard monthly ceiling. Storage is included up to the tier limit and, according to the Flex billing docs, unlimited data transfer, because Atlas does not charge Free or Flex clusters for outgoing data.

Billing follows throughput each hour, not your monthly peak. MongoDB publishes five bands, and each band's hourly rate applies only to the hours you spend in it:

Ops per second	Hourly rate	Monthly if sustained for 30 days
0 to 100 (base)	$0.0110	$8.00
100 to 200	$0.0205	$15.00
200 to 300	$0.0288	$21.00
300 to 400	$0.0356	$26.00
400 to 500	$0.0411	$30.00

MongoDB's own one-day example shows how that plays out: 5 quiet hours, 10 hours bursting past 400 ops per second and 9 hours near 150 come to $0.65 for the day. A traffic spike costs cents, not a tier upgrade.

The limits are about features, not price. The Flex limitations page caps storage at 5 GB and throughput at 500 operations per second, allows one daily snapshot with no point-in-time restore, and rules out private endpoints, network peering, sharding, database auditing and the Performance Advisor.

Leave Flex for features, not for traffic. The day you need point-in-time recovery, a private endpoint for a security review, or more room than Flex storage allows, Dedicated is the answer, whatever the throughput says.

Dedicated clusters: from M10 to M700

Dedicated starts with M10 at 2 GB of RAM and 2 vCPUs, and the price roughly doubles or more at each early step. MongoDB recommends M10 and M20 for pre-production and small, non-critical workloads because they run on shared vCPUs, and M30 and above for performance-critical traffic on dedicated vCPUs.

Tier	RAM	vCPUs	Storage range	Hourly rate	About 730 hours
M10	2 GB	2	10 GB to 128 GB	$0.08	$56.94 (printed)
M20	4 GB	2	20 GB to 256 GB	$0.20	$146
M30	8 GB	2	40 GB to 512 GB	$0.54	$394
M40	16 GB	4	80 GB to 1 TB	$1.04	$759
M50	32 GB	8	160 GB to 4 TB	$2.00	$1,460
M60	64 GB	16	320 GB to 4 TB	$3.95	$2,884
M80	128 GB	32	750 GB to 4 TB	$7.30	$5,329

The 730-hour column is our arithmetic from the hourly rates, rounded to the dollar; only the M10 monthly figure is printed by MongoDB. Above M80, the page lists M140 at $10.99 an hour, M200 at $14.59, M300 at $21.85, M400 at $22.40 and M700 at $33.26, with 4 TB as the single-cluster storage ceiling and sharding for anything larger.

The jump from M20 to M30 is the one to plan for. It is the step from shared to dedicated vCPUs, and at about $394 a month it is close to triple M20. Before paying it, check the Performance Advisor and your indexes on M20, because a missing index is cheaper to fix than a tier.

Auto-scaling is available on every Dedicated tier and can move both the cluster tier and storage with CPU and memory use. Set a ceiling: an auto-scaled cluster that climbs two tiers during a backfill keeps billing at the higher rate until it scales back.

Backups, transfer and pausing: the lines below the cluster

Cloud backup snapshots bill per GB-month, at $0.14 to $0.19 on AWS, $0.34 to $0.65 on Azure and $0.08 to $0.12 on Google Cloud, according to the configuration costs page. A 50 GB snapshot footprint on AWS therefore adds roughly $7 to $9.50 a month. Continuous backup, needed for point-in-time restore, uses a separate tiered rate that starts at $1.00 to $1.55 per GB a month for the first 5 GB on AWS and falls as volume grows.

Exporting a snapshot to S3, Azure Blob or Google Cloud Storage costs $0.125 per GB on top of the cloud provider's own transfer charge. That matters for teams that ship nightly exports to a data lake.

Pausing helps development clusters. Atlas charges only for storage while a Dedicated cluster is paused, and no compute or data transfer. An M10 used for 40 hours a week runs about 173 hours a month, about $14 of compute at the listed rate, plus the storage charge for the paused hours.

Data transfer is the line to watch on Dedicated. Egress and traffic between regions or clouds are billed at rates that depend on provider and region, and MongoDB's advice is to deploy the application in the same region as the cluster. An app hosted in a different region from its database pays cross-region transfer on its query traffic; Vercel pricing and Railway pricing cover the app side of the same bill.

What three real stacks cost on Atlas

We priced three common deployments using only the published rates, at list price on AWS, before backups, egress and support.

Stack	Clusters	Monthly cluster cost
Side project	One M0	$0
Startup app with staging	Flex at base for staging, M10 for production	$64.94
Growing SaaS	Flex dev, M10 staging, M30 production	about $459

The startup stack is the most common shape and the cheapest safe one. Staging on Flex at its base band plus production on M10 lands under $65 a month, and production keeps continuous backup and private networking available. If staging bursts all month, its cost can only rise to the Flex cap, which puts the worst case at about $87.

The growing SaaS stack is dominated by the M30 line, which is most of the $459. A team at that stage that adds continuous backup on 50 GB, plus a support subscription, should expect a three-figure increase on top. MongoDB lists its Atlas support plans by response time (8 hours on Developer down to 15 minutes on Platinum for severity 1) and sends buyers to sales for the price.

How Atlas compares with Postgres hosts

Atlas is priced like a provisioned database above Flex: you pay for the tier whether the cluster is busy or idle. Serverless Postgres hosts bill compute only while the database is awake, which favors apps that sleep. The Neon pricing breakdown shows that model, and Supabase pricing covers a fixed-plan Postgres backend with auth and storage bundled.

The choice is rarely price alone. If your data model is documents and your team writes MongoDB queries, porting to Postgres to save a tier is a rewrite, not a migration. If you are starting fresh, the Postgres hosting roundup and the Supabase vs Firebase comparison are where to weigh the alternatives, and the backend as a service guide covers the bundled platforms.

Devshot tracks database price moves like these in its daily email for developers; subscribe at devshot.co if Atlas is in your stack.

Which Atlas tier should you pay for?

Stay on M0 for tutorials, hackathons and demos that fit in the free storage limit and can tolerate a pause after a quiet month. It costs nothing and throttles instead of billing.

Use Flex for staging, internal tools and low-traffic production that can live with daily snapshots. Its monthly ceiling makes it the most predictable line on any database invoice.

Move to Dedicated M10 when you need point-in-time restore, private endpoints, auditing, or storage past the Flex limit, and to M30 when production traffic needs dedicated vCPUs. Pause or delete non-production Dedicated clusters outside working hours; the hourly billing rewards it.

How we checked these prices

We read MongoDB's pricing page, the Flex and cluster configuration billing docs, the Free and Flex limitation pages and the support plans page on October 19, 2026. Scenario totals multiply the published hourly or monthly rates and exclude backups, egress, storage resizing and support unless stated. Prices vary by cloud and region, so confirm the figure in the Atlas cluster builder or the pricing calculator before you commit a budget.

FAQ

How much does MongoDB Atlas cost in 2026?

MongoDB Atlas has three Core options. M0 is free with 512 MB of storage, Flex runs from $8 to $30 a month depending on throughput, and Dedicated starts at $56.94 a month on M10, with M30 at $0.54 an hour for dedicated vCPUs. All paid tiers bill hourly with a monthly invoice, as of October 2026 on AWS list rates.

Is MongoDB Atlas free?

Yes, the M0 cluster is free forever, with 512 MB of storage, shared RAM and CPU, and up to 100 operations per second. It allows one free cluster per project a weekly data transfer allowance, and it pauses after 30 days without connections. It suits learning and demos rather than production.

What is MongoDB Atlas Flex and how is it billed?

Flex is a shared tier with 5 GB of storage and up to 500 operations per second. It bills hourly by throughput band, from $0.011 an hour at the base band, and the monthly total has a hard cap at the top band. Outgoing data transfer is not charged on Flex. It lacks point-in-time restore, private endpoints and sharding.

When should I move from Flex to a Dedicated cluster?

Move when you need a feature Flex lacks, not when traffic grows. Point-in-time restore, private endpoints, network peering, auditing, sharding and storage above 5 GB all require Dedicated. On price, M10 costs roughly double the Flex ceiling, so the upgrade is a feature decision.

Does MongoDB Atlas charge for backups and data transfer?

Yes, on Dedicated clusters. Cloud backup snapshots cost $0.14 to $0.19 per GB-month on AWS, continuous backup uses a separate tiered rate, and snapshot exports cost $0.125 per GB. Egress and cross-region transfer are billed by provider and region. Free and Flex clusters are not charged for outgoing data.

Can I pause a MongoDB Atlas cluster to save money?

Yes. A paused Dedicated cluster is charged for storage only, with no compute or data transfer charges, so pausing development and staging clusters outside working hours cuts most of their cost. Free M0 clusters pause automatically after 30 days with zero connections, and you can resume them later.

Cite this: Devshot, "MongoDB Atlas Pricing 2026: Free, Flex and Dedicated", November 2026.

Get the next Atlas price change in your inbox: Devshot's free daily email covers the tools and bills behind developer stacks. Subscribe at devshot.co.

Some offers on this page may be paid placements or contain affiliate links.