# FinOps: the framework, tagging, FOCUS and a 90-day plan

> FinOps is an operational framework and cultural practice that maximizes the business value of technology. Phases, tagging, FOCUS, Kubernetes and a 90-day plan.

- URL: https://computese.com/finops/
- Author: Duong Quan Nguyen, CEO, Computese
- Published: 2026-11-21
- Updated: 2026-11-21
- Topics: Cloud

## In short
- FinOps is an operational framework and cultural practice that maximizes the business value of technology through collaboration between engineering, finance and business teams. It is more than a way to save money.
- The Framework runs in three iterative phases, Inform, Optimize and Operate, and rates maturity as Crawl, Walk or Run. Its sample Crawl goals are at least 70% of cost allocated to a known owner and forecast variance below 20%.
- Allocate before you optimize. Enforce a few required tags at creation, in code and by policy, and measure coverage in money. On AWS, a tag reaches billing reports only after you activate it as a cost allocation tag.
- FOCUS is an open billing data specification, and FOCUS 1.4 was ratified on June 4, 2026. As of October 2026, AWS exports FOCUS 1.0 or 1.2, Azure lists 1.2-preview and Google Cloud's BigQuery export is a Preview.
- Kubernetes tools price the gap between requests and usage by different rules, commitments are paid whether or not a matching resource runs, and budgets alert without stopping spend by default.

FinOps is, in the FinOps Foundation's words, "an operational framework and cultural practice" that maximizes the business value of technology through collaboration between engineering, finance and business teams. It works through three phases, Inform, Optimize and Operate, and it is more than a way to save money.

