What is the FOCUS open cost and usage specification and how does it simplify multi cloud reporting?

FOCUS the FinOps Open Cost and Usage Specification is an open technical standard maintained by the FinOps Foundation that defines a vendor-neutral schema for cloud billing and usage data. Its purpose is to make cost and usage records from AWS, Azure, GCP, and other technology vendors use the same column names, the same cost definitions, and the same data semantics so FinOps teams can analyze multi-cloud spend without building and maintaining separate data pipelines for each provider. FOCUS is not a product or a tool. It is a specification, in the same way HTML defines how web content is structured, and any provider or platform can implement it.

The problem FOCUS was built to solve

Before FOCUS, multi cloud cost reporting required significant and ongoing engineering investment that had nothing to do with optimization. Every cloud provider invented its own billing schema:

• AWS produced Cost and Usage Reports with hundreds of cryptically named columns using terminology like “lineItem/UnblendedCost” that had no equivalent in other providers.
• Azure exported CSVs using terms like “MeterName” and “PreTaxCost” that mapped only partially to AWS concepts.
• GCP piped billing data into BigQuery with its own schema where compute was denominated differently from the other two providers entirely.

Answering a question as simple as “how much are we spending on compute across all three clouds this month” required three separate ETL pipelines, a manual terminology mapping table, and ongoing maintenance every time a provider changed their billing format. FinOps teams spent a disproportionate share of their capacity on data normalization rather than cost optimization and the normalized output was still unreliable because the mapping decisions were subjective. For organizations running the multi-cloud cost management programs that modern FinOps requires, this data fragmentation was the single biggest structural barrier to unified reporting.

How FOCUS solves it

FOCUS defines 65 standardized columns grouped into categories that every participating provider must populate consistently. The most impactful area is cost columns, where FOCUS introduces a precise and universal distinction that previously did not exist across providers:

• BilledCost: the exact amount that appears on the provider invoice before any amortization.
• EffectiveCost: the actual cost after applying discounts, Reserved Instances, Savings Plans, and Committed Use Discounts.

Before FOCUS, every provider calculated and named these differently, making true multi-cloud cost comparison practically impossible. FOCUS also standardizes resource and service fields resource identifiers, service names, and higher level service categories that map every provider’s services into consistent buckets: Compute, Storage, Database, and Networking.

A single SQL query against a FOCUS-formatted dataset works identically across AWS, Azure, and GCP without any schema translation. Microsoft confirmed that FOCUS combines actual and amortized costs in a single row, producing 49% fewer rows and approximately 30% smaller total data size compared to maintaining separate actual and amortized datasets, a direct reduction in both storage and compute costs for the analytics pipeline itself.

FOCUS version history and current state

FOCUS 1.0 – November 2023

The first stable release covering cloud billing data from AWS, Azure, GCP, and Oracle Cloud. Made the spec production-ready and gave cloud providers a concrete implementation target.

FOCUS 1.1 – 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 – May 2025

The most significant expansion to date. Extended FOCUS beyond cloud billing to cover SaaS and PaaS in a single unified schema, meaning one dashboard or SQL query now covers an organization’s entire technology spend including Snowflake, Datadog, and other SaaS tools alongside cloud infrastructure.

FOCUS 1.3 – December 2025

The current version. Introduced a dedicated Contract Commitment dataset that tracks active commitments, start and end dates, and remaining units in one place. Added new allocation columns that expose exactly how shared costs are split across workloads, not just the output but the methodology. Providers must now timestamp datasets and flag completeness status so teams always know whether the data they are looking at is final or subject to revision.

What FOCUS enables that was not possible before

Beyond data normalization, FOCUS unlocks four specific FinOps capabilities that multi-cloud teams previously could not achieve reliably:

• Cross-cloud commitment comparison: because EffectiveCost is defined identically across providers, teams can now calculate their effective savings rate from Reserved Instances, Savings Plans, and CUDs in a single report without provider-specific adjustments.
• Portable FinOps tooling: any platform that ingests FOCUS-formatted data works across all FOCUS-compatible providers without custom integrations, meaning switching or adding a provider does not require rebuilding the analytics stack.
• Consistent unit economics: cost-per-x metrics such as cost per GB stored, cost per API call, or cost per customer can now be calculated consistently across providers using the same column definitions.
• New hire onboarding speed: FinOps practitioners who learn FOCUS terminology are immediately productive regardless of which cloud providers the organization uses, reducing provider-specific billing education overhead.

Where FOCUS still has gaps

FOCUS adoption is not yet universal. Some providers offer partial FOCUS support or export FOCUS-formatted data alongside their legacy billing schemas rather than replacing them. The Contract Commitment dataset introduced in FOCUS 1.3 is new and not yet widely supported across all tooling platforms. And while FOCUS 1.2 added SaaS coverage, the depth of SaaS billing normalization varies significantly by vendor. Organizations evaluating FinOps platforms should treat native FOCUS support as a baseline requirement but verify specific provider coverage rather than assuming complete implementation across every service.

How Usage.ai relates to FOCUS standardized environments

Usage.ai operates at the commitment management layer, the function that FOCUS 1.3 specifically expanded with its new Contract Commitment dataset. As FOCUS adoption makes commitment data more structured and portable across providers, Usage.ai’s autonomous Autopilot benefits directly: standardized commitment data enables more accurate real-time analysis of coverage gaps and utilization rates across AWS, Azure, and GCP simultaneously. Its multi-org reporting outputs align with FOCUS cost column definitions, making savings attribution directly comparable to provider billing exports. For teams building the data foundation that FOCUS enables, understanding how cloud cost optimization actually works beyond dashboards is essential context.

Bottom line

FOCUS is the most structurally important development in multi-cloud FinOps in the past five years because it eliminates the data normalization problem that has historically consumed a disproportionate share of FinOps team capacity. Organizations that adopt FOCUS formatted billing exports and use platforms that ingest FOCUS natively will spend less time cleaning data and more time optimizing it. The current version, FOCUS 1.3, extends this advantage to commitment tracking, shared cost allocation, and SaaS spend making it the foundation for a unified technology cost management practice rather than a cloud-specific one.