Skip to main content
Billing-backed, per resource, per day

Every dollar,
traced to what
spent it.

A cost report is only useful if you can defend it in a room with finance. ZopNight reads your cloud's own billing data where it exists and rated pricing where it does not, row by row, and tells you which of the two produced every figure.

7anomaly dimensions
3severity bands
2reconciled cost sources
Team + tagattribution

Two sources, reconciled per row.

Not an org-wide switch that one unsynced account can break.

01

Read the real bill

Billing cost comes from AWS Cost Explorer or a CUR 2.0 export, Azure Cost Management, and GCP BigQuery net of credits. Azure uses amortized cost, so a reserved VM shows its real effective daily rate instead of the zero that actual cost reports at subscription scope.

02

Fill the gaps per row

A resource-day with a billing-backed row uses it. A resource-day without one falls back to rated pricing. Same org, same query, decided per row. An org-wide gate used to let one unsynced account suppress real billing for everything. It was removed.

03

Attribute it

Split by team, with shared resources divided across owning teams, or by tag, using both your cloud tags and the tags ZopNight derived. A Sankey view shows where the money actually flows.

04

Catch the breaks

Anomaly detection runs daily across seven dimensions. Each anomaly names what changed: an instance resize, a new resource, a reservation expiring, a schedule that failed to fire, or a resource running unscheduled.

Built to not cry wolf.

An alerting system people mute is worse than no alerting system.

Severity bands
Warning at 30 to 150 percent deviation, critical at 150 to 500, emergency above 500. Detected by both percent deviation against a 7-day rolling average and z-score. The higher severity wins.
False-positive guards
A minimum of 4 data points, a minimum of one dollar a day, and a standard deviation above 10 percent of the mean. Resource-level alerts are capped at the top 10 per org by deviation.
Redistribution suppression
When cost shifts between teams but the net change is under 20 percent, both anomalies are suppressed. A reorg is not an incident.
Dimensions
Org, cloud account, resource type, resource group, resource, team, and the Azure hierarchy parsed from ARM resource IDs. Evaluation runs whether or not you have configured a single notification channel.

Bring a number finance cannot argue with.

Connect billing export access and the first reconciled report is ready after the next sync.

Multi-cloud automation· Production-ready in 30 min· SOC 2 · ISO 27001· 20–60% off the bill, first month· 4 platforms · 1 console· Multi-cloud automation· Production-ready in 30 min· SOC 2 · ISO 27001· 20–60% off the bill, first month· 4 platforms · 1 console·