This guide covers the 2026 framework, a tagging policy you can enforce in code, shared costs, FOCUS billing data, Kubernetes allocation, savings levers and a 90-day plan. Tags belong in code, so it pairs with our guide to [infrastructure as code](https://computese.com/infrastructure-as-code/). Cloud vendor details are as documented in October 2026.

## What is FinOps, and what is it not?

The [FinOps Foundation's definition](https://www.finops.org/introduction/what-is-finops/), marked updated in March 2026 and read in October 2026, is: "FinOps is an operational framework and cultural practice which maximizes the business value of technology, enables timely data-driven decision making, and creates financial accountability through collaboration between engineering, finance, and business teams." The name is a portmanteau of "Finance" and "DevOps".

Drop two misreadings early:

- **It is not a cost-cutting project.** "If it seems that FinOps is about saving money, think again," the Foundation writes. Sometimes a business tightens the belt and sometimes it invests more; the goal is to identify, communicate and optimize the value behind technology decisions.
- **It reaches beyond the public cloud.** The Foundation extends the practice to SaaS, licensing, data centers and data cloud platforms, but this guide covers public cloud and Kubernetes.

If your bill jumped after a migration, our [cloud migration strategy](https://computese.com/cloud-migration-strategy/) guide covers cost and governance after cutover.

## How is the FinOps Framework organized?

The [Framework](https://www.finops.org/framework/) is "flexible and non-prescriptive": you take the parts you need. Its [six principles](https://www.finops.org/framework/principles/), listed in no particular order, cover collaboration, business value, ownership of usage, accessible and timely data, central enablement and the variable cost model of the cloud.

The [phases](https://www.finops.org/framework/phases/) are the working loop, run iteratively. In **Inform**, you examine cost, usage and efficiency data. In **Optimize**, you document options, including usage optimization, "using fewer resources to achieve an acceptable outcome", and rate optimization, "paying an appropriate amount for the resources we must use". In **Operate**, you implement the changes and loop back.

The Capabilities sit in four [domains](https://www.finops.org/framework/domains/): Understand Usage & Cost, Quantify Business Value, Optimize Usage & Cost and Manage the FinOps Practice. The Framework names six [core personas](https://www.finops.org/framework/personas/): FinOps Practitioner, Engineering, Finance, Product, Procurement and Leadership. A [FinOps Scope](https://www.finops.org/framework/scopes/) is "a defined segment of spending across technology categories", aligned to business constructs such as a product, cost center or environment.

Maturity is Crawl, Walk or Run. The [maturity model](https://www.finops.org/framework/maturity-model/) lists sample goals from the FinOps community:

| Maturity | Cost allocated | Forecast vs actual variance |
| -------- | -------------- | --------------------------- |
| Crawl    | At least 70%   | Below 20%                   |
| Walk     | At least 85%   | Less than 10%               |
| Run      | More than 90%  | Less than 5%                |

The same page warns that "an organization's goal should never be simply to achieve a 'Run' maturity in every Capability".

The [2026 revision](https://www.finops.org/insights/2026-finops-framework/), published on March 19, 2026, updates the definition and adds Executive Strategy Alignment as a Capability.

## How do you build a tagging policy that holds?

Allocation comes first, because anomaly alerts, budgets, unit costs and commitments all assume you can say whose spend it is. The [Foundation](https://www.finops.org/framework/capabilities/allocation/) says allocation needs an allocation strategy, a tagging strategy and a shared cost strategy, and that tagging works better with automation, such as infrastructure as code or tools that manage tags after launch. Count coverage in money, because the maturity goals above are stated in cost.

![A long receipt of grey bars is sorted by small tag symbols into three bins, one per symbol. A fourth, orange bin collects the bars that have no tag, including two long ones.](https://computese.com/images/blog/finops/receipt-sorted-by-tag.460749d5d9-1536.webp)

*Costs without a tag fall into a bin no team owns, so measure coverage in money.*

Start with four keys. This table is an example policy, not a standard:

| Key           | Values (example)                                 | The question it answers                              |
| ------------- | ------------------------------------------------ | ---------------------------------------------------- |
| `costcenter`  | Codes from your finance chart, such as `cc-1001` | Which budget pays for this?                          |
| `environment` | `production`, `staging`, `development`, `test`   | Can it be switched off outside working hours?        |
| `owner`       | A team alias, not a person                       | Who is told when it grows, and who books the saving? |
| `application` | The service name in your catalog                 | Which product does it belong to, for unit costs?     |

Use lowercase for keys and values. AWS tag keys and values are [case sensitive](https://docs.aws.amazon.com/organizations/latest/userguide/orgs_manage_policies_tag-policies.html), so `CostCenter` and `costcenter` are different tags. Google Cloud [label keys and values](https://docs.cloud.google.com/resource-manager/docs/labels-overview) can contain only lowercase letters, numeric characters, underscores and dashes (international characters are allowed), so one lowercase convention works on both.

Enforce at creation, not in cleanup. The Foundation calls this shifting left: ownership and metadata standards are "enforced at the point a resource is created, not reconstructed later through tagging cleanup." These controls combine:

| Control                                                                                                                                                                                                                                               | What it does, and its limit                                                                                                                                                                                                                         |
| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Code (AWS): Terraform provider with `tag_policy_compliance = "error"`                                                                                                                                                                                 | Checks required tags before a resource is created and before its tags change; non-tag updates are always permitted. Needs [provider 6.22.0 or later](https://docs.aws.amazon.com/organizations/latest/userguide/enforce-required-tag-keys-iac.html) |
| Pipeline (AWS): CloudFormation hook `AWS::TagPolicies::TaggingComplianceValidator`                                                                                                                                                                    | Warn mode lets deployments proceed; Fail mode blocks those missing required tags. Activate it in every account and Region you want covered                                                                                                          |
| Guardrail (AWS): a [service control policy](https://aws.amazon.com/blogs/mt/implement-aws-resource-tagging-strategy-using-aws-tag-policies-and-service-control-policies-scps/) denying `ec2:RunInstances` when `aws:RequestTag/costcenter` is missing | Blocks untagged EC2 launches. AWS described this pattern in 2021, when a tag policy enforced a tag's accepted value, not its presence                                                                                                               |
| Azure: [Azure Policy](https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/tag-policies) "Require a tag on resources" (deny) and "Inherit a tag from the resource group if missing" (modify)                                     | The first does not apply to resource groups; the second leaves an existing tag with a different value unchanged                                                                                                                                     |

> [!WARNING]
> A tag on a resource is not yet a tag in your cost data. On AWS, a tag key reaches billing reports only after you [activate it as a cost allocation tag](https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/activating-tags.html), which can take up to 24 hours to appear for activation and up to 24 more to activate. Only the management account (or a standalone account) can open the [cost allocation tags manager](https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/custom-tags.html). On Azure, [tag inheritance](https://learn.microsoft.com/en-us/azure/cost-management-billing/costs/enable-tag-inheritance) copies subscription and resource group tags onto usage records, "and not the resources themselves", within 24 hours for the current month.

On AWS, the organization-level piece is a tag policy. This one follows the AWS [example for required tag keys](https://docs.aws.amazon.com/organizations/latest/userguide/orgs_manage_policies_example-tag-policies.html), in lowercase, and defines one of the four keys; the others follow the same pattern.

```json
{
  "tags": {
    "environment": {
      "tag_key": { "@@assign": "environment" },
      "tag_value": {
        "@@assign": ["production", "staging", "development", "test"]
      },
      "report_required_tag_for": {
        "@@assign": [
          "ec2:ALL_SUPPORTED",
          "rds:ALL_SUPPORTED",
          "s3:ALL_SUPPORTED"
        ]
      }
    }
  }
}
```

In Terraform, HashiCorp's [guide](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/guides/tag-policy-compliance) says the tag policy must be created in the organization's management account and the principal that runs Terraform needs the `ListRequiredTags` permission. In `warning` mode, resources built on Terraform Plugin SDK V2, a majority of the provider's resources, cannot emit warning diagnostics for violations and log a WARN message instead, shown when you set `TF_LOG=warn`.

## How do shared costs, showback and chargeback work?

Some spend has no single owner: a shared cluster, networking, support plans. The Foundation says many early practices adopt an "informed ignore" approach, a business decision to budget shared costs centrally. AWS Cost Categories offer [split charge rules](https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/splitcharge-cost-categories.html) with Proportional, Fixed and Even split methods, though you see the split only on the cost category's details page in the console. Azure [cost allocation](https://learn.microsoft.com/en-us/azure/cost-management-billing/costs/allocate-costs) does not support purchases such as reservations and savings plans and does not affect your invoice; "all chargeback processes happen in your organization outside of Azure".

The [Foundation](https://www.finops.org/framework/capabilities/invoicing-chargeback/) separates showback from chargeback by formality: chargeback sends expenses to official accounting budgets. Its position: "Showback is always required in any FinOps practice, but chargeback is dependent on organizational accounting policies." Invoices arrive "between 3 and 12 days after the end of the previous month in most cases", so showback can run as usage data arrives, and chargeback can follow the invoice.

## What is FOCUS, and which clouds export it?

The FinOps Open Cost and Usage Specification ([FOCUS](https://focus.finops.org/what-is-focus/)) is "an open specification that defines clear requirements for technology billing data generators to produce consistent datasets". Without it, you normalize each vendor's terminology and metrics before analysis.

![Three differently laid out billing sheets, one per cloud provider, feed through a single funnel into one common table of identical columns whose header row is orange.](https://computese.com/images/blog/finops/focus-common-table.6582e2476e-1536.webp)

*FOCUS defines one set of column names, so one query can cover several providers where their exports conform.*

As of October 2026 the latest version is [FOCUS 1.4](https://focus.finops.org/docs/specification/v1-4/), ratified on June 4, 2026, with new Invoice Detail and Billing Period datasets and, the FOCUS site says, zero incompatible changes. Providers lag the specification, so check each export's version before combining them:

| Provider        | Export status, October 2026                                                                                                                                                                                                                                                                                                                                                                     |
| --------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| AWS             | [Data Exports](https://docs.aws.amazon.com/cur/latest/userguide/what-is-data-exports.html) offers FOCUS 1.0 or 1.2. Version 1.2 has been [generally available since November 19, 2025](https://aws.amazon.com/blogs/aws-cloud-financial-management/data-exports-for-focus-1-2-is-now-generally-available/), is recommended for all new implementations and is not backwards compatible with 1.0 |
| Microsoft Azure | The [schema index](https://learn.microsoft.com/en-us/azure/cost-management-billing/dataset-schema/schema-index) lists "Cost and usage details (FOCUS)" for EA and MCA at 1.2-preview                                                                                                                                                                                                            |
| Google Cloud    | The [BigQuery FOCUS export](https://docs.cloud.google.com/billing/docs/how-to/export-data-bigquery-tables/focus-export) is a Preview, available "as is" with possibly limited support                                                                                                                                                                                                           |

Start with these columns (FOCUS 1.4 names):

| Column                                                                                                     | What it holds                                                                                                 | Use it for                                                |
| ---------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------- |
| [`BilledCost`](https://focus.finops.org/docs/specification/v1-4/columns/cost-and-usage/billed-cost/)       | The cost of a charge as invoiced by the invoice issuer in a billing period                                    | Invoice reconciliation, cash-based forecasting, budgeting |
| [`EffectiveCost`](https://focus.finops.org/docs/specification/v1-4/columns/cost-and-usage/effective-cost/) | The cost recognized in a charge period, including amortized portions of related purchases such as commitments | Accrual-based reporting, forecasting, cost allocation     |
| [`Tags`](https://focus.finops.org/docs/specification/v1-4/columns/cost-and-usage/tags/)                    | A JSON object of user-defined and provider-defined tags; may be null, and a key may carry a null value        | Your allocation keys                                      |

The [FOCUS tag coverage use case](https://focus.finops.org/docs/use-cases/v1-4/analyze-tag-coverage/) gives a query and a matching KPI, the percentage of cloud costs that are tagging policy compliant, which "requires an established organizational tagging policy". This PostgreSQL version, which assumes unquoted column names and `Tags` stored as `jsonb`, shows where the untagged dollars sit, by service:

```sql
SELECT
  ServiceName,
  SUM(EffectiveCost) AS total_cost,
  COALESCE(SUM(EffectiveCost) FILTER (
    WHERE NULLIF(Tags ->> 'costcenter', '') IS NULL), 0) AS untagged_cost
FROM focus_data
WHERE ChargePeriodStart >= '2026-09-01'
  AND ChargePeriodEnd <= '2026-10-01'
GROUP BY ServiceName
ORDER BY untagged_cost DESC;
```

`ChargePeriodEnd` is an exclusive bound, as [Google's FOCUS export reference](https://docs.cloud.google.com/billing/docs/how-to/export-data-bigquery-tables/focus-export) spells out, so `<=` keeps September 30. The query counts a missing key, a null value and an empty string as untagged: [PostgreSQL's `->>` operator](https://www.postgresql.org/docs/current/functions-json.html) returns NULL rather than failing when a key does not exist, and [`NULLIF`](https://www.postgresql.org/docs/current/functions-conditional.html) turns an empty string into NULL. Google's export has no `Tags` column: the same information arrives in `x_Tags`, `x_Labels`, `x_SystemLabels` and `x_ProjectLabels`, so the predicate changes.

## How do you allocate Kubernetes costs?

Kubernetes [places Pods by their requests](https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/): the scheduler uses them to pick a node, and the kubelet reserves at least the requested amount. A generous request therefore reserves capacity whether or not the workload uses it, and someone pays for the gap.

![A server node drawn as a row of eight cells holds two pods. The left pod reserves four cells but fills one, and its three empty cells are orange. The right pod fills both cells it reserves.](https://computese.com/images/blog/finops/requests-vs-usage.38f3f23785-1536.webp)

*Placement follows the request, so a generous request reserves capacity the workload does not use.*

Tools price that gap by different rules, so check the rule before you compare numbers. [GKE cost allocation](https://docs.cloud.google.com/kubernetes-engine/docs/how-to/cost-allocations) data "is based on resource requests, not resources consumed". AWS [split cost allocation data](https://docs.aws.amazon.com/cur/latest/userguide/enabling-split-cost-allocation-data.html) for EKS lets you choose resource requests or, with Amazon Managed Service for Prometheus, "the higher of Kubernetes pod CPU and memory resource requests and actual utilization". The [OpenCost specification](https://opencost.io/docs/specification/) says workload cost should be understood as "max(request, usage)" for resources with allocation costs, such as CPU and GPU. A Pod that requests 2 vCPU and uses 0.5 carries the cost of 2 under each rule. A Pod that requests 0.5 and bursts to 2 carries the cost of 0.5 under a requests-only rule and of 2 under a higher-of rule.

OpenCost is a [CNCF project](https://www.cncf.io/projects/opencost/): accepted on June 17, 2022 and Incubating since October 25, 2024. Its specification defines cluster idle cost as the portion of resource allocation cost not allocated to any workload. Choose one allocation rule, write it down and apply it to every team. Subscription platforms add a licence line to the same problem; our [OpenShift vs Kubernetes](https://computese.com/openshift-vs-kubernetes/) guide covers what the OpenShift subscription adds.

## Which optimization levers save money, and what do they risk?

Usage and rate optimization interact. The Foundation's [rate optimization](https://www.finops.org/framework/capabilities/rate-optimization/) guidance warns that a commitment recommendation can conflict with one to change a resource's type or size, so teams may double count the benefit or pay for a year for resources that no longer exist in their original form. Waiting for fully optimized usage "will almost always lead to paying more than a balanced approach", so keep one backlog and rank it by value.

Rightsizing needs care. The Foundation's [usage optimization](https://www.finops.org/framework/capabilities/usage-optimization/) guidance says to examine "longer-cycle periods of high utilization (e.g. higher utilization at month-end or during quarterly busy periods)". AWS [Compute Optimizer](https://docs.aws.amazon.com/compute-optimizer/latest/ug/metrics.html) analyzes metrics from a period over the last 14 days, or up to 93 days if you activate enhanced infrastructure metrics, so by our reading a month-end peak can fall outside the shorter window.

![A tall server with ten slots, only the bottom two filled, stands at the left. A curved arrow leads to a smaller four-slot server at the right with every slot filled, drawn in orange.](https://computese.com/images/blog/finops/right-sized-server.e919ce39ca-1536.webp)

*Rightsizing swaps a mostly idle big box for a smaller one that is actually used.*

| Lever                       | How it saves                                  | What can go wrong                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
| --------------------------- | --------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Rightsizing                 | Fits a resource to measured use               | A short look-back window can miss peaks, as above, and resizing can disrupt service                                                                                                                                                                                                                                                                                                                                                                                         |
| Scheduling non-production   | Stops environments nobody is using            | The Foundation says pre-production resources "should always require scheduled start/stop at launch when feasible"                                                                                                                                                                                                                                                                                                                                                           |
| Storage tiers and lifecycle | Moves or expires data nobody reads            | Colder tiers have minimum durations: [Azure](https://learn.microsoft.com/en-us/azure/storage/blobs/access-tiers-overview) cool 30 days, cold 90, archive 180, and [Google Cloud](https://docs.cloud.google.com/storage/docs/storage-classes) Nearline 30, Coldline 90, Archive 365. [S3](https://docs.aws.amazon.com/AmazonS3/latest/userguide/lifecycle-transition-general-considerations.html) skips objects under 128 KB by default and charges a request per transition |
| Commitments                 | A lower rate in return for committed usage    | Paid whether or not a matching resource runs; see the products below                                                                                                                                                                                                                                                                                                                                                                                                        |
| Spot and preemptible        | Uses spare capacity at a lower price          | Capacity can be taken back: [AWS](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/spot-instance-termination-notices.html) warns two minutes before a stop or termination, [Azure](https://learn.microsoft.com/en-us/azure/virtual-machines/spot-vms) offers best-effort notice up to 30 seconds ahead and no SLA, and [Google Cloud](https://docs.cloud.google.com/compute/docs/instances/spot) can preempt "at any time"                                               |
| Data transfer               | Removes avoidable per-GB charges              | [AWS](https://aws.amazon.com/blogs/architecture/overview-of-data-transfer-costs-for-common-architectures/) charges for cross-AZ and cross-Region transfer and per GB through a NAT gateway. Same-AZ transfer is free, so keeping chatty services in one AZ saves money but gives up multi-AZ availability                                                                                                                                                                   |
| Architecture                | Changes the design: managed services, caching | "Value and cost efficiency is best achieved by architecting it into a system's design", per the [Foundation](https://www.finops.org/framework/capabilities/architecting-workload-placement/). [Infracost](https://github.com/infracost/infracost) shows estimates before changes are deployed                                                                                                                                                                               |

Table formats keep old data until you remove it: [Iceberg snapshots accumulate until they are expired](https://iceberg.apache.org/docs/latest/maintenance/), as our [Apache Iceberg](https://computese.com/apache-iceberg/) guide shows. Serverless can cost more than a container at a steady load, which our [serverless computing](https://computese.com/the-future-of-serverless-computing-streamlining/) guide works through. Resilience is a cost decision too: our [RTO vs RPO](https://computese.com/rto-vs-rpo/) guide matches standby capacity to each system's recovery targets.

A commitment discount is not a resource. The Foundation compares it to a coupon: "If no resource is running which matches the type of the commitment, the organization still pays for the resource." The products differ in how much you can undo:

- **AWS [Savings Plans](https://docs.aws.amazon.com/savingsplans/latest/userguide/what-is-savings-plans.html)** commit you to an amount of compute, measured per hour, for one or three years. A plan with an hourly commitment of $100 or less can be [returned](https://docs.aws.amazon.com/savingsplans/latest/userguide/return-sp.html) if it was bought in the last seven days and in the same calendar month, within your return limit.
- **Azure [reservations](https://learn.microsoft.com/en-us/azure/cost-management-billing/reservations/save-compute-costs-reservations)** can be exchanged for another reservation of the same type, or refunded up to $50,000 USD in a 12-month rolling window. An [Azure savings plan](https://learn.microsoft.com/en-us/azure/cost-management-billing/savings-plan/savings-plan-overview) is a fixed dollar amount per hour, unused commitment for an hour expires, and purchases cannot be cancelled or refunded.
- **Google Cloud [committed use discounts](https://docs.cloud.google.com/docs/cuds)** are spend-based or resource-based commitments for one or three years.

![Twelve equal boxes each stand for one committed hour. Grey usage fills two boxes to the top and the other ten only partway, and the unused space above the grey, up to the top of each box, is orange.](https://computese.com/images/blog/finops/commitment-gap.e8bd75128c-1536.webp)

*A commitment is paid whether or not usage fills it, so the space above usage is paid for and unused.*

Buy in stages. The Foundation's KPIs include commitments that return more than 10% on the investment, break even within 9 months, and are spread over the year so that some are always expiring.

## How do unit economics, budgets and anomaly alerts fit in?

[Unit economics](https://www.finops.org/framework/capabilities/unit-economics/) ties technology cost to business outcomes. The Foundation's examples include cost per transaction, per customer, per case resolved, per GB stored and per token.

A worked example with made-up numbers: an orders service has an allocated cost, shared costs included, of $18,400 in March for 230,000 orders, or $0.08 per order. In April it costs $19,500 for 310,000 orders, or about $0.063 per order. Spend rose 6% while the cost per order fell 21%, which the total alone would hide.

AWS and Azure alerts run on delayed data. [AWS Budgets](https://docs.aws.amazon.com/cost-management/latest/userguide/budgets-managing-costs.html) is "updated up to three times a day", typically 8 to 12 hours after the previous update. Azure cost data is typically available within 8 to 24 hours and [budgets are evaluated every 24 hours](https://learn.microsoft.com/en-us/azure/cost-management-billing/costs/tutorial-acm-create-budgets). An anomaly, in the Foundation's [definition](https://www.finops.org/framework/capabilities/anomaly-management/), is spending "different (usually higher) than normal historical or expected spend". [AWS Cost Anomaly Detection](https://docs.aws.amazon.com/cost-management/latest/userguide/manage-ad.html) runs approximately three times a day and can take up to 24 hours to detect an anomaly after usage occurs; a new service subscription needs 10 days of history first.

![A rising row of grey bars crosses a dashed threshold line while an orange bell above it rings. A road barrier beside the path stands with its arm pointing straight up, so the way stays open.](https://computese.com/images/blog/finops/budget-alert-no-brake.a061a182f7-1536.webp)

*An alert reports that spend crossed a line; by default it does not stop the spend.*

> [!WARNING]
> Budgets report; they stop nothing unless you set them up to. Azure says "Resources aren't affected, and your consumption isn't stopped", and [Google](https://docs.cloud.google.com/billing/docs/how-to/budgets) says an alerts-only budget "doesn't automatically cap" usage or spending. AWS Budgets can run an action if you configure one, such as applying a custom IAM policy that denies new provisioning, and Google Cloud offers project-level spend cap budgets for supported services. Use a hard limit where one mistake could burn a month of budget.

## Which FinOps mistakes should you avoid?

| Mistake                                     | Why it hurts                                                                                                   | Instead                                                              |
| ------------------------------------------- | -------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------- |
| Tag debt                                    | Ownership is "reconstructed later through tagging cleanup"                                                     | Enforce required keys at creation and report coverage by cost        |
| Optimizing before allocating                | Savings have no owner, and rightsizing and commitment advice can double count                                  | Reach the Crawl goal of 70% allocated, then keep one ranked backlog  |
| Commitments bought too early or all at once | They are paid whether or not a matching resource runs, and Azure savings plans cannot be cancelled or refunded | Buy in stages against steady usage and watch utilization             |
| Savings nobody books                        | A saving that never reaches the forecast or budget is absorbed by growth                                       | Record expected savings per item, name an owner, update the forecast |

## What does a 90-day FinOps plan look like?

This sequence is ours, not part of the Framework. Each step names an owner and a check.

1. **Days 1 to 15: owners and data.** Name an owner and a cost center for every account, subscription and project. Turn on billing exports (FOCUS where offered), activate cost allocation tags on AWS and enable tag inheritance on Azure. Owner: FinOps lead. Check: last month's export loads into a warehouse and ties to the invoice.
2. **Days 16 to 30: policy and first showback.** Publish the four-key tagging policy and run the coverage query. Owner: FinOps lead and engineering leads. Check: at least 70% of cost allocated to a known owner, the Foundation's sample Crawl goal.
3. **Days 31 to 45: switch off and expire.** Schedule non-production environments and add storage lifecycle rules. Owner: engineering owners. Check: non-production resources start and stop on a schedule, and expired data is deleted.
4. **Days 46 to 60: backlog and commitments.** Rank rightsizing items by savings against effort and risk, then buy a first commitment on steady usage. Owner: engineering, finance and procurement. Check: each item has an owner, an estimate and a date, and utilization is tracked daily.
5. **Days 61 to 75: enforce and alert.** Turn on tag policy checks in code, then budgets and anomaly alerts for each owner. Owner: platform engineering. Check: a plan with a missing required key fails, and a test alert reaches the owner.
6. **Days 76 to 90: one unit cost and the first review.** Pick a business measure such as orders or tenants and report cost per unit as a trend. Owner: product, finance and the FinOps lead. Check: the review happens, and booked savings appear in the forecast.

Computese's [cloud transformation service](https://computese.com/services/cloud-transformation/) puts tagging, budgets and guardrails in place from the first day and runs FinOps reviews that tie spend to value, with tools such as AWS Cost Explorer, Azure Cost Management, Kubecost, OpenCost and Infracost.

## Key terms
- **FinOps**: An operational framework and cultural practice that maximizes the business value of technology, enables timely data-driven decision making and creates financial accountability through collaboration between engineering, finance and business teams.
- **FOCUS**: The FinOps Open Cost and Usage Specification: an open specification that defines requirements for technology billing data generators to produce consistent datasets. FOCUS 1.4 was ratified on June 4, 2026.
- **Showback**: Reporting that shows any group, large or small, the costs of the scope it is responsible for. The FinOps Foundation says showback is always required in any FinOps practice, unlike chargeback.
- **Chargeback**: The formal step of sending technology expenses to official accounting budgets. The FinOps Foundation says it depends on organizational accounting policies and is not always required.
- **Cost allocation tag**: On AWS, a tag key you activate in the Billing and Cost Management console so that it appears on your billing reports. Activating or deactivating a key affects every value that shares it.
- **Commitment discount**: A discount in exchange for committing to usage or spend, such as AWS Savings Plans, Azure reservations and Google Cloud committed use discounts. The Foundation compares it to a coupon: it is not a resource.
- **Usage and rate optimization**: Options the Foundation names in the Optimize phase. Usage optimization means using fewer resources to achieve an acceptable outcome. Rate optimization means paying an appropriate amount for the resources you must use.
- **Unit economics**: A way to tie technology cost to business outcomes by tracking it per unit, such as per transaction, per customer or per case resolved.
- **Cluster idle cost**: In the OpenCost specification, the portion of resource allocation costs that is not allocated to any workload.

## Common questions

### What is FinOps?

FinOps is, in the FinOps Foundation's definition, an operational framework and cultural practice that maximizes the business value of technology, enables timely data-driven decision making and creates financial accountability through collaboration between engineering, finance and business teams. The name is a portmanteau of Finance and DevOps. The Foundation writes that if FinOps seems to be about saving money, think again.

### What are the phases of FinOps?

The Framework has three phases, Inform, Optimize and Operate, which teams work through iteratively. In Inform you examine cost, usage and efficiency data. In Optimize you identify and document options, and in Operate you implement the changes and loop back to the earlier phases.

### How is FinOps different from cloud cost optimization?

Optimization is one phase of FinOps, and it comes after Inform, where cost, usage and efficiency data are examined. The Optimize phase covers usage optimization, which uses fewer resources, and rate optimization, which pays an appropriate amount for the resources you must use. The Foundation also warns that waiting for fully optimized usage before rate optimization will almost always lead to paying more than a balanced approach.

### What is the difference between showback and chargeback?

The FinOps Foundation says the primary difference is formality: chargeback sends expenses to official accounting budgets, while showback shows any group the costs of its scope. It adds that showback is always required in any FinOps practice, but chargeback depends on organizational accounting policies.

### What is FOCUS?

FOCUS, the FinOps Open Cost and Usage Specification, is an open specification that defines requirements for billing data generators to produce consistent datasets. FOCUS 1.4 was ratified on June 4, 2026. As of October 2026, AWS Data Exports offers FOCUS 1.0 or 1.2, Azure lists 1.2-preview and Google Cloud's BigQuery export is a Preview.

### How do you allocate Kubernetes costs?

Decide how to price the gap between what a Pod requests and what it uses, then apply one rule to every team. GKE cost allocation is based on resource requests, AWS lets you choose requests or the higher of requests and utilization for EKS, and the OpenCost specification says workload cost should be understood as max(request, usage).

## Sources
1. [What is FinOps?](https://www.finops.org/introduction/what-is-finops/), FinOps Foundation
2. [FinOps Framework overview](https://www.finops.org/framework/), FinOps Foundation
3. [FinOps Principles](https://www.finops.org/framework/principles/), FinOps Foundation
4. [FinOps Phases](https://www.finops.org/framework/phases/), FinOps Foundation
5. [FinOps Domains](https://www.finops.org/framework/domains/), FinOps Foundation
6. [FinOps Personas](https://www.finops.org/framework/personas/), FinOps Foundation
7. [FinOps Scopes](https://www.finops.org/framework/scopes/), FinOps Foundation
8. [FinOps Maturity Model](https://www.finops.org/framework/maturity-model/), FinOps Foundation
9. [FinOps Framework 2026: Executive Strategy, Technology Categories, and Converging Disciplines](https://www.finops.org/insights/2026-finops-framework/), FinOps Foundation
10. [Allocation (FinOps Framework Capability)](https://www.finops.org/framework/capabilities/allocation/), FinOps Foundation
11. [Tag policies (AWS Organizations)](https://docs.aws.amazon.com/organizations/latest/userguide/orgs_manage_policies_tag-policies.html), Amazon Web Services
12. [Labels overview (Resource Manager)](https://docs.cloud.google.com/resource-manager/docs/labels-overview), Google Cloud
13. [Enforce required tag keys with IaC (AWS Organizations)](https://docs.aws.amazon.com/organizations/latest/userguide/enforce-required-tag-keys-iac.html), Amazon Web Services
14. [Implement AWS resource tagging strategy using AWS Tag Policies and Service Control Policies (SCPs)](https://aws.amazon.com/blogs/mt/implement-aws-resource-tagging-strategy-using-aws-tag-policies-and-service-control-policies-scps/), AWS Management & Governance Blog
15. [Policy definitions for tagging resources (Azure Resource Manager)](https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/tag-policies), Microsoft Learn
16. [Activating user-defined cost allocation tags (AWS Billing)](https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/activating-tags.html), Amazon Web Services
17. [Using user-defined cost allocation tags (AWS Billing)](https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/custom-tags.html), Amazon Web Services
18. [Group and allocate costs using tag inheritance (Microsoft Cost Management)](https://learn.microsoft.com/en-us/azure/cost-management-billing/costs/enable-tag-inheritance), Microsoft Learn
19. [Tag policy syntax and examples (AWS Organizations)](https://docs.aws.amazon.com/organizations/latest/userguide/orgs_manage_policies_example-tag-policies.html), Amazon Web Services
20. [Tag Policy Compliance (Terraform AWS provider guide)](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/guides/tag-policy-compliance), HashiCorp Terraform Registry
21. [Splitting charges within cost categories (AWS Billing)](https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/splitcharge-cost-categories.html), Amazon Web Services
22. [Allocate Azure costs (Microsoft Cost Management)](https://learn.microsoft.com/en-us/azure/cost-management-billing/costs/allocate-costs), Microsoft Learn
23. [Invoicing & Chargeback (FinOps Framework Capability)](https://www.finops.org/framework/capabilities/invoicing-chargeback/), FinOps Foundation
24. [What is FOCUS?](https://focus.finops.org/what-is-focus/), FinOps Foundation (FOCUS)
25. [FOCUS Specification 1.4](https://focus.finops.org/docs/specification/v1-4/), FinOps Foundation (FOCUS)
26. [What is AWS Data Exports?](https://docs.aws.amazon.com/cur/latest/userguide/what-is-data-exports.html), Amazon Web Services
27. [Data Exports for FOCUS 1.2 is now generally available](https://aws.amazon.com/blogs/aws-cloud-financial-management/data-exports-for-focus-1-2-is-now-generally-available/), AWS Cloud Financial Management Blog
28. [Cost Management dataset schema index](https://learn.microsoft.com/en-us/azure/cost-management-billing/dataset-schema/schema-index), Microsoft Learn
29. [Structure of FOCUS data export (Cloud Billing)](https://docs.cloud.google.com/billing/docs/how-to/export-data-bigquery-tables/focus-export), Google Cloud
30. [Billed Cost (FOCUS Specification 1.4)](https://focus.finops.org/docs/specification/v1-4/columns/cost-and-usage/billed-cost/), FinOps Foundation (FOCUS)
31. [Effective Cost (FOCUS Specification 1.4)](https://focus.finops.org/docs/specification/v1-4/columns/cost-and-usage/effective-cost/), FinOps Foundation (FOCUS)
32. [Tags (FOCUS Specification 1.4)](https://focus.finops.org/docs/specification/v1-4/columns/cost-and-usage/tags/), FinOps Foundation (FOCUS)
33. [Analyze tag coverage (FOCUS use cases, version 1.4)](https://focus.finops.org/docs/use-cases/v1-4/analyze-tag-coverage/), FinOps Foundation (FOCUS)
34. [JSON Functions and Operators (PostgreSQL 18)](https://www.postgresql.org/docs/current/functions-json.html), PostgreSQL Documentation
35. [Conditional Expressions (PostgreSQL 18)](https://www.postgresql.org/docs/current/functions-conditional.html), PostgreSQL Documentation
36. [Resource Management for Pods and Containers](https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/), Kubernetes
37. [Get key spending insights for your GKE resource allocation and cluster costs](https://docs.cloud.google.com/kubernetes-engine/docs/how-to/cost-allocations), Google Cloud
38. [Enabling split cost allocation data (AWS Data Exports)](https://docs.aws.amazon.com/cur/latest/userguide/enabling-split-cost-allocation-data.html), Amazon Web Services
39. [OpenCost Specification](https://opencost.io/docs/specification/), OpenCost
40. [OpenCost (CNCF project page)](https://www.cncf.io/projects/opencost/), Cloud Native Computing Foundation
41. [Rate Optimization (FinOps Framework Capability)](https://www.finops.org/framework/capabilities/rate-optimization/), FinOps Foundation
42. [Usage Optimization (FinOps Framework Capability)](https://www.finops.org/framework/capabilities/usage-optimization/), FinOps Foundation
43. [Metrics analyzed by AWS Compute Optimizer](https://docs.aws.amazon.com/compute-optimizer/latest/ug/metrics.html), Amazon Web Services
44. [Access tiers for blob data (Azure Storage)](https://learn.microsoft.com/en-us/azure/storage/blobs/access-tiers-overview), Microsoft Learn
45. [Storage classes (Cloud Storage)](https://docs.cloud.google.com/storage/docs/storage-classes), Google Cloud
46. [Transitioning objects using Amazon S3 Lifecycle](https://docs.aws.amazon.com/AmazonS3/latest/userguide/lifecycle-transition-general-considerations.html), Amazon Web Services
47. [Spot Instance interruption notices (Amazon EC2)](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/spot-instance-termination-notices.html), Amazon Web Services
48. [About Azure Spot Virtual Machines](https://learn.microsoft.com/en-us/azure/virtual-machines/spot-vms), Microsoft Learn
49. [Spot VMs (Compute Engine)](https://docs.cloud.google.com/compute/docs/instances/spot), Google Cloud
50. [Overview of Data Transfer Costs for Common Architectures](https://aws.amazon.com/blogs/architecture/overview-of-data-transfer-costs-for-common-architectures/), AWS Architecture Blog
51. [Architecting & Workload Placement (FinOps Framework Capability)](https://www.finops.org/framework/capabilities/architecting-workload-placement/), FinOps Foundation
52. [Infracost (GitHub repository)](https://github.com/infracost/infracost), Infracost
53. [Maintenance (Apache Iceberg documentation)](https://iceberg.apache.org/docs/latest/maintenance/), Apache Iceberg
54. [What are Savings Plans?](https://docs.aws.amazon.com/savingsplans/latest/userguide/what-is-savings-plans.html), Amazon Web Services
55. [Returning a purchased Savings Plan](https://docs.aws.amazon.com/savingsplans/latest/userguide/return-sp.html), Amazon Web Services
56. [What are Azure Reservations?](https://learn.microsoft.com/en-us/azure/cost-management-billing/reservations/save-compute-costs-reservations), Microsoft Learn
57. [What are savings plans? (Microsoft Cost Management)](https://learn.microsoft.com/en-us/azure/cost-management-billing/savings-plan/savings-plan-overview), Microsoft Learn
58. [Committed use discounts (Google Cloud)](https://docs.cloud.google.com/docs/cuds), Google Cloud
59. [Capability: Unit Economics (FinOps Framework)](https://www.finops.org/framework/capabilities/unit-economics/), FinOps Foundation
60. [Managing your costs with AWS Budgets](https://docs.aws.amazon.com/cost-management/latest/userguide/budgets-managing-costs.html), Amazon Web Services
61. [Tutorial: Create and manage budgets (Microsoft Cost Management)](https://learn.microsoft.com/en-us/azure/cost-management-billing/costs/tutorial-acm-create-budgets), Microsoft Learn
62. [Anomaly Management (FinOps Framework Capability)](https://www.finops.org/framework/capabilities/anomaly-management/), FinOps Foundation
63. [Detecting unusual spend with AWS Cost Anomaly Detection](https://docs.aws.amazon.com/cost-management/latest/userguide/manage-ad.html), Amazon Web Services
64. [Create, edit, or delete budgets and budget alerts (Cloud Billing)](https://docs.cloud.google.com/billing/docs/how-to/budgets), Google Cloud
