I took part in the FinOps Foundation and in FOCUS, its effort to define a common format for cloud cost and usage data, and I served on the foundation’s governing board. FOCUS is the clearest example I have of people doing open work where the work isn’t open source.
FOCUS stands for the FinOps Open Cost and Usage Specification. Every cloud provider publishes billing data in its own shape, with its own column names and its own idea of what counts as a charge. If you run workloads on more than one cloud, or sell a tool that reads those bills, you spend a lot of time translating. FOCUS defines shared columns, metrics, and terms so data from different vendors can be lined up and compared.1 The group produces a specification. It wasn’t trying to ship a program.
What interested me was who did the work. Most of the people involved build or sell proprietary software and services, and many don’t write code. Companies usually guard their cost structures and purchasing information closely. FOCUS gave competitors and customers a place to agree on a shared language for that commercially sensitive data.
Where FOCUS came from
FinOps as a practice took much of its shape from Cloud FinOps, the O’Reilly book by J.R. Storment and Mike Fuller.2 They and other practitioners formed the FinOps Foundation, which merged with the Linux Foundation in June 2020.3
FOCUS started in the foundation’s Open Billing working group. In January 2023 it became a specification project under the Joint Development Foundation, hosted by the Linux Foundation.4 Version 1.0 became generally available on June 20, 2024, announced at FinOps X with support from the major cloud providers.5 Later releases reached into SaaS and platform billing, contract commitments, and data freshness. Version 1.4 was ratified on June 4, 2026.6
Adoption and conformance are separate questions. On November 15, 2026, the FOCUS site listed 19 providers exporting billing data in the format, at versions from 1.0 to 1.3, some still in preview. None of the listings showed a conformance certificate, though the foundation runs a certification program.7 A vendor saying it supports a standard doesn’t tell a customer which version it implements or how thoroughly.
FOCUS wasn’t the Linux Foundation’s first standard. SPDX, a format for describing software packages and their licenses, began there around 2010 and became ISO/IEC 5962:2021.8 OpenChain’s license-compliance specification became ISO/IEC 5230:2020.9 The Joint Development Foundation had joined the Linux Foundation in 2018.10
What felt different to me was the community. A FinOps conference in 2026 feels different from an OSCON in 2008. OSCON centered on source code and the developers maintaining it. At a FinOps event, many attendees are finance and engineering leads, practitioners, vendors, and cloud providers. They share a practice, even when the products they sell remain proprietary.
What exactly is open?
The specification, its implementations, and the group that maintains it are separate things. Open source software comes with source code under terms that meet the Open Source Definition. An implementation of an open standard can be proprietary: publishing the spec doesn’t dictate the license on every program that follows it.
For an open standard, I look for a publicly accessible specification, clear rights to implement it, and a published process for changing it. Patent terms matter too. A document anyone can read may still come with implementation costs or restrictions. Whether outsiders can propose a change, and who can approve it, is another test.
Those distinctions make FOCUS easier to describe. It is a public specification developed through collaboration among customers and vendors. Many of its implementations are proprietary. Its governance gives some participants more authority than others. Calling the whole arrangement open source would hide what the group actually produces.
Why competitors cooperate
Open specifications with proprietary implementations are familiar. The IETF writes internet standards under the principle of “rough consensus and running code.”11 TCP is specified in public RFCs, though a router implementing it may be proprietary.12 SQL and PDF also have standards with competing implementations.1314
A shared format can cut integration costs and move competition onto features and service. Customers can change vendors without replacing every system that reads their data. Vendors who participate can shape the next version, and customers can ask several suppliers for the same change in one room. None of this requires the participants to abandon their commercial interests.
It does require them to fund the work. Foundations pay for staff, legal work, infrastructure, and meetings. Vendor memberships cover much of that cost. I think vendors deserve credit for supporting it.
But funding also buys influence. Most of FOCUS’s Steering Committee works for large companies, including Google Cloud, Microsoft, and AWS. Individual practitioners can join community calls, which isn’t the same as a vote.15 A Premier FinOps Foundation membership comes with a governing board representative.16 I sat on that board. A public specification doesn’t erase the advantage held by people whose employers can pay for a seat and the time to use it.
The useful question is what someone outside that circle can do. Can a practitioner document a billing problem, get it considered, and follow the decision? Can a small supplier implement the result on workable terms? Can a customer export its records without buying another service? The answers reveal more than a membership roster or an open label.
The AI turn
AI needs this kind of shared work too. A benchmark can be public even when the systems being tested are proprietary. A protocol can let competing services connect without opening the services themselves.
MLCommons grew out of the MLPerf benchmark, begun in 2018. Its consortium brings companies, universities, and nonprofits together to produce shared benchmarks and datasets.17 Its AI Safety working group formed in October 2023 and published an initial safety-benchmark proof of concept in April 2024.18 The evaluation’s availability and the rules for deciding what it measures deserve separate examination. A public score is more useful when people can inspect the test and understand who chose it.
In December 2025 Anthropic donated the Model Context Protocol, its specification for connecting models to tools and data, to the Agentic AI Foundation. Anthropic co-founded the Linux Foundation directed fund with Block and OpenAI.19 That moved a vendor-created protocol into a shared institutional home; its technical governance and membership structure remain things a user should read.20
FinOps has followed its own work into AI. The Linux Foundation launched the Tokenomics Foundation in August 2026 to develop shared methods for measuring AI costs and value. Its roadmap includes token cost reporting in FOCUS.21 The same billing problem is returning in a new form: before customers can compare services, they need suppliers to describe what was consumed in compatible terms.
For each of these projects, a public artifact is a beginning. The practical test is whether another party can use it, implement it, challenge it, and continue without the original vendor. FOCUS makes that test concrete for billing data. The next chapters apply it to software communities and to the models themselves.
Many of these commercial and institutional arguments were already in print in 1999, in Open Sources: Voices from the Open Source Revolution and Eric Raymond’s The Cathedral and the Bazaar.22 Rereading them shows both how much the earlier writers understood and where the work has become harder.
Notes
FOCUS Project, “Introduction,” FOCUS Specification working draft,
specification/overview.md, GitHub, accessed 15 November 2026, https://github.com/FinOps-Open-Cost-and-Usage-Spec/FOCUS_Spec/blob/working_draft/specification/overview.md. The scope section says the schema defines dimensions, metrics, attributes, and “a common lexicon for describing billing data.” ↩FinOps Foundation, “Cloud FinOps O’Reilly Book,” finops.org, accessed 15 November 2026, https://www.finops.org/insights/finops-book. The page lists J.R. Storment as Executive Director and Mike Fuller as CTO of the FinOps Foundation. ↩
FinOps Foundation, “About the FinOps Foundation,” finops.org, accessed 15 November 2026, https://www.finops.org/about. The FAQ says the foundation “merged with the Linux Foundation” in June 2020 and closed its previous non-profit entity at the end of 2020. ↩
FOCUS Project, “Background and History,” in “Introduction,” FOCUS Specification working draft, GitHub, accessed 15 November 2026, https://github.com/FinOps-Open-Cost-and-Usage-Spec/FOCUS_Spec/blob/working_draft/specification/overview.md. See also FOCUS Project, “About the FOCUS Project,” https://focus.finops.org/about-focus, which describes FOCUS as a Joint Development Foundation Specification Project. ↩
Mike Fuller, Rob Martin, Udam Dewaraja, J.R. Storment, and Amber Gregorio, “FOCUS 1.0 is Now Available. Practitioners and Clouds Begin Adoption.,” FinOps Foundation, 20 June 2024, https://www.finops.org/insights/focus-1-0-available. The post says Storment announced the release at FinOps X 2024 in San Diego and that AWS, Microsoft, Google, and Oracle supported FOCUS at launch. ↩
FOCUS Project, “What is FOCUS?,” focus.finops.org, accessed 15 November 2026, https://focus.finops.org/what-is-focus. The release history covers 1.2 (ratified 29 May 2025, SaaS and PaaS billing), 1.3 (ratified 5 December 2025, a Contract Commitment dataset and data recency and completeness metadata), and 1.4 (ratified by the Steering Committee on 4 June 2026). The 1.4 text is at https://focus.finops.org/docs/specification/v1-4. ↩
FOCUS Project, “Get Started with FOCUS Datasets,” focus.finops.org, accessed 15 November 2026, https://focus.finops.org/get-started/. On that date the Data Generators table listed 19 providers with their latest supported FOCUS version and status (generally available, public preview, or private preview); its Conformance Gap Report and Conformance Certificate columns were empty for every row. For the program, see FinOps Foundation, “FinOps Certified FOCUS v1.2 Conformant,” finops.org, accessed 15 November 2026, https://www.finops.org/certification-for-organizations/finops-certified-focus-conformant, which says certified providers are listed on the FOCUS website and that certification is open to FinOps Foundation members who generate billing datasets. ↩
SPDX, “About SPDX: Overview,” spdx.dev, accessed 15 November 2026, https://spdx.dev/about/overview/. The timeline says drafting began in February 2010 in a Linux Foundation work group and that SPDX was announced in August 2010 as part of the Linux Foundation’s Open Compliance Program. For the standard, see ISO, “ISO/IEC 5962:2021 Information technology: SPDX Specification V2.2.1,” published August 2021, https://www.iso.org/standard/81870.html. ↩
ISO, “ISO/IEC 5230:2020 Information technology: OpenChain Specification,” https://www.iso.org/standard/81039.html. OpenChain describes itself as maintaining the ISO/IEC standards for open source license compliance and security assurance at https://www.openchainproject.org/. ↩
Emily Olin, “The Joint Development Foundation Joins the Linux Foundation Family to Drive Adoption of Open Source and Standards,” Linux Foundation, 11 December 2018, https://www.linuxfoundation.org/press/press-release/jdf-joins-lf-family. The release says the JDF launched in 2015 and describes it as a “standards organization in a box.” ↩
IETF, “Introduction to the IETF,” ietf.org, accessed 15 November 2026, https://www.ietf.org/about/introduction/. The principles section lists “Rough consensus and running code.” ↩
W. Eddy, ed., “Transmission Control Protocol (TCP),” RFC 9293, IETF, August 2022, https://www.rfc-editor.org/rfc/rfc9293.html. This Internet Standard (STD 7) replaces the original RFC 793 specification of TCP. ↩
ISO, “ISO/IEC 9075-1:2023,” https://www.iso.org/standard/76583.html. Part 1 of the international SQL standard. ↩
ISO, “ISO 32000-2:2020,” https://www.iso.org/standard/75839.html. The current international standard for PDF. ↩
FOCUS Project, “About the FOCUS Project,” focus.finops.org, accessed 15 November 2026, https://focus.finops.org/about-focus. The roster on that date had nine members: staff from Adobe, IBM Cloudability, Datadog, Capital One, Walmart, AWS, Google Cloud, and Microsoft, plus the FinOps Foundation’s CTO. Members are appointed by the FinOps Foundation Governing Board. The page directs people who aren’t formal Contributing Members to FOCUS Community Calls. ↩
FinOps Foundation, “Governing Board,” finops.org, accessed 15 November 2026, https://www.finops.org/about/governing-board/. Under the Participation Agreement, voting members include “one representative appointed by each Premier Member.” ↩
MLCommons, “MLCommons Announces the Formation of AI Safety Working Group,” 26 October 2023, https://mlcommons.org/2023/10/mlcommons-announces-the-formation-of-ai-safety-working-group. The boilerplate describes MLCommons as “an open engineering consortium” that began with the MLPerf benchmark in 2018 and works with “125+ members.” For the current figure, see MLCommons, “Our Members,” mlcommons.org, accessed 15 November 2026, https://mlcommons.org/our-members, which describes “125+ members and affiliates” including “startups, leading companies, academics, and non-profits.” ↩
MLCommons, “MLCommons Announces the Formation of AI Safety Working Group,” 26 October 2023, https://mlcommons.org/2023/10/mlcommons-announces-the-formation-of-ai-safety-working-group; MLCommons, “Announcing MLCommons AI Safety v0.5 Proof of Concept,” 16 April 2024, https://mlcommons.org/2024/04/mlc-aisafety-v0-5-poc/. ↩
Anthropic, “Donating the Model Context Protocol and establishing the Agentic AI Foundation,” Anthropic News, December 2025, https://www.anthropic.com/news/donating-the-model-context-protocol-and-establishing-of-the-agentic-ai-foundation. The post says the AAIF is “a directed fund under the Linux Foundation, co-founded by Anthropic, Block and OpenAI, with support from Google, Microsoft, Amazon Web Services (AWS), Cloudflare, and Bloomberg.” On what a directed fund is, see the Linux Foundation’s standard Directed Fund Participation Agreement, for example “The OpenSearch Software Foundation Fund Directed Fund Participation Agreement,” accessed 15 November 2026, https://cdn.platform.linuxfoundation.org/agreements/opensearch-foundation.pdf, which says the fund’s purpose is “to raise, budget and spend funds in support of” its technical project and that members must also be Linux Foundation members. ↩
Linux Foundation, “Linux Foundation Announces the Formation of the Agentic AI Foundation (AAIF), Anchored by New Project Contributions Including Model Context Protocol (MCP), goose and AGENTS.md,” 9 December 2025, https://www.linuxfoundation.org/press/linux-foundation-announces-the-formation-of-the-agentic-ai-foundation. On membership tiers, see Agentic AI Foundation, “Members,” accessed 15 November 2026, https://aaif.io/members/. That page lists eight Platinum members (AWS, Anthropic, Block, Bloomberg, Cloudflare, Google, Microsoft, OpenAI), with Platinum limited to eight seats at $350,000 to $370,000 a year, plus Gold and Silver tiers and no-cost Associate membership for approved nonprofits and universities. ↩
Linux Foundation, “Linux Foundation Launches the Tokenomics Foundation to Define the Economics and ROI of AI Value,” 4 August 2026, https://www.linuxfoundation.org/press/linux-foundation-launches-the-tokenomics-foundation-to-define-the-economics-and-roi-of-ai-value. The release says the technology value foundations “will also support FOCUS, the open billing data specification that provides the substrate for normalizing cost and usage data across providers,” and plans token cost telemetry for FOCUS v1.5 and later. ↩
Chris DiBona, Sam Ockman, and Mark Stone, eds., Open Sources: Voices from the Open Source Revolution (O’Reilly, 1st ed., January 1999), full text at https://www.oreilly.com/openbook/opensources/book/; Eric S. Raymond, The Cathedral and the Bazaar (O’Reilly), https://www.oreilly.com/library/view/the-cathedral/0596001088. That catalog page is for the revised edition. Raymond’s revision history for the essay lists the 31 August 1999 text as “the version that O’Reilly printed in the first edition of the book”: http://www.catb.org/~esr/writings/cathedral-bazaar/cathedral-bazaar/. ↩
From But Is It Open? by Timothy O’Brien (Discursive, 2026). © 2026 Timothy O’Brien. All rights reserved.