On this page
Serverless instances don't currently support the Atlas features listed below. If you require these capabilities, please use a dedicated cluster.
MongoDB plans to add support for more configurations and actions on serverless instances over time. Footnotes indicate that MongoDB plans to support the feature for serverless instances in the future.
Currently, serverless instances don't support the following configurations:
Serverless instances do support X.509 certificates and IAM for authentication.
Currently, serverless instances don't support the following actions:
Convert Atlas serverless instances into clusters. 
Convert Atlas dedicated clusters into Atlas serverless instances
Live migrate into Atlas serverless instances.
Store more than 1 TB of data.
This value includes the number of bytes of all uncompressed BSON documents stored in all collections, plus the bytes stored in their associated indexes.
Perform automated restores from backup snapshots.
Use Atlas Search.
Use Online Archive.
Use Atlas Triggers.
Use predefined replica set tags.
Track database access.
Download database logs.
Use wire compression between clients and Atlas serverless instances.
Use BI Connector.
Additionally, serverless instances have the following operational limitations and considerations:
Aggregation fields on serverless instances that represent database and collection names (such as $merge values) can't be expressions.
Aggregation pipelines for serverless instances can have a maximum of 50 stages.
The $sort stage has a limit of 32 megabytes of RAM.
Serverless instances support the following authentication methods only:
Build Index with Rolling Build
Serverless instances don't support building indexes with a rolling build.
Real-Time Performance Panel
Serverless instances don't provide access to the Real-Time Performance Panel.
Serverless instances don't routinely cap operation throughput. Atlas may throttle operations for your serverless instance temporarily while the system scales.
Serverless instances can support up to 500 simultaneous connections.
Some database commands have limitations for serverless instances. To learn more, see Unsupported Commands in Serverless Instances.
You cannot create a capped collection or convert an existing collection to a capped collection.
Namespaces and Database Names
Atlas limits serverless instance namespaces to 95 characters and database names to 38 characters.
Database and Collections
Serverless instances have a maximum of 50 databases and 500 collections total.
Changes to custom roles may take up to 30 seconds to deploy in serverless instances.
Access to Collections in
Serverless instances don't allow:
Atlas issues an error similar to the following if you attempt to read or write to collections in these databases:
Serverless instances don't support change streams.
Serverless instances don't support this feature even though it's a part of the Stable API v1.
Serverless instances don't support collation on collections, indexes, or queries.
BSON Nested Object Depth
Serverless instances can't store documents with more than 50 nested levels.
Serverless instances support multi-document transactions that are up to 700 MB in size. Atlas aborts any serverless instance transactions that exceed 700 MB.
Serverless instances don't support a numeric write
concern level greater than
To connect to your serverless instance using a driver, you must use at least one of the following versions:
To connect to serverless instances using
mongosh, you must use
version 1.0.0 or later.
You can't connect to serverless instances using the legacy
To connect to serverless instances using MongoDB Compass, you must use version 1.28 or later.