April 7, 2026

Back

FOCUS (FinOps Open Cost and Usage Specification): The Complete Guide for 2026

8 min read

Cloud billing is a mess. FOCUS is here to clean it up.

If you've ever tried to compare cloud costs across AWS, Azure, and Google Cloud in a single spreadsheet, you already know the pain. Every provider speaks a different language.

AWS gives you a Cost and Usage Report (CUR) with hundreds of cryptically named columns. Azure exports a completely different CSV with its own schema. GCP pipes data into BigQuery in yet another format. And you're left writing custom ETL pipelines, arguing about what "cost" even means, and wondering why FinOps is supposed to be easy.

That's exactly the problem that FOCUS (FinOps Open Cost and Usage Specification) was built to solve. And in 2026, it's no longer a promising idea on a whiteboard. It's a production-ready standard that's reshaping how enterprises manage cloud spend.

Let's break it all down.

What is FOCUS, exactly?

FOCUS is an open standard for cloud cost and usage data developed and maintained by the FinOps Foundation. Think of it as a universal language for cloud billing. Instead of every cloud provider inventing its own schema, FOCUS defines a shared, vendor-neutral format that any provider can implement.

The goal is simple: you should be able to drop AWS, Azure, and GCP cost data into the same tool, with the same column names, and get meaningful insights without writing a line of transformation code.

FOCUS is not a product. It's not a tool you buy. It's a specification, like HTML or JSON. Any provider can support it, any tool can consume it, and you own your data throughout.

The FinOps Foundation (the same organization that defined the FinOps framework and runs the FinOps Certified Practitioner program) governs the spec through an open working group that includes contributors from major cloud providers, tool vendors, and enterprise FinOps teams.

The Version Story: Where FOCUS Stands in 2026

FOCUS v1.0 was the landmark stable release that made the spec production-ready and gave cloud providers a concrete target to implement. But the project has moved fast since then.

FOCUS 1.1 (ratified November 2024) added deeper support for cloud provider billing data, enabling more granular multi-cloud analysis and improving the metadata that powers ETL pipelines.

FOCUS 1.2 (ratified May 2025) was a major leap forward. It expanded FOCUS beyond pure cloud billing to cover SaaS and PaaS in a single unified schema, meaning one dashboard or SQL query can now cover your entire technology spend. It also introduced multi-currency normalization and invoice reconciliation capabilities, making chargeback and P&L reporting dramatically more reliable.

FOCUS 1.3 (ratified December 2025) is the current version and it delivers some of the most requested enterprise features yet. A new dedicated Contract Commitment dataset lets practitioners track active commitments, start and end dates, and remaining units in one place. New allocation columns expose exactly how shared costs are split across workloads, not just the output but the methodology. And providers must now timestamp datasets and flag completeness status, so you always know whether the data you're looking at is final or still subject to revision.

The versioning model is semantic and the working group has prioritized backward compatibility throughout. Nobody wants to rebuild a data warehouse every time a spec bumps a version, and FOCUS has held to that commitment.

Also read: Stages of Adopting FinOps FOCUS™

The Schema: What FOCUS Actually Looks Like

At its core, FOCUS is a set of well-defined columns that every provider must populate in a standardized way. The schema is organized around a few key areas that matter most to FinOps practitioners.

Cost Columns are arguably the most impactful part of the spec. FOCUS clearly distinguishes between BilledCost (what actually appears on your invoice) and EffectiveCost (what you actually paid after discounts, Reserved Instances, and Savings Plans are applied). Before FOCUS, every provider calculated and named these differently, which made multi-cloud cost comparison nearly impossible. Having a shared, precise definition for each cost type is one of the spec's most immediate practical wins.

Resource and Service Fields standardize how cloud resources are identified and categorized. This includes fields for resource identifiers, human-readable names, service names, and higher-level service categories that map services into logical buckets like Compute, Storage, Database, and Networking. That means EC2, Azure Virtual Machines, and GCP Compute Engine all roll up under the same category, making cross-provider analysis genuinely apples-to-apples.

Time and Billing Fields align billing periods and usage timestamps across providers so you can compare costs within the same time window without manual adjustments.

Commitment and Discount Fields capture the nuances of Reserved Instances, Savings Plans, and committed use discounts in a standardized way, so your optimization analysis works the same regardless of which provider the commitment lives on.

