Azure Auto-Shutdown Alternative: ZopNight

Azure Auto-Shutdown is a built-in feature that automatically shuts down a single VM at a scheduled time. It is configured per-VM in the Azure portal and only supports shutdown, there is no built-in auto-start. Teams managing dozens of VMs across multiple subscriptions need something more scalable.

It is a reasonable starting point, and plenty of teams begin there. The trouble is that it was designed for a narrower world than most teams actually live in, and the seams show as soon as you have more than one cloud or more than a handful of resource types to coordinate.

Where Azure Auto-Shutdown runs out of room

The limits are structural, not cosmetic:

• Shutdown only, no scheduled auto-start.
• Configured per-VM with no bulk management.
• Azure VMs only, no databases, containers, or other resources.
• No dependency ordering between resources.
• No cross-subscription or multi-cloud view.

Each one is survivable on its own; together they mean the tool stops scaling with you right around the point your environment gets interesting: multiple accounts, mixed clouds, resources that depend on each other.

What ZopNight does differently

ZopNight was built for that messier reality:

• Scheduled start and stop, not just shutdown.
• Bulk scheduling across all subscriptions and clouds.
• Covers VMs, databases, AKS clusters, and more.
• Dependency-aware sequencing across resource types.
• Unified dashboard with savings tracking.

You get a visual dashboard instead of CloudFormation, dependency-aware ordering instead of independent start/stop, and coverage that spans clouds and resource types rather than a fixed pair. ZopNight ships 490 built-in audit rules across AWS (216), GCP (127), and Azure (147), and migration is low-stakes: connect read-only and run both in parallel until you are confident. See it on AWS EC2, compared head to head with CloudHealth, and the discipline behind it in FinOps.

How ZopNight schedules non-production resources

The loop that does this is deliberately mechanical, and it starts read-only. You connect your cloud provider with a read-only role, and ZopNight discovers every non-production resources across your regions and accounts. It records a per-action permission verdict for each one, so you can see where it can list a resource but not yet stop it, and you review that inventory, filter it by status or type, and search for the specific resources you care about before anything is scheduled.

Scheduling itself is a cron you write once in plain terms, stop at 7 PM, start at 8 AM on weekdays, pinned to your timezone so the jobs fire at local business hours rather than UTC. A weekly 24-hour grid shows the schedule visually so you catch gaps and overlaps before you save, and an estimate of active versus inactive hours appears before you commit. Resources attach individually or bundle into groups like “dev-cluster” or “staging-db” so a whole environment follows one cadence.

Actions run in dependency order, so a database comes up before the app server that depends on it. When something needs to stay up, an override forces a non-production resources ON or OFF for a defined window, carries a reason so teammates understand why it exists, and expires automatically so nothing is left running by accident. If a start or stop fails, ZopNight retries up to three times and falls back to a dead-letter queue rather than silently dropping the action, and every state change lands in an audit trail that records whether a schedule, an override, or a specific user triggered it.

Getting started

Getting started is intentionally low-stakes:

• Connect your cloud provider with a read-only role. Nothing is scheduled or changed at this stage.
• Let ZopNight discover your non-production resources and review exactly what it found, filtered by account, region, and status.
• Create a schedule in your timezone and attach the non-production resources or groups you want it to cover.
• Watch the first cycle run, with Slack, Teams, or Google Chat notifications on every start, stop, and failure, then layer in idle cleanup and guided rightsizing.

Production stays excluded by default throughout, and because discovery and recommendations are read-only, you can prove the value before you enable a single action.