What it is: Maintenance Waves lets Atlas customers control the order in which maintenance is applied across projects in an organization. Assign projects to a First, Second, or Last wave so that maintenance completes for projects in each earlier wave before it begins for projects in the next wave.

Who it’s for: This feature is for database administrators, platform engineers, and DevOps teams that manage Atlas deployments across development, staging, and production environments. It is particularly relevant for organizations with established maintenance processes that need to control when each environment receives an update.

Why it matters: Maintenance Waves lets teams establish a staged maintenance rollout across development, staging, and production environments rather than coordinating updates independently for each project. Teams can validate updates in lower-risk environments and progress them toward production on a more predictable schedule.