What 1.2 and 1.3 Added: FOCUS 1.2 introduced allocation methodology columns that expose how shared costs are split across workloads, multi-currency normalization fields with auditable exchange rates, and invoice ID associations for every charge or credit. FOCUS 1.3 added ServiceProvider and HostProvider columns, which let you distinguish between the entity making a service available for purchase and the underlying provider it actually runs on. This is especially useful for reseller and marketplace scenarios. FOCUS 1.3 also introduced data recency and completeness metadata so you always know whether a dataset is final or still subject to revision.

The full column reference with exact field names, data types, and mandatory vs. optional status is published openly at focus.finops.org and the official FOCUS GitHub repository.

Cloud Provider Support: Who's In?

This is where the FOCUS story gets genuinely impressive. All major clouds have been active contributors to the ongoing FOCUS 1.3 specification development, meaning they're not just implementing someone else's standard but helping shape it.

FOCUS is already supported by cloud and technology providers worldwide including Alibaba, AWS, Databricks, Google Cloud, Grafana, Huawei, Microsoft, Oracle Cloud Infrastructure, OVH Cloud, and Tencent. That list spans hyperscalers, regional cloud providers, and major data platform vendors, which signals that FOCUS is becoming a true cross-industry standard rather than a Western hyperscaler-only initiative.

Beyond public cloud, many enterprises are now using FOCUS language in their internal reporting systems and generating FOCUS datasets for their data center and private cloud spending. That's a significant development. It means FOCUS isn't just a tool for comparing AWS vs. Azure. It's becoming the common language for all technology spend, on-premises and cloud alike.

The practical takeaway: if your organization runs workloads across any combination of these platforms, the data you need to normalize costs already exists in FOCUS format or will soon. The bottleneck is no longer provider support. It's your internal pipeline and tooling.

The Competitive Landscape: FOCUS vs. Everything Else

Here's where it gets interesting. FOCUS doesn't compete with cloud providers or third-party tools. It's a standard that everything else plugs into. But understanding how it fits into the existing landscape is essential.

FOCUS vs. AWS CUR

The Cost and Usage Report is the gold standard of AWS billing data. It's detailed, comprehensive, and deeply AWS-specific. FOCUS doesn't replace CUR for AWS-only shops. But for any organization running multi-cloud, FOCUS is far more valuable because it gives you a common schema that makes cross-provider analysis possible.

FOCUS vs. Azure Cost Management

Azure's native cost export is excellent within the Azure ecosystem, but it speaks a completely different schema from CUR. FOCUS bridges that gap. With both providers now offering FOCUS exports, a FinOps analyst can pull from both into a single data model.

Third-Party Tool Landscape

The major FinOps platforms are actively integrating FOCUS support because their customers are demanding it. Tools that drag their feet on FOCUS support are increasingly seen as technical debt.

Newer FinOps tools and startups have a genuine advantage here: they can build FOCUS-first from the ground up instead of retrofitting legacy pipelines. Expect to see this as a major differentiator in vendor pitches through 2026 and beyond.

For container-native environments, Kubernetes cost visibility is a growing challenge. There are active discussions in the FOCUS working group about extensions for container workload attribution. Standardized Kubernetes cost data would dramatically simplify chargeback models for platform teams.

What FOCUS Is NOT Competing With

FOCUS is not a FinOps platform. It doesn't do anomaly detection, optimization recommendations, or budget alerting. It's the data layer that makes those capabilities possible across providers. Think of it as the foundation, not the house.

Why FOCUS Matters for Your Organization Right Now

Let's get practical. Here's why your team should care about FOCUS in 2026.

You're almost certainly multi-cloud. Most enterprises of any significant size are running workloads on at least two cloud providers, even if that wasn't a deliberate strategic choice. FOCUS is the single most impactful thing you can do to make that multi-cloud reality governable.

ETL is costing you money. If your FinOps team spends time writing and maintaining transformation pipelines to normalize AWS, Azure, and GCP billing data, FOCUS eliminates much of that work. That's engineering time that can go toward actual optimization.

Vendor lock-in is real. If your cost management tool speaks only one proprietary format, you're locked in. FOCUS-standardized data means you can switch tools without migrating your entire data model. That leverage matters in contract negotiations.

