Cost Allocation
Tagging enforced at provisioning, and apportioning shared costs.
3 to work through
-
intermediate
Forty percent of your cloud spend is untagged. What do you do?
2 min answer -
advanced
A multi-tenant platform needs to know what each customer costs to serve. What makes this hard, and how is it approached?
2 min answer -
advanced
Tag coverage is at 98% and teams still argue about their bill every month. Roughly a fifth of the spend is shared - the service mesh, the log pipeline, NAT gateways, the Kafka cluster, and the commitment discounts. How would you allocate it?
3 min answer
5 terms in this topic
Amortised Cost View
Reporting each team's spend at the effective discounted rate spread across a commitment term, so a team's number moves only when its own usage moves …
practiceCost Allocation
Attributing spend to the team, service or customer that causes it — the prerequisite for every other cost conversation.
practiceCost Allocation Tagging
A mandatory, enforced tagging scheme that attributes every resource to an owner, so spend can be understood and acted on below the level of the whole…
practiceCost Attribution
Assigning every unit of infrastructure spend to a team and a product, enforced at resource creation - the prerequisite without which no other cost co…
practiceStructural Cost Attribution
Deriving cost ownership from deployment boundaries - account per workload, cluster per team - rather than from tags, because tagging discipline never…
Neighbouring topics
Cost & FinOps
General material on the economics of an architecture.
Total Cost of Ownership
Lifetime cost including people, operations, upgrades and exit.
Cloud Pricing Models
On-demand, committed and spot, and the crossover arithmetic.
Reserved & Committed Capacity
Committing the baseline, laddering terms, and expiry as a silent failure.
Spot & Interruptible Capacity
Deep discounts for work that can be interrupted and resumed.
Unit Economics
Cost per request, per tenant, per transaction — the actionable number.
Cost per Request
Fully-loaded per-unit cost, including the lines usually left out.
Storage Costs
Tiering, lifecycle policies, retrieval charges and minimum durations.
Network & Egress Costs
Cross-zone and cross-region transfer that appears on no diagram.
Compute Optimisation
Instance families, utilisation, and architecture that wastes less.
Rightsizing
Matching provisioned resources to observed demand rather than to a guess.
Showback & Chargeback
Making teams see, or own, the cost of what they run.
Architecture Cost Modelling
Pricing a design before building it, at expected and at ten times volume.
Cost vs Reliability
Each nine costing an order of magnitude, and pricing the failure instead.
Observability Cost
Telemetry bills, cardinality control and retention tiering.
Licence & Vendor Costs
Per-core, per-seat and per-environment terms that shape designs.
FinOps Practice
Inform, optimise, operate — and cost as a design-review criterion.
Waste Elimination
Idle environments, orphaned volumes, forgotten instances, dead data.
Cost Governance
Budgets, anomaly alerts, quotas and preventive policy.