Unit Economics for Cloud Cost: Per-MAU, Per-Order, Per-Request
Total spend tells you what the bill is. Cost per unit tells you whether it is growing faster than the business it supports.
Unit economics for cloud cost is the practice of dividing technology spend by a measure of what that spend produces: monthly active users, completed orders, API requests, signups, or any other unit the business counts. The result, a cost per unit, lets you judge a rising bill in context. Spend that doubles while the unit count triples is a product getting more efficient; spend that doubles while units stay flat is a problem.
The FinOps Foundation’s Unit Economics capability frames it as bringing together what an organization spends on technology and the value that spending creates, because without a way to relate cost to benefit it is hard to know whether spending is appropriate. It lists examples at two levels: business metrics such as cost per transaction, per customer, or relative to revenue, and technical metrics such as cost per service request, per workload, per GB stored, or per token. It also advises distinguishing the two kinds and reading them as a trend over time within a defined scope, rather than forcing comparisons across unrelated products.
Choosing the unit
A good unit has three properties: it moves with the load the infrastructure serves, it is counted reliably somewhere outside the cloud bill, and the people who own the cost recognize it.
| Unit | Fits | Watch out for |
|---|---|---|
| Cost per monthly active user | Consumer and SaaS products | MAU definitions differ between analytics tools; fix one and keep it |
| Cost per order | Commerce and marketplaces | Refunds and cancellations; decide whether they count |
| Cost per 1,000 requests | APIs and platform teams | Health checks and bot traffic inflate the denominator |
| Cost per signup | Products in acquisition mode | Signups lag or lead the load they create |
Start with one unit per product. Several units on one chart dilute attention.
Getting the numerator and denominator right
The numerator is cloud cost for the scope, which only works if the scope is allocated: the product’s accounts, projects, or tags, plus an agreed share of shared platform cost. The denominator comes from outside the cloud, from product analytics, the order database, or request logs. Two errors are easy to make. One is mixing scopes, dividing a single product’s cost by company-wide users. The other is mixing periods, dividing monthly cost by a daily active count.
Reading the trend
Cost per unit falling while volume grows suggests economies of scale. Cost per unit rising with flat volume points to a change in the system, such as a new service, a pricing change, or waste, and is worth a look at the cost breakdown for the same period. When a step change appears, check it against the release and migration calendar before treating it as an anomaly.
Unit economics in ZopNight
ZopNight adds cost per unit as an overlay on the Cost Reports trend chart: you define a business denominator such as monthly active users, orders, 1,000 API requests, or signups, and the chart gains a secondary axis showing infrastructure spend per unit. The numerator comes from ZopNight’s cost data; the denominator is supplied by you, because application metrics are not visible from the infrastructure layer. Values arrive by push API, CSV upload, or a pull endpoint that ZopNight fetches on a daily schedule. Cost per unit is computed as total cost divided by total units per bucket, buckets with a zero denominator are skipped, and the report can be scoped to a team or a tag. A catalog offers five common metric types (MAU, DAU, requests, transactions, signups) for quick setup.
Choosing between the ingest paths is covered in pull API vs push API; scoping cost to a team is covered in cloud cost allocation; and a step-by-step setup is in how to set up cost per MAU.
Questions we get a lot.
If yours isn't here, email us and we'll answer directly.
Can I compute cost per unit for one team rather than the whole organization?
Yes. ZopNight's unit economics report accepts a team or a tag key and value as scope. The cost numerator then comes from that team's or tag's attributed cost; if no values were supplied for that scope, the denominator falls back to the organization-wide metric.
How do I backfill historical denominator values?
Upload a CSV. ZopNight accepts CSV uploads of up to 1 MB or 5,000 rows per file, and all ingest paths upsert by metric and date, so re-sending a day replaces it rather than duplicating it.
Should cost per unit include shared platform cost?
Decide once and document it. Including an agreed share gives a truer full cost; excluding it keeps the metric closer to what the product team controls. Changing the rule later breaks the trend.