Licence & Vendor Costs
Per-core, per-seat and per-environment terms that shape designs.
5 to work through
-
intermediate Multiple choice
A design-collaboration SaaS at Canva's scale licenses stock photography and fonts on a per-use royalty. Exports have grown fivefold in 2026 while royalty reporting is still derived from the asset CDN's request logs, and the vendor's audit says the reported numbers no longer match usage. Which change fixes reporting without changing what users can do?
3 min answer -
intermediate
An enterprise's database licensing is tied to processor cores, and a virtualisation change unexpectedly multiplies the licence cost. How should licensing influence architecture?
2 min answer -
advanced Multiple choice
A data tooling vendor licences its product per environment plus per named seat. The platform team is about to give every pull request an ephemeral preview environment containing the full stack. Which change keeps the licence bill flat without abandoning preview environments?
2 min answer -
advanced
A per-core database licence makes horizontal scaling more expensive than vertical. How does that change your design, and would you challenge it?
2 min answer -
advanced
A team's licence and managed-service costs are growing faster than its infrastructure. How should it decide what to bring in-house?
2 min answer
3 terms in this topic
Billable-Event Metering
Recording the event a contract actually charges for at the point in the system where that obligation is created, rather than inferring it from delive…
conceptLicence Costs
Software licensing whose pricing model frequently constrains architecture more than its technical characteristics do.
conceptLicence Metric Risk
The exposure created when a software licence is priced on a unit that cloud architecture changes unpredictably, such as cores, sockets or instances.
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.
Cost Allocation
Tagging enforced at provisioning, and apportioning shared costs.
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.
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.