Skip to main content

CNCF Releases FinOps Open Cost and Usage Specification (FOCUS) 1.0

The FinOps Foundation, a part of The Linux Foundation's non-profit technology consortium focused on advancing the people and practice of FinOps, announced the General Availability (GA) of the FinOps Open Cost and Usage Specification (FOCUS) Version 1.0.

By creating a uniform format for cloud bills across different cloud providers, FOCUS reduces complexity for FinOps practitioners and eases adoption of cloud infrastructure and software.

All of the leading cloud providers, including Google Cloud, Microsoft Azure, Amazon Web Services, Inc. (AWS), and Oracle Cloud, have all formally contributed to the development of Version 1.0. FOCUS boasts a Steering Committee with voting members from leading cloud providers as well as practitioners from some of the largest and most advanced cloud users in the world.

Today, the specification's 1.0 release is ready for general adoption having passed through a rigorous approval and IP review process. In the coming months, the Foundation expects to see improving data exports from billing generators such as the clouds, platforms, private cloud, and SaaS providers.

While this is an early major milestone in the FOCUS journey, the specification is just getting started. As the Use Case Library expands, FOCUS contributors, maintainers and steering committee members are already working on the 1.1 release and planning for the 1.2 release. The depth and quality of the spec will increase over time and the project expects to see billing generators (e.g. the clouds) increase the quality of their FOCUS outputs. As adoption grows, more vendors plan to support FOCUS data ingestion and reporting, adopt FOCUS terminology in their platforms, and align billing data outputs to the requirements in the specification.

Version 1.0 includes common taxonomy, terminology, and metrics for billing datasets produced by cloud infrastructure as a service (IaaS) providers. FOCUS will be extensible to other cloud Software-as-a-Service (SaaS) billing datasets, including networking, observability, and security tools. Future updates are expected to add further support for SaaS providers and on-premises datasets.

"Adopting FOCUS now immediately gives cloud consumers the benefit of normalized cloud spend, plus starts them on a journey with the specification that will allow them to easily add future types of spending as iterative releases improve it. It solves for today's use cases, but it also sets you up for tomorrow's opportunities," said Mike Fuller, CTO at the FinOps Foundation. "We've moved beyond the initial building phase for FOCUS and into the phase where practitioners can use these datasets to perform multi-cloud discount analysis, optimize resource usage, and allocate shared costs. FOCUS makes it easier for organizations to increase value from their cloud investments."

To help realize business value, FinOps practitioners worked with the FinOps Foundation to build a library of over forty common FinOps use cases, each complete with an SQL query that leverages FOCUS columns to answer critical business questions. These use cases offer a standardized approach to extracting answers from billing data and give practitioners time back to work on higher priority FinOps capabilities.

To get to this simple set of columns that makes FOCUS so impactful, thousands of hours of discussion and reviews occurred in an operational structure that allows community inputs, and contains a set of IP protections processes to protect adopters from patent infringement concerns. Getting to consensus on a specification takes time, and deep discussion with product experts from the entire environment of cloud. Some conversations around simple labels and column descriptions are the culminations of hundreds of hours of conversations with dozens of contributors.

"The general availability of the FOCUS 1.0 specification represents not only a pivotal step in IT cost management but also a huge step forward in supporting multicloud strategies in billing disintermediation from any specific vendor environment. This is a BIG deal. All organizations of any size and at any point in their cloud journey and across all industries will benefit immensely. FOCUS 1.0 is the first step in a long journey towards the abstractable, composable cloud. It removes the burden of the multi-skill set knowledge required to manage costs across all of the tools and clouds organizations use to manage and support their IT environment. In doing so, organizations can more easily optimize their cloud investments and drive sustainable financial growth," said Tracy Woo, Forrester Principal Analyst.

Hot Topic

The Latest

80% of respondents agree that the IT role is shifting from operators to orchestrators, according to the 2026 IT Trends Report: The Human Side of Autonomous IT from SolarWinds ...

40% of organizations deploying AI will implement dedicated AI observability tools by 2028 to monitor model performance, bias and outputs, according to Gartner ...

Until AI-powered engineering tools have live visibility of how code behaves at runtime, they cannot be trusted to autonomously ensure reliable systems, according to the State of AI-Powered Engineering Report 2026 report from Lightrun. The report reveals that a major volume of manual work is required when AI-generated code is deployed: 43% of AI-generated code requires manual debugging in production, even after passing QA or staging tests. Furthermore, an average of three manual redeploy cycles are required to verify a single AI-suggested code fix in production ...

