ZopNight by Role: What Each Cloud Cost Owner Needs
The same bill means different work to a CTO, an SRE and a FinOps analyst. Start from what you are accountable for.
Cloud cost has several owners at once. Leadership answers for the total, finance for the allocation, engineering for the usage. The FinOps Framework reflects this with core personas (FinOps Practitioner, Engineering, Finance, Leadership, Procurement and Product) rather than a single owner. Each guide below starts from one role’s accountabilities and maps them to specific ZopNight capabilities, with the limits stated.
Role guides
- CTOs: a total that reconciles to the invoice, de-duplicated savings for the board, unit cost, and a read-only start.
- VPs of Engineering: team-scoped access and budgets, recommendations routed into Jira, and applied status checked against measured evidence.
- Engineering managers: your team’s showback, budget alerts, anomaly root causes at team scope, and resource ownership from activity logs.
- FinOps teams: a capability-by-capability map to the FinOps Framework, including what ZopNight leaves to finance.
- Platform engineers: IaC policy in pull requests, derived tagging, MCP access with write tiers off by default, and Cloud IAM Import.
- SRE teams: blast radius before a change, how failed actions are handled, autoscaler modes, and the known reliability gaps.
- DevOps engineers: readable schedules, expiring overrides, Kubernetes namespace scheduling, alerts and remediation.
- Cloud architects: topology, one-hop impact analysis, priced guardrails at plan time, and adopting existing scaling policies.
If the rules of your industry shape the bill more than your role does, see the guides by industry.