> ## Documentation Index
> Fetch the complete documentation index at: https://help.nops.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Pause Non-Production MongoDB Atlas Clusters Outside Working Hours

> Pause non-production MongoDB Atlas clusters outside working hours and resume them on a schedule.

A dedicated MongoDB Atlas cluster bills its instance hours around the clock. A paused cluster stops those instance charges. nOps finds non-production M10 and larger clusters that run almost all day, every day including weekends, and estimates the saving from running them only 12 hours on weekdays.

| | |
| - | - |
| **Cloud** | MongoDB Atlas |
| **Category** | Database |
| **Service** | MongoDB Atlas |
| **Action** | Modify |
| **Effort** | Medium |
| **Restart needed** | Yes |
| **Can be rolled back** | Yes |
| **Analysis window** | Last 14 days |
| **Source** | nOps |

## Why it matters

Development and test clusters are rarely used at night or at weekends, but bill the same as during the working day.

## How nOps finds it

nOps reads the last 14 days of MongoDB Atlas instance charges for M10 and larger clusters. A cluster is flagged when at least 90% of its cost is non-production (from its tags, then the nOps environment, then the cluster name), it was billed on all 14 days, it averaged at least 20 hours a day, and it ran on at least 3 of the 4 weekend days. Running hours assume a 3-node replica set. The saving is the last 7 days of instance cost, scaled to a month, times the share of the week a 60-hour schedule (12 hours each weekday) would keep it off, and must be at least \$5 a month. Clusters mostly paid with Atlas credits (beyond what you pay through a cloud marketplace) are left out.

## Before you start

Atlas Project Owner or Cluster Manager access, and agreement from the cluster's users on working hours.

## How to implement

1. Confirm nobody uses the cluster overnight or at weekends, including scheduled jobs and CI.
2. Create a schedule that pauses the cluster in the evening and resumes it in the morning on weekdays, for example with an Atlas scheduled trigger or a cron job that calls the Atlas Admin API to set `paused` on the cluster.
3. Make sure applications and tests handle the cluster being unavailable outside the schedule.
4. Check the next week's Atlas invoice for lower instance charges.

## Risks and considerations

* Storage and backups are still billed while the cluster is paused.
* Atlas resumes a paused cluster automatically after 30 days, and a cluster cannot be paused within 60 minutes of resuming.
* If the cluster has more than 3 nodes, the running-hours check reads differently and the saving may vary.
* To roll back, remove the schedule and resume the cluster.

## FAQs

> [accordion] What schedule does nOps assume?
>
> 12 hours on each weekday, 60 hours a week. A different schedule saves more or less in proportion.

## Related

* [Schedule Pause for Non-Production Redshift Clusters](https://help.nops.io/inform/supported-recommendations/schedule-pause-for-non-production-redshift-clusters)
* [Supported recommendations](https://help.nops.io/inform/supported-recommendations.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.