Many organizations describe AI as strategic, but they do not manage it strategically. When AI plans are disconnected from strategy, detached from organizational learning, and protected from serious assumptions testing, the problem is no longer technical immaturity; it is a failure of management discipline ... Executives too often tell organizations to "use AI" before they define what AI is supposed to change. The problem deepens in organizations where strategy isn't well articulated in the first place ...

Across the enterprise technology landscape, a quiet crisis is playing out. Organizations have run hundreds, sometimes thousands, of generative AI pilots. Leadership has celebrated the proof of concept (POCs) ... Industry experience points to a sobering reality: only 5-10% of AI POCs that progress to the pilot stage successfully reach scaled production. The remaining 90% fail because the enterprise environment around them was never ready to absorb them, not the AI models ...

Today's modern systems are not what they once were. Organizations now rely on distributed systems, event-driven workflows, hybrid and multi-cloud environments and continuous delivery pipelines. While each adds flexibility, it also introduces new, often invisible failures. Development speed is no longer the primary bottleneck of innovation. Reliability is ...

Seeing is believing, or in this case, seeing is understanding, according to New Relic's 2025 Observability Forecast for Retail and eCommerce report. Retailers who want to provide exceptional customer experiences while improving IT operations efficiency are leaning on observability ... Here are five key takeaways from the report ...

Technology leaders across the federal landscape are facing, and will continue to face, an uphill battle when it comes to fortifying their digital environments against hostile and persistent threat actors. On one hand, they are being asked to push digital transformation ... On the other hand, they are facing the fiscal uncertainty of continuing resolutions (CR) and government shutdowns looming near and far. In the face of these challenges, CIOs, CTOs, and CISOs must figure out how to modernize legacy systems and infrastructure while doing more with less and still defending against external and internal threats ...

Reliability is no longer proven by uptime alone, according to the The SRE Report 2026 from LogicMonitor. In the AI era, it is experienced through speed, consistency, and user trust, and increasingly judged by business impact. As digital services grow more complex and AI systems move into production, traditional monitoring approaches are struggling to keep pace, increasing the need for AI-first observability that spans applications, infrastructure, and the Internet ...

If AI is the engine of a modern organization, then data engineering is the road system beneath it. You can build the most powerful engine in the world, but without paved roads, traffic signals, and bridges that can support its weight, it will stall. In many enterprises, the engine is ready. The roads are not ...

CNCF Releases FinOps Open Cost and Usage Specification (FOCUS) 1.0

The FinOps Foundation, a part of The Linux Foundation's non-profit technology consortium focused on advancing the people and practice of FinOps, announced the General Availability (GA) of the FinOps Open Cost and Usage Specification (FOCUS) Version 1.0.

By creating a uniform format for cloud bills across different cloud providers, FOCUS reduces complexity for FinOps practitioners and eases adoption of cloud infrastructure and software.

All of the leading cloud providers, including Google Cloud, Microsoft Azure, Amazon Web Services, Inc. (AWS), and Oracle Cloud, have all formally contributed to the development of Version 1.0. FOCUS boasts a Steering Committee with voting members from leading cloud providers as well as practitioners from some of the largest and most advanced cloud users in the world.

Today, the specification's 1.0 release is ready for general adoption having passed through a rigorous approval and IP review process. In the coming months, the Foundation expects to see improving data exports from billing generators such as the clouds, platforms, private cloud, and SaaS providers.

While this is an early major milestone in the FOCUS journey, the specification is just getting started. As the Use Case Library expands, FOCUS contributors, maintainers and steering committee members are already working on the 1.1 release and planning for the 1.2 release. The depth and quality of the spec will increase over time and the project expects to see billing generators (e.g. the clouds) increase the quality of their FOCUS outputs. As adoption grows, more vendors plan to support FOCUS data ingestion and reporting, adopt FOCUS terminology in their platforms, and align billing data outputs to the requirements in the specification.

Version 1.0 includes common taxonomy, terminology, and metrics for billing datasets produced by cloud infrastructure as a service (IaaS) providers. FOCUS will be extensible to other cloud Software-as-a-Service (SaaS) billing datasets, including networking, observability, and security tools. Future updates are expected to add further support for SaaS providers and on-premises datasets.

"Adopting FOCUS now immediately gives cloud consumers the benefit of normalized cloud spend, plus starts them on a journey with the specification that will allow them to easily add future types of spending as iterative releases improve it. It solves for today's use cases, but it also sets you up for tomorrow's opportunities," said Mike Fuller, CTO at the FinOps Foundation. "We've moved beyond the initial building phase for FOCUS and into the phase where practitioners can use these datasets to perform multi-cloud discount analysis, optimize resource usage, and allocate shared costs. FOCUS makes it easier for organizations to increase value from their cloud investments."

