Committed use discountCUD
A discount a provider gives in exchange for committing to a minimum spend or usage level for a fixed term.
Read the full definition →Glossary
Answer-first definitions for the cost terms that turn up on your AWS bill, your Anthropic invoice, and every FinOps review in between.
Last updated 50 terms
The pricing models, cost-accounting bases, and waste patterns behind an AWS-style bill.
A discount a provider gives in exchange for committing to a minimum spend or usage level for a fixed term.
Read the full definition →A commitment to a specific instance type in a specific region or zone, discounted versus on-demand pricing.
Read the full definition →A commitment to a dollar-per-hour spend level, applied automatically across compute regardless of instance family.
Read the full definition →On-demand pricing charges the full published rate with no commitment; spot pricing sells unused capacity at a steep discount but can be reclaimed with little notice.
Read the full definition →The fee a cloud provider charges for data leaving its network, including (on most providers) transfer between availability zones.
Read the full definition →Three different bases for reporting the same underlying spend: unblended is the raw per-resource rate, blended averages a rate across an account, and amortized spreads upfront commitment costs evenly across the term they cover.
Read the full definition →The four cost columns FOCUS defines for the same charge: cash-basis, amortized, pre-discount, and negotiated-rate. That's why two dashboards can quote two different numbers for the same month.
Read the full definition →Matching a resource's provisioned size to its actual, observed utilization instead of the peak it was originally sized for.
Read the full definition →Resources still running (and billing) despite doing no meaningful work: idle resources are underused, orphaned resources have no owner or purpose left at all.
Read the full definition →A pricing/durability tier for stored data: the same bytes cost a different amount, and take a different amount of time to read back, depending which class they sit in.
Read the full definition →A rule that automatically moves or deletes stored data after a set condition (an age threshold, most often) without anyone touching it by hand.
Read the full definition →A backup that stores only the blocks changed since the previous snapshot in its chain, not a full independent copy. That's why deleting one frees far less space than its listed size suggests.
Read the full definition →What's left for pods to request on a Kubernetes node, after the kubelet, container runtime, OS, and DaemonSets reserve their own slice of it.
Read the full definition →A request is what the scheduler reserves for a container and determines whether it fits on a node; a limit is just a ceiling the kubelet enforces at runtime.
Read the full definition →Node capacity that's schedulable but was never even requested by any pod: a bin-packing and autoscaling problem, not a request-sizing one.
Read the full definition →Capacity a pod requested, and had reserved on its behalf, but doesn't use. A request-sizing problem, fixed by right-sizing to observed usage.
Read the full definition →How tightly a scheduler packs pods onto the fewest nodes possible, given their requests. Loose packing strands capacity as cluster idle across many half-empty nodes.
Read the full definition →Key-value labels applied to cloud resources so spend can be grouped by team, project, environment, or customer instead of showing up as one undifferentiated total.
Read the full definition →The share of spend (measured by dollars, not resource count) that carries a required tag set.
Read the full definition →The share of a bill that can't be attributed to a real owner, because it isn't tagged, its tag is wrong, or it structurally can't carry a tag at all.
Read the full definition →Showback reports each team's cloud spend for visibility only; chargeback bills that spend back to the team's budget.
Read the full definition →Infrastructure cost expressed per customer, per request, or per transaction, instead of as a single company-wide total.
Read the full definition →Coverage measures what share of eligible usage is discounted by a commitment; utilization measures what share of the commitment you purchased is being used.
Read the full definition →The cost of the monitoring stack itself (hosts, custom metrics, traces, and logs) growing on its own, independent of the infrastructure it's watching.
Read the full definition →The number of unique metric-name + tag-value combinations a monitoring platform has to store and bill for, not the number of metric names your code emits.
Read the full definition →A billing method that charges close to a resource's peak usage during a period, rather than its average. A spike lasting long enough can set the whole month's charge.
Read the full definition →Two separate charges most observability platforms bill independently: ingest is charged the moment a log event arrives; index (or retention) is a recurring charge for keeping it searchable afterward.
Read the full definition →Snowflake's unit of compute billing. A virtual warehouse burns credits every second it runs, at a rate that doubles with each warehouse size.
Read the full definition →Snowflake's default behavior of suspending an idle warehouse to stop billing it, and resuming it on the next query — with each resume billing at least 60 seconds regardless of how short the query is.
Read the full definition →A unit of query-processing capacity in BigQuery. On-demand queries draw from a shared pool billed by bytes scanned; an Editions reservation buys dedicated slots billed by slot-hour instead.
Read the full definition →On-demand BigQuery bills by how much data a query reads, not how long it runs. Partition pruning and column selection are the two levers that shrink that number.
Read the full definition →Two Snowflake mechanisms that keep changed or deleted data recoverable, and keep billing storage for it: Time Travel for a configurable window, Fail-safe for a fixed 7 days after that.
Read the full definition →How usage-based model API spend is metered, priced, and controlled.
The basic unit of text an LLM API meters and bills by: roughly three to four characters of English text, not a whole word.
Read the full definition →Most LLM APIs price input tokens (the prompt you send) and output tokens (the response generated) separately, with output usually priced several times higher.
Read the full definition →The maximum number of tokens (prompt, conversation history, and generated output combined) a model can process in a single request.
Read the full definition →A pricing and performance feature that discounts (and speeds up) tokens repeated across requests, instead of billing the full input rate every time.
Read the full definition →An asynchronous request mode that trades a longer turnaround (minutes to hours) for a significant discount versus real-time API calls.
Read the full definition →The standard unit LLM providers use to publish pricing: the dollar cost of one million input or output tokens, since a single token is too small a unit to price meaningfully.
Read the full definition →The fully-loaded cost of a single API call (input tokens, output tokens, and any tool calls) expressed as one number per request or per completed task.
Read the full definition →Fine-tuning cost is a one-time (or periodic) training expense to specialize a model; inference cost is the ongoing, usage-based cost of running it.
Read the full definition →Routing each request to the cheapest model capable of handling it well, instead of sending every request to the most capable (and most expensive) model available.
Read the full definition →The habits and metrics that turn a bill into something a team can manage.
The operating practice of managing cloud (and increasingly AI) spend as a shared responsibility between finance and engineering, on an ongoing cadence.
Read the full definition →The FinOps Open Cost and Usage Specification: an open, vendor-neutral standard for how a provider's cost and usage export is shaped, maintained by the FinOps Foundation.
Read the full definition →Automatically flagging spend that deviates meaningfully from a service or workload's own historical baseline, instead of waiting for a human to notice on the invoice.
Read the full definition →A budget is a target spend ceiling for a scope of cost; a budget alert notifies an owner when actual or forecasted spend approaches or crosses it.
Read the full definition →Projecting future spend from historical trend and known upcoming changes, used to catch a budget overrun before it happens rather than after.
Read the full definition →Current spend annualized (or projected to month-end) as if the recent pace continued unchanged: a quick, if naive, forward-looking number.
Read the full definition →The full cost of a system or vendor decision over its useful life, including costs beyond the sticker price: migration, integration, ongoing operation, and eventual replacement.
Read the full definition →The experience of an invoice arriving dramatically higher than expected, with no earlier warning that it was building.
Read the full definition →A cost-tool pricing model that charges a cut of the spend it manages or the savings it identifies, rather than a flat fee.
Read the full definition →Provider pricing pages change without notice. CostMon tracks the bill that pays for it.