Nothing runs
at 3am unless
you said so.
Non-production runs 168 hours a week and gets used for about 50. Attach a cron schedule to a resource or a group and ZopNight stops it and starts it on time, across AWS, GCP, Azure, Snowflake, Databricks and Kubernetes.
One schedule object. Start and stop together.
Not two objects you have to remember to keep in sync.
Write it
Cron expressions in a real IANA timezone, so daylight saving is the library's problem and not yours. Multiple cron strings live in one schedule, which means start and stop cannot drift apart.
Attach it
To a single resource, or to a group. Sequenced execution runs group members in order with delays, for the cases where an app server coming up before its database is a bad morning.
It fires
The scheduler re-evaluates every schedule every second and computes the action at fire time, so an edit you made a minute ago is the one that runs. It writes a self-contained intent, and the executor is the only service that ever touches your cloud.
Kubernetes properly
A namespace stop scales Deployments and StatefulSets to zero and suspends CronJobs, saving the replica counts, the HPA and the PDB. Start puts all of it back. System namespaces are refused at the executor, not just greyed out in the UI.
Across every platform you run.
Per-provider behaviour is handled, not flattened into a lowest common denominator.
- Providers
- AWS, GCP and Azure, plus Snowflake, Databricks on all three clouds, and Kubernetes on EKS, GKE, AKS and OpenShift.
- Provider quirks
- Azure deallocates rather than stopping, because a stopped Azure VM still bills for compute. EKS node pools scale. Each provider's real semantics are implemented rather than assumed identical.
- Savings maths
- Savings are 24/7 cost minus actual cost, computed from exact on-seconds in state history. Every state transition is recorded with a timestamp, so the figure is reconstructable rather than modelled.
- Bulk actions
- Start or stop every resource in a group at once, through a worker pool with coordinated delays and sequencing. Manual changes outside the schedule are recorded the same way scheduled ones are.
Stop paying for nights and weekends.
Connect an account, group your non-production resources, attach one schedule. The savings figure comes from your own state history.