zopnight icon

zopnight

zopnight schedules cloud resources to power down when they are not being used and right-sizes what remains, helping teams reduce non-production cloud spend across AWS, GCP, Azure, and Kubernetes. It is aimed at engineering and FinOps teams that want continuous cost control with read-only discovery and guided remediation.

zopnight

Overview

zopnight is a cloud cost and governance product that finds wasted spend, schedules resources to stop when they are idle, and right-sizes workloads based on actual usage. It works across AWS, GCP, Azure, and Kubernetes, with findings reconciled against the live bill before they reach the dashboard.

The product is built for engineering and FinOps teams that need continuous cost control rather than one-off cleanup. Its core workflow is detect, decide, and act: surface recommendations, apply safe remediations where appropriate, and keep cloud waste from reappearing through continuous monitoring and policy-driven automation.

Features

Continuous recommendations

Scans across AWS, GCP, and Azure to surface idle resources, rightsizing opportunities, schedules, orphaned resources, compliance issues, discount opportunities, security issues, and reliability risks. Each finding includes the metric, threshold, recommended action, and dollar impact.

Smart scheduling

Powers down non-production resources on cron-based schedules with dependency awareness and timezone handling. The product supports more than 30 resource types, including VMs, Kubernetes, SQL, and Databricks, and can wake storage before compute.

Rightsizing and autoscaling

Uses production demand data to recommend or apply right-sizing changes for workloads such as ASGs, scale sets, and AKS pools. The product supports monitor, recommend, and autopilot modes.

Inventory, showback, and ownership

Provides a cross-cloud inventory, team and tag-based cost attribution, budgets, and creator-based ownership signals derived from cloud audit logs. Shared resources can be split across owning teams and spending is reconciled against actual billing data.

Policy-driven tagging and remediation

Predicts environment and stop-eligibility for untagged resources, lets users accept or reject derived tags, and supports one-click remediation with an audit trail. Customer databases are excluded from automatic actions.

AI-native access and workflow integrations

Includes an MCP server with read-only tools for resources, schedules, costs, recommendations, teams, budgets, and audit logs. The product also supports Slack, PagerDuty, API access, webhooks, and Jira ticket creation from recommendations.

Use Cases

  • Reducing non-production cloud spend

    Teams can identify development and test resources that run outside working hours and schedule them to stop automatically, instead of relying on manual shutdowns or dashboard checks.

  • Cleaning up idle and orphaned resources

    Engineers and FinOps practitioners can find detached disks, stale snapshots, unused IPs, and other leftover assets, then review or remediate them from the same workspace.

  • Managing production rightsizing

    Platform teams can compare actual usage with provisioned capacity and move eligible production workloads into monitor, recommend, or autopilot modes for right-sizing and autoscaling.

  • Running attribution and budget workflows

    Finance and engineering leaders can assign spend to teams or tags, track budgets by team, resource group, or resource, and monitor threshold-based alerts through the same system.

  • Supporting governed operations

    Regulated or larger teams can use read-only discovery, role-based access, approval workflows, and audit logs to keep remediation controlled while still reducing waste.

Pros and Cons

Pros

  • Covers discovery, scheduling, rightsizing, attribution, and remediation in one product.
  • Reconciles findings against actual billing data before surfacing them.
  • Supports read-only start, least-privilege access, and controlled write actions.
  • Works across AWS, GCP, and Azure, with Kubernetes and several adjacent cloud services.
  • Offers pricing and deployment options that include a free starter tier, a paid Pro tier, and an Enterprise option with self-hosting and SSO.

Cons

  • The pricing page and changelog show some features are still evolving, so coverage may vary by service and release.
  • One-click remediation still requires explicit enablement for write permissions and may use approval workflows for sensitive actions.
  • The source only confirms some integrations and support details; broader ecosystem depth is not fully documented here.

FAQ

How does setup work?

Connect cloud accounts through read-only cloud APIs and grant the required IAM roles once; the pricing page says discovery starts in minutes and most accounts see initial findings within 2-3 minutes.

Does zopnight require agents or code changes?

No. The pricing page states there are no agents, no sidecars, and no Terraform changes required for discovery.

What happens when I remediate something?

Depending on the action, zopnight can call the cloud provider API directly, log the action in the audit trail, and support approval workflows so changes do not run without human sign-off.

Which clouds are supported?

The product pages explicitly support AWS, GCP, and Azure, plus Kubernetes-related workloads and several cloud services such as Databricks.

What does pricing depend on?

Pricing is based on the number of cloud resources managed rather than seats or savings found. The published tiers include Starter, Pro, and Enterprise.

Quick Facts

Category
Cloud cost management
Primary users
Engineering teams, FinOps teams, and cloud platform owners
Platforms
AWS, GCP, Azure, Kubernetes
Source domain
zop.dev
Pricing model
Per cloud account and per resource-managed structure, with Starter, Pro, and Enterprise tiers
Notable workflow
Detect waste, reconcile it to live billing, then schedule or remediate from the same workspace

Alternativas a zopnight