Unit Economics: Cloud Cost per Customer, Order or Request

What it shows

Unit economics adds a second axis to the Cost Reports trend chart: infrastructure spend divided by a business count you choose. Monthly and daily active users, API requests, transactions and signups are ready-made choices, and you can define your own, such as completed orders, with a name, label and display scale (per unit, per hundred or per thousand).

The numerator is ZopNight’s own cost data. The denominator has to come from you, because application metrics such as orders are not visible from the infrastructure layer.

Three ways to send the denominator

• Push API. Your pipeline posts date and value pairs for a metric.
• CSV upload. Useful for a backfill or a one-off load of history.
• Pull API. Register an HTTPS endpoint with its authentication and ZopNight fetches it on a daily schedule. A Test fetch button runs the full pull path once before the schedule starts, and the endpoint credential is stored encrypted. Outbound fetches are checked against private and internal address ranges before they are made.

All three write to the same store, and re-sending a date overwrites rather than duplicates it.

How the number is computed

For each daily, weekly or monthly bucket, cost per unit is the sum of cost divided by the sum of the metric. A bucket with a zero denominator is skipped rather than drawn as infinity. When there is enough history, a simple forecast based on the average of recent points is included.

You can narrow the view to a team or a tag value. In that case the cost side comes from showback attribution, and if you have not sent a team-specific denominator, the org-wide metric is used.

Where it fits

Unit cost is the metric that lets finance and engineering talk about the same line. It depends on good attribution, so set up showback first if you want per-team unit cost, and read unit economics for cloud cost or cost per MAU for how to pick a denominator. Push versus pull is compared in pull API vs push API.