How the charge for mongodb atlas is 72hrs per day?

[111965 (מתן מימון)]

so i got my first invoice about the most simple & cheapest plan in atlas.

i was shocked when the total amount was 21$ even when I purchased the plan at the half of the month,
and even that my application isn’t live for use (only me use for dev usage).

I opened the deatiled invoice and saw -

1. I got a lot of payment row (each day & type), 72 server hrs for a single day.
2. I’ve got charged per each day… full (more then full) == 72 hrs charged
3. Not only the “server hours” is what I’m paying for, but also for the GB(?), even though it was very small amount, I would be happy to know this type of chrage.

Please, if anyone could explain how do I have got charged so much hours even the db wans’t really work so much hours really. (cases 1&2 )

Thanks in advanced.

[Stennie_X (Stennie)]

Welcome to the MongoDB Community Forums @111965 !

Dedicated Atlas clusters (M10+) are provisioned with a minimum of 3 instances running as a replica set, which equates to 72 server hours per calendar day. Billing is based on those dedicated instances running as requested, not on the number of hours they are actually used.

If your Atlas deployment is lightly used, you have a few options to potentially save on costs:

• Pause your M10+ cluster for up to 30 days when unused. Paused clusters only include charges for storage, but do not have charges for any other services or data transfer. You can pause and resume via the Atlas API for convenience: How to Easily Pause and Resume MongoDB Atlas Clusters.

• Try MongoDB Atlas Serverless (currently in preview). Serverless pricing is based entirely on usage (read processing units, write processing units, storage, backup, and data transfer) rather than a dedicated allocation of resources. Since Serverless is a newer service, if you plan to try it out I would check your app deployment meets the Minimum Driver Versions for Serverless Instances.

Regards,
Stennie