HyperObserve
Search HyperObserve
Platform hub

MongoDB Atlas limits

Managed cluster connections, storage, throughput, collections, and project limits. Values below are scoped rather than flattened into one misleading platform-wide number.

Verified Aug 22, 2026Official docs
Quick answer:  MongoDB Atlas has multiple independent constraints. Match the exact plan, model, runtime, invocation mode, or server configuration shown in each row.

Current documented limits

ConstraintCurrent valueScopeVerified source
free cluster data storageStored BSON documents and their indexes count toward the hard cap.0.5 GBFree clusterMongoDBAug 22, 2026
concurrent connectionsAtlas connection limits apply per node or mongos depending on topology.500Free clusterMongoDBAug 22, 2026
read and write operationsAtlas throttles and applies a one-second cooldown when the limit is exceeded.100 operations per secondFree clusterMongoDBAug 22, 2026
database and collection countsThe collection count is aggregate across all databases in the cluster.100 databases and 500 collections totalFree clusterMongoDBAug 22, 2026
idle pause thresholdAtlas can automatically pause an idle free cluster.30 days with zero connectionsFree clusterMongoDBAug 22, 2026

How to apply MongoDB Atlas limits safely

The monitored baseline covers free cluster data storage, concurrent connections, read and write operations, database and collection counts, idle pause threshold. Treat these as separate constraints rather than one platform-wide capacity number: a workload can fit one row and still fail another because the plan, model, endpoint, runtime, region, invocation mode, or account scope differs.

  1. Match the production workload to the exact scope printed beside each value and confirm it in the active MongoDB Atlas console, configuration, or response headers.
  2. Measure the serialized request, token volume, duration, concurrency, storage, or connection demand at realistic percentiles, then preserve headroom for bursts and retries.
  3. Check every adjacent layer—client, SDK, gateway, proxy, queue, database, and downstream service—for a smaller effective limit before changing architecture.

Specific limit pages

These pages exist because the constraint has a distinct implementation or troubleshooting intent. Closely related keyword variations stay consolidated.

Compare alternatives

Official sources

MongoDB Atlas Free cluster limits

View MongoDB Atlas change history