ZopNight for FinOps Teams: Mapped to the FinOps Framework
You already have a framework. This page maps ZopNight onto it, capability by capability, including the parts it leaves to you.
A FinOps practitioner, in the FinOps Foundation’s words, bridges business, engineering and finance by applying the FinOps Framework. The framework runs through three phases (Inform, Optimize, Operate) and four domains: Understand Usage and Cost, Quantify Business Value, Optimize Usage and Cost, and Manage the FinOps Practice. The table below maps the capabilities where ZopNight does real work to the feature that does it. The capability names are the Foundation’s own.
Capability map
| FinOps capability | What ZopNight does |
|---|---|
| Allocation | Team showback with shared resources split equally across owning teams; tag showback from AWS tags, GCP labels, Azure tags and accepted smart tags; unattributed spend tracked separately |
| Reporting and Analytics | Billing overlay from Cost Explorer or CUR 2.0, Azure Cost Management (amortized) and GCP BigQuery (net of credits); unmatched invoice lines added so totals reconcile; Sankey cost flow |
| Anomaly Management | Daily detection across seven dimensions, severity bands, root-cause analysis per anomaly, redistribution suppression |
| Budgeting | Budgets per cloud account, resource, resource group or AI provider, with threshold alerts |
| Unit Economics | Cost per user, order, request or signup from denominators you push, upload or let ZopNight pull |
| Usage Optimization | Idle, rightsizing, schedule and orphan recommendations with evidence; off-hours schedules; remediation workflows |
| Rate Optimization | Advisory 1-year and 3-year commitment recommendations priced from real rate ratios and measured uptime, with a break-even gate |
| Governance, Policy and Risk | Tagging policies, IaC plan checks with priced guardrails, recommendation policies that open Jira tickets |
What ZopNight leaves to you
Team and tag views are showback, attributed-only by design; turning them into internal invoices, the framework’s Invoicing and Chargeback capability, stays with finance. Commitment recommendations are advisory only, so purchasing reservations or savings plans stays with you. The forecast in the product is an average-of-last-N projection on the unit-economics chart, not a budget forecast.
Numbers you can put in front of finance
Three design choices matter to a practitioner. First, a recommendation’s status (what the team says it did) is stored separately from its resolution state (what ZopNight measured afterwards against a frozen baseline), so “applied” is never taken on trust. Second, the recommendations export de-duplicates savings per resource, so overlapping options are not summed into an inflated headline. Third, Azure costs use amortized billing so reservation purchases are spread across their term per resource, while AWS and GCP use actual cost.
A FinOps dashboard preset is built in. Build your practice around it with setting up a FinOps practice, check maturity with the FinOps maturity model, and compare attribution models in showback vs chargeback.
Questions we get a lot.
If yours isn't here, email us and we'll answer directly.
Why do tag totals exceed the organization total?
Tag showback gives each tag key and value the full cost of the resources carrying it, so a resource with several tags appears under each. Team showback splits shared resources instead, so team totals do not double-count.
Does ZopNight buy reservations or savings plans?
No. Commitment recommendations are advisory. They show 1-year and 3-year options priced from live rates, and suppress any option that does not clear a break-even margin.