Cloud governance without visibility is just guesswork. You cannot enforce what you cannot see, audit what you cannot trace, or control costs you cannot attribute. ZopNight v2.0 is built around one idea: governance should be complete, auditable, and programmable at every layer.
This release ships seven new features, seven revamped core systems, measurable performance gains, and the foundation for two major capabilities arriving next. Every changelog item in this post comes from production. This is not a roadmap preview. This is what is live today.
What’s New
1. Atlas: Architecture and Topology View
Atlas is the most significant infrastructure visibility feature any FinOps platform has ever shipped. It provides region-level infrastructure mapping across AWS, GCP, and Azure in a single view. The Globe view plots every discovered resource by provider and region on a navigable world map. The Canvas view gives you a filterable, zoomable topology surface you can search by region and filter by cloud provider.
This is not a reporting layer. Atlas is the foundation for region-aware governance and remediation planning. Before you enforce a policy, you need to know exactly where it applies, which accounts it touches, and which regions are in scope. Atlas answers that question before you ever click enforce.
Provider support: AWS, GCP, Azure.
2. MCP Server Integration
ZopNight now exposes a Model Context Protocol (MCP) server endpoint, configurable directly under Settings > Organisation. Compatible with Claude, Cursor, and Codex.
Toggle the integration active, copy the server URL, access the setup guide, and generate tokens. This makes ZopNight’s governance context programmable. Your AI assistant can now query ZopNight’s resource state, schedule context, and policy data before taking an action. Policy-aware AI integration and guardrail-enforced automated workflows become possible without custom API work.
One important scope note: no other API or SDK changes shipped in this release. MCP is the sole new developer-facing surface in v2.0.
3. Cost Reports and Budget Tracking
Cost data has moved from buried metrics to a dedicated Cost Reports page that surfaces the numbers that drive cost discipline: Current Estimated Spend, Verified Schedule Savings, Savings Rate, and Cost Trends Over Time with configurable reporting periods.
The new Budget Overview enforces financial accountability at the organizational level. Total Budget, Total Spend, and Budget Health are visible in one place. Forecastable. Audit-ready. Finance teams and engineering leads now have a shared source of truth that does not require a custom dashboard or a spreadsheet export.
4. Dedicated Schedule Management
Schedules used to live inside resource rows. Finding them required knowing which resource to check. That model breaks at scale.
The new standalone Schedules page surfaces every schedule as a card: name, description, next execution time, a 24-hour on/off timeline, verified savings percentage, weekly average cycle, and resource count. Create, review, and manage every schedule from one place. Operational clarity at the page level, not buried in a table row.
5. Override Management
Override exceptions have always been the governance gap that causes 3 AM incidents. You approved an exception for a resource, it expired without notice, and now something is down.
The new Overrides page closes that gap. It surfaces all active and expired overrides in one place, with full audit context: Override Type, Start/End Time with timezone, Reason, and Status. Create and manage production-safe overrides with dependency-aware guardrails. Every exception is visible, traceable, and time-bounded. No guessing which resources have active exceptions.
6. Auto Tagging
Manual tagging is reactive. By the time someone runs a tagging sweep, the resource has already been running untagged for days or weeks.
Auto Tagging moves tag enforcement to the point of discovery. The new Auto Tagging page under Insights surfaces tag suggestions generated the moment a resource is discovered. Suggestions are organized into Pending Review, Accepted, and Rejected tabs. Filter by provider and review tags in bulk.
This shifts tagging from a cleanup task to a governance workflow. Infrastructure hygiene is enforced by policy, not manual effort.
Provider support: AWS, Azure. GCP tag suggestions are planned for a future release.
7. Execution History
Every start/stop action now has a complete, queryable audit trail. The new Execution History page logs each execution with full context: Resource, Status (Started or Stopped), Source (User or Schedule), Triggered By (the person or schedule name), and Timestamp with timezone.
Filter by status, source, resource, sort order, and date range. This is the answer to “what ran last night and who triggered it” without opening a Slack thread or digging through logs. Every action logged, filterable, and audit-ready.
Revamped Core Systems
1. RBAC: Roles and Permissions
Role-Based Access Control has been rebuilt from the ground up. The previous permission model was not granular enough for multi-team governance. The new system ships three system roles with precise policy counts:
| Role | Policies |
|---|---|
| Viewer | 16 |
| Editor | 32 |
| Admin | 52 |
Custom roles can now be created, edited, and deleted to match your organization’s structure. Assign roles directly from Organisation settings. Every team member’s access level is now an explicit governance decision, not a default.
2. Recommendations Engine
The old binary Optimized/Unoptimized status told you a resource had a recommendation. It did not tell you what kind, how severe, or how to prioritize it.
The revamped Recommendations Engine restructures this entirely. Summary cards now show Open, Projected Verified Savings, Applied, and Auto-Resolved counts upfront. New category classifications replace the binary status: Compliance, Discount, Idle, and Rightsizing. A Resource vs. Rule view toggle lets you switch between recommendations grouped by the resource they affect or the rule that generated them. Severity filtering and provider-level account scoping complete the picture.
This is a remediation pipeline. Not a recommendation list.
3. Resource Discovery and Hierarchy
The resource view has moved from a flat table to a parent-child hierarchy. EKS clusters, Auto Scaling Groups, and managed databases now display their child resources with drill-down links. Infrastructure is displayed as it actually exists: hierarchical, dependency-aware, and navigable.
Flat tables obscure dependency relationships. When a parent resource has 40 child nodes, knowing that matters before you schedule a stop action. The hierarchy view makes those relationships explicit.
4. Settings: Fully Operational
The Settings section was previously non-functional in meaningful ways. In v2.0, it is a complete configuration hub with six sub-tabs:
| Tab | What It Controls |
|---|---|
| Organisation | Org details, member management, MCP Server config |
| Cloud Accounts | Connected provider accounts |
| Notifications | Alert preferences and channels |
| Preferences | Platform-level defaults |
| Teams | Team management (moved from top-level navigation) |
| Roles | Role definitions and assignments |
Governance, access, and operational preferences are configured in one place. No hunting across navigation.
5. Dashboard: Governance-First Metrics
The old Overview page has been replaced. The new governance-focused Dashboard leads with the metrics that matter: Total Resources, Current Estimated Spend, Realized Verified Savings, and Savings Rate.
The Efficiency and Spending Velocity chart shows Unblended Cost vs. Net Verified Savings on Daily, Weekly, and Monthly views. Scheduler event dots have moved to the dedicated Execution History page. The Dashboard reports estate health. The History page reports what happened. Two distinct jobs, two distinct pages.
6. Audit Logs: Structured and Filterable
Audit Logs have moved from a chart-and-table hybrid to a clean, structured, filterable table. Filter by Action type (Created, Updated, or Deleted), Resource, Status, User, sort order, and date range. Each row shows Action, Timestamp, Resource with type label, User, Status with HTTP code, and Description. Rows expand for full detail.
The audit trail is now queryable and precise. Compliance reviews no longer require scrolling through a mixed chart-and-table layout.
7. Groups: Decoupled from Schedules
Groups have moved from an accordion list with inline schedule bars to a card layout showing group name, description, and resource count. Schedule management is now fully decoupled and handled on the dedicated Schedules page.
Clean separation between what is grouped and what is scheduled. Mixing both concerns into one view created confusion at scale. They are separate concerns and now have separate pages.
Migration and Breaking Changes
- RBAC — All existing user assignments have been migrated to the new role structure. Users previously assigned basic access map to the Viewer role. Users with elevated access map to Editor or Admin based on prior permission scope. Review your team’s role assignments under Settings > Roles to confirm.
- Groups and Schedules — Existing group-schedule associations remain intact. Schedules now appear on the dedicated Schedules page rather than inline within Groups. No action required.
- Settings — All previously configured cloud accounts, notification preferences, and team structures have been preserved. No re-configuration needed.
- Dashboard — Historical scheduler event data is now accessible from the Execution History page, not the Dashboard. Bookmarks or saved links to the old Overview page will redirect.
Performance Improvements
Two measurable performance gains were shipped in v2.0.
- Resource Discovery — 30% faster scan time for hierarchical accounts, EKS clusters, Auto Scaling Groups, and managed databases.
- Recommendations Engine — Significantly faster load times for estates with 1,000 or more active recommendations.
Coming Up Next
Two major capabilities are in active development.
- Showback — Maps cost attribution to teams, projects, and business units. Every dollar in your cloud bill has an owner. Audit-ready and forecastable.
- Autoscaler — Policy-driven autonomous scaling with dependency-aware guardrails. Infrastructure that right-sizes itself within governance boundaries without manual intervention.
Both capabilities are being built on the governance primitives shipped in v2.0.
What v2.0 Means for Your Team
Seven new features and seven rebuilt systems are a large release. The thread connecting all of it is the same: governance needs to be complete at every layer.
- Atlas makes your infrastructure visible before you enforce.
- Cost Reports and Budget Tracking make spending accountable.
- Auto Tagging and Execution History make every action traceable.
- MCP Integration makes your governance context programmable.
- RBAC makes access itself a governed decision.
ZopNight v2.0 is available now. Explore the release at zop.dev/zopnight.
