nOps vs ZopNight: Commitment Autopilot or Hands-On Control
nOps is at its best buying discounts for you. ZopNight is at its best deciding what should be running at all. Here is how to tell which problem you have.
What nOps does
We read nOps’ own site on 24 September 2026. Its headline product is autonomous rate optimization. In its own words, nOps will “automatically purchase and manage the right mix of RIs, Savings Plans, and CUDs” (nops.io). You connect AWS, Azure and GCP accounts with read-only access, and no agent is needed. Alongside that sits a cost visibility layer with reporting, allocation, forecasting, anomaly detection and unit economics, covering multicloud, Kubernetes, SaaS and AI spend.
nOps also schedules. The nOps Scheduler recommends resources to put on a schedule, and nOps “will automatically turn on/off instances via our integration with AWS EventBridge” (Cloud Optimization Essentials). The same page describes detecting and deleting idle EBS volumes. An earlier version of this page called nOps AWS-only with no scheduler. Neither is true today.
Pricing has two parts (nops.io/pricing). Cost visibility is a fixed fee based on your cloud spend. For rate optimization, “you pay only a percentage of savings realized”. There is a 14-day free trial.
Where the two actually differ
Both tools will find idle spend and switch instances off on a schedule, so the real question is which lever you want to pull. nOps is built to lower the price of the capacity you keep: it buys and rebalances commitments on your behalf. ZopNight is built to lower the quantity. It shows you what is running, schedules what does not need to be, and turns recommendations into cloud actions.
On commitments, ZopNight is deliberately more cautious than nOps. Its RI and CUD recommendations are advisory only. Each one is priced from the resource’s real on-demand and committed rates and its measured uptime. If uptime is unknown, ZopNight says “savings unknown” rather than assume the resource runs 24/7. It never makes the purchase for you. If you want purchasing done for you, that is nOps’ territory.
| Capability | ZopNight | nOps |
|---|---|---|
| Clouds connected | AWS, GCP, Azure | AWS, Azure, GCP |
| Commitment purchasing | Advisory recommendations only | Automated RI, Savings Plan and CUD management |
| Off-hours scheduling | Cron schedules with IANA timezone, per resource or group | nOps Scheduler via AWS EventBridge |
| Kubernetes namespace start/stop | EKS, GKE, AKS | Not stated on the pages we read |
| Pricing model | See zop.dev/pricing | Fixed fee for visibility; share of realized savings for rate optimization |
Choose nOps if…
- You mainly want your commitment portfolio bought and rebalanced without an engineer doing it by hand.
- You prefer paying a share of realized savings to paying a flat licence.
- Your off-hours needs are mostly EC2 instances, and EventBridge-driven start/stop covers them.
Choose ZopNight if…
- You want one schedule model across AWS, GCP and Azure. A schedule is a cron in your own timezone, attached to single resources or to resource groups, and a group starts in a set order (storage, then databases, then compute, then apps) and stops in reverse, with per-resource delays.
- You schedule more than VMs. ZopNight can start and stop RDS, Cloud SQL, EKS, GKE, AKS, ECS services, Auto Scaling groups, Databricks, and whole Kubernetes namespaces. See RDS scheduling for how it works on one resource.
- You want remediation you can gate: one-click fixes run through a wizard, and destructive operations go through an admin approval step.
- You want overrides that carry a reason and expire on their own, so a “keep this up tonight” request never becomes permanent.
The two can run side by side. A common split is to let a rate tool handle commitments on steady-state capacity while scheduling removes the hours nobody uses. Buying a commitment for hours you are about to switch off is money wasted, so decide what to schedule before you commit.
Questions we get a lot.
If yours isn't here, email us and we'll answer directly.
Does nOps support Azure and GCP?
Yes. As of 24 September 2026 the nOps homepage says you can connect AWS, Azure and GCP accounts, and it manages RIs, Savings Plans and CUDs.
Does nOps have a scheduler?
Yes. The nOps Scheduler recommends resources to schedule and turns instances on and off through AWS EventBridge. The real comparison is scope: ZopNight schedules databases, Kubernetes clusters and namespaces, and resource groups with ordered start and stop across all three clouds.
Which should I set up first?
Scheduling, if you have environments that sit idle overnight. The hours you remove change how much capacity is worth committing to. Buy commitments afterwards, on the steady-state baseline that remains.
What access does ZopNight need?
A read-only connection gives you discovery, cost data and recommendations. Starting, stopping and remediating resources needs a read and write connection, which you can switch to later without reconnecting the account.