Cloud cost
Unit economics
Infrastructure cost expressed per customer, per request, or per transaction, instead of as a single company-wide total.
Last updated
Definition
A total monthly cloud bill tells you almost nothing about whether the business is getting more efficient or less; it just grows with usage. Dividing that same spend by an active-customer count, a request count, or a completed transaction count turns it into a number you can compare over time: is it costing more or less to serve the same unit of value as the product and its usage evolve?
This is where cloud and AI cost measurement converge, since per-request cost (the AI/LLM equivalent) applies the same idea to a metered API call instead of an infrastructure footprint.
A per-unit cost view is also exportable as a report. Save it once and it can generate a CSV or PDF export on demand, or be delivered to a channel on a recurring schedule for whoever owns the metric.
Where it shows up
Unit economics is a computed metric, not a native billing field: it takes a total spend figure straight from the billing export and divides it by an active-customer count, a request count, or a completed-transaction count pulled separately from the product's own usage data over the same period.
What makes it expensive
The costly mistake is watching a total monthly bill in isolation and mistaking growth in spend for a problem, when it may simply track growth in usage. The question a total cannot answer is whether serving one customer costs more this quarter than it did last quarter. Divide before you worry.
Related
More in Cloud cost
- Committed use discount (CUD)
- Reserved instance (RI)
- Savings plan (SP)
- On-demand vs. spot instances
- Data egress
- Amortized, blended, and unblended cost
- Billed vs. effective vs. list vs. contracted cost
- Rightsizing
- Idle and orphaned resources
- Storage class
- Lifecycle policy
- Incremental snapshot
- Allocatable capacity
- Requests vs. limits
- Cluster idle
- Workload idle
- Bin packing
- Cost allocation tags
- Tag coverage
- Unallocated spend
- Showback vs. chargeback
- RI/SP coverage and utilization
- Observability tax
- Metric cardinality
- High-water-mark billing
- Log ingest vs. index
- Snowflake credit
- Auto-suspend / resume minimum
- BigQuery slot
- Bytes scanned & partition pruning
- Time Travel & Fail-safe
A total nobody owns, nobody fixes.
An unattributed cost stays unowned. CostMon assigns spend to an owner, so someone can act on it.