Showback and chargeback get easier. When your cost allocation model is built on a standardized schema, finance teams can trust the numbers. EffectiveCost means the same thing whether it came from AWS or Azure. That consistency builds organizational confidence in FinOps data.

Sustainability is coming to the spec. As enterprises face pressure to report on carbon emissions tied to cloud workloads, there are active efforts to incorporate carbon and sustainability data into future FOCUS releases. Building your data pipeline on FOCUS now means you're ready when that arrives.

How to Get Started with FOCUS

Getting started is more accessible than you might think.

Step 1:

Enable FOCUS exports from your cloud providers. Both AWS and Azure have documentation on how to configure FOCUS-format cost and usage exports. This is a configuration change, not an engineering project.

Step 2:

Audit your existing tooling. Check whether your FinOps platform already supports FOCUS ingestion. If it doesn't, ask your vendor for their roadmap. A vendor without a clear FOCUS strategy in 2026 is a yellow flag.

Step 3:

Normalize your data model. Start mapping your internal cost allocation taxonomy to FOCUS fields. Even if you don't flip entirely to FOCUS overnight, understanding how your current data maps to ServiceCategory, ChargeType, and CommitmentDiscountStatus will improve your FinOps practice.

Step 4:

Think beyond cloud. With FOCUS 1.2 and 1.3 supporting SaaS, PaaS, and even private cloud datasets, now is the time to evaluate whether your internal data center reporting can adopt FOCUS language too. Many enterprises already are.

Step 5:

Get involved. The FOCUS spec is open. The working group is open to FinOps Foundation members and community feedback directly shapes the spec. If your organization has edge cases that the current spec doesn't handle, that's a contribution opportunity.

The Bottom Line

The cloud industry has needed a billing standard for years. FOCUS is that standard, and in 2026, it's no longer aspirational. It has real production support from the hyperscalers, growing tool ecosystem adoption, and a working group that's actively evolving the spec to meet real enterprise needs.

Whether you're a FinOps analyst drowning in custom ETL, an IT leader trying to get a handle on multi-cloud costs, a developer who wants billing data that makes sense, or a CFO signing off on a cloud budget you can't fully explain, FOCUS is the foundation that makes cloud cost management sustainable at scale.

The question isn't whether FOCUS will become the de facto standard for cloud cost data. It already is. The question is how quickly your organization gets on board.

[Request a demo and speak to our team]
[Sign up for a no-cost 30-day trial]
[Check out our free resources on FinOps]
[Try Amnic AI Agents today]

FAQs: FOCUS in 2026

1. What is FOCUS and who created it?

FOCUS stands for FinOps Open Cost and Usage Specification. It is an open standard created and maintained by the FinOps Foundation, a vendor-neutral organization dedicated to cloud financial management best practices. The spec was built with contributions from major cloud providers, tool vendors, and enterprise FinOps practitioners to solve the long-standing problem of incompatible billing formats across cloud providers.

2. Do I need to replace my existing cloud billing tools to use FOCUS?

No. FOCUS is a data standard, not a product or platform. Most major cloud providers now offer FOCUS-format exports alongside their existing billing reports. You can adopt FOCUS incrementally by enabling the export option from your cloud provider and updating your data pipelines, without throwing out your existing tooling overnight.

3. Which cloud providers currently support FOCUS?

AWS, Microsoft Azure, Google Cloud Platform, and Oracle Cloud Infrastructure all support or are actively rolling out FOCUS-compatible exports. AWS and Azure in particular have production-ready FOCUS export options available today, making multi-cloud cost normalization more accessible than ever.

4. What is the difference between BilledCost and EffectiveCost in FOCUS?

BilledCost is the raw amount that appears on your cloud invoice, before any discounts or commitments are factored in. EffectiveCost is what you actually paid after applying Reserved Instances, Savings Plans, or other commitment-based discounts. One of FOCUS's biggest wins is standardizing this distinction across all providers, so these terms mean exactly the same thing whether you're looking at AWS or Azure data.

5. Is FOCUS only relevant for large enterprises running multi-cloud?

Not at all. While multi-cloud organizations see the most immediate impact, even single-cloud teams benefit from FOCUS. The standardized schema makes it easier to switch cost management tools without rebuilding your data model, simplifies chargeback and showback reporting, and future-proofs your data strategy as your cloud footprint grows. Getting on FOCUS now means you are ready when your organization expands to a second provider.