To help realize business value, FinOps practitioners worked with the FinOps Foundation to build a library of over forty common FinOps use cases, each complete with an SQL query that leverages FOCUS columns to answer critical business questions. These use cases offer a standardized approach to extracting answers from billing data and give practitioners time back to work on higher priority FinOps capabilities.

To get to this simple set of columns that makes FOCUS so impactful, thousands of hours of discussion and reviews occurred in an operational structure that allows community inputs, and contains a set of IP protections processes to protect adopters from patent infringement concerns. Getting to consensus on a specification takes time, and deep discussion with product experts from the entire environment of cloud. Some conversations around simple labels and column descriptions are the culminations of hundreds of hours of conversations with dozens of contributors.

"The general availability of the FOCUS 1.0 specification represents not only a pivotal step in IT cost management but also a huge step forward in supporting multicloud strategies in billing disintermediation from any specific vendor environment. This is a BIG deal. All organizations of any size and at any point in their cloud journey and across all industries will benefit immensely. FOCUS 1.0 is the first step in a long journey towards the abstractable, composable cloud. It removes the burden of the multi-skill set knowledge required to manage costs across all of the tools and clouds organizations use to manage and support their IT environment. In doing so, organizations can more easily optimize their cloud investments and drive sustainable financial growth," said Tracy Woo, Forrester Principal Analyst.

Hot Topic

The Latest

80% of respondents agree that the IT role is shifting from operators to orchestrators, according to the 2026 IT Trends Report: The Human Side of Autonomous IT from SolarWinds ...

40% of organizations deploying AI will implement dedicated AI observability tools by 2028 to monitor model performance, bias and outputs, according to Gartner ...

Until AI-powered engineering tools have live visibility of how code behaves at runtime, they cannot be trusted to autonomously ensure reliable systems, according to the State of AI-Powered Engineering Report 2026 report from Lightrun. The report reveals that a major volume of manual work is required when AI-generated code is deployed: 43% of AI-generated code requires manual debugging in production, even after passing QA or staging tests. Furthermore, an average of three manual redeploy cycles are required to verify a single AI-suggested code fix in production ...

Many organizations describe AI as strategic, but they do not manage it strategically. When AI plans are disconnected from strategy, detached from organizational learning, and protected from serious assumptions testing, the problem is no longer technical immaturity; it is a failure of management discipline ... Executives too often tell organizations to "use AI" before they define what AI is supposed to change. The problem deepens in organizations where strategy isn't well articulated in the first place ...

Across the enterprise technology landscape, a quiet crisis is playing out. Organizations have run hundreds, sometimes thousands, of generative AI pilots. Leadership has celebrated the proof of concept (POCs) ... Industry experience points to a sobering reality: only 5-10% of AI POCs that progress to the pilot stage successfully reach scaled production. The remaining 90% fail because the enterprise environment around them was never ready to absorb them, not the AI models ...

Today's modern systems are not what they once were. Organizations now rely on distributed systems, event-driven workflows, hybrid and multi-cloud environments and continuous delivery pipelines. While each adds flexibility, it also introduces new, often invisible failures. Development speed is no longer the primary bottleneck of innovation. Reliability is ...

Seeing is believing, or in this case, seeing is understanding, according to New Relic's 2025 Observability Forecast for Retail and eCommerce report. Retailers who want to provide exceptional customer experiences while improving IT operations efficiency are leaning on observability ... Here are five key takeaways from the report ...

Technology leaders across the federal landscape are facing, and will continue to face, an uphill battle when it comes to fortifying their digital environments against hostile and persistent threat actors. On one hand, they are being asked to push digital transformation ... On the other hand, they are facing the fiscal uncertainty of continuing resolutions (CR) and government shutdowns looming near and far. In the face of these challenges, CIOs, CTOs, and CISOs must figure out how to modernize legacy systems and infrastructure while doing more with less and still defending against external and internal threats ...

Reliability is no longer proven by uptime alone, according to the The SRE Report 2026 from LogicMonitor. In the AI era, it is experienced through speed, consistency, and user trust, and increasingly judged by business impact. As digital services grow more complex and AI systems move into production, traditional monitoring approaches are struggling to keep pace, increasing the need for AI-first observability that spans applications, infrastructure, and the Internet ...

If AI is the engine of a modern organization, then data engineering is the road system beneath it. You can build the most powerful engine in the world, but without paved roads, traffic signals, and bridges that can support its weight, it will stall. In many enterprises, the engine is ready. The roads are not ...