Cloud Foundry Foundation
The Linux Foundation fund behind Cloud Foundry, Paketo and the Open Service Broker API: launched in 2015 with seven Platinum members, now backed mainly by SAP and Broadcom’s VMware.
What it is
The Cloud Foundry Foundation (CFF) holds and funds Cloud Foundry, the open-source platform as a service that VMware created in 2009 and released in 2011. It was announced in December 2014 and launched in January 2015 as an independent non-profit run as a Linux Foundation Collaborative Project, with more than 40 members and seven Platinum members: EMC, HP, IBM, Intel, Pivotal, SAP and VMware. VMware gave the code to the foundation, and its first projects were the Cloud Foundry runtime and BOSH, the tool that deploys it. Since a charter that took effect on January 1, 2021 it has been a directed fund of the Linux Foundation, whose job is to “raise, budget and spend funds” for its projects.
For someone choosing Cloud Foundry, the foundation is what keeps the name and the code out of any one company’s hands: its charter requires all project trademarks to be held by LF Projects, LLC or the Linux Foundation, and the code is under the Apache License 2.0. The charter names three projects, Cloud Foundry, Paketo (a set of Cloud Native Buildpacks) and the Open Service Broker API, and the technical community is organised into working groups, which in 2025 and 2026 added Concourse CI and an Agentic Runtime group for running AI agents on Cloud Foundry.
The badge says nothing about how many companies are behind it, and that number has fallen a long way. In October 2026 the foundation listed eight members: two Platinum (SAP and VMware, now part of Broadcom), four Silver (anynines, Comcast, fivetwenty and STACKIT) and two Associate members, among them the UK’s Government Digital Service. Charter revisions removed the executive director post in 2022 and the Gold tier in 2023, and four of the five elected technical leaders work at SAP or Broadcom.
Its projects in this catalog
In depth
Who decides#
The Governing Board handles the budget, membership, outreach and policy. Its voting members are one representative from each Platinum member, one Silver representative the board picks from the Silver members’ nominees, and the chair of the Technical Oversight Committee (TOC). No company or group of related companies may have more than one vote: if the TOC chair works for a company that already appoints a director, the chair sits on the board without a vote, which was the case in October 2026, when the chair worked at SAP. Members must also belong to the Linux Foundation, which holds the money and takes 9% of the first $1 million raised each year and 6% above that.
The TOC runs the technical side: it sets the overall direction and roadmap, resolves disputes, coordinates releases, and approves the creation and dissolution of projects and working groups. It has five members serving staggered two-year terms, and no more than two should come from the same company. Anyone who has contributed in the past twelve months can vote in its elections, with people who have at least 25 measurable contributions added to the voter list automatically, and ballots are ranked using the Schulze method. In October 2026 its members came from SAP (two, including the chair), Broadcom (two) and the US government’s Cloud.gov.
Changes go through RFCs#
Larger changes are proposed as RFCs in the public cloudfoundry/community repository, discussed in the open and accepted by the TOC; by October 2026 the repository held 74 of them. The working groups own the code: each has execution and technical leads and a list of GitHub repositories, from App Runtime Platform and Foundational Infrastructure, which includes BOSH, to Paketo, Concourse and documentation.
The RFC process also retires work. RFC 0060, started on July 10, 2026, proposed archiving the Cloud Foundry on Kubernetes working group and its Korifi project because the community had lost interest: no Slack traffic, no meeting attendees, no new issues and no known production users, with the three remaining maintainers, all at SAP, out of capacity. It was accepted, and Korifi was archived on September 15, 2026.
Where it came from2009–2026
Cloud Foundry started in 2009 as Project B29, built by a small VMware team led by Derek Collison, and VMware released it as open source in 2011. It moved to Pivotal, a joint venture of EMC, VMware and GE, and in February 2014 plans were announced for an open governance foundation. The Cloud Foundry Foundation was announced in December 2014 as an independent non-profit managed as a Linux Foundation Collaborative Project, and it launched in January 2015 with more than 40 members.
As Kubernetes drew developers away, the foundation shrank and was restructured as a directed fund of the Linux Foundation, under a charter effective January 1, 2021. Within months the project management committees were replaced by an elected Technical Oversight Committee and working groups. Later revisions handed day-to-day operations to staff instead of an executive director (2022) and cut the membership tiers to Platinum, Silver and Associate (2023).
Attempts to run Cloud Foundry on Kubernetes, from Eirini in 2018 to Korifi, were wound down; Korifi was archived in September 2026. Meanwhile the community took on Concourse CI in 2025 and an Agentic Runtime working group in 2026.
Why it’s built this way
- A neutral owner for the name and code
- Pivotal’s chief executive Paul Maritz said the cloud was “too important to allow it to become proprietary and have customers locked in”, and the founding members wanted a certification programme to keep products sold as Cloud Foundry consistent.
- Technical leaders elected by contributors
- Technical direction is meant to follow the contributors rather than the dues: the TOC that replaced the project management committees in 2021 is elected by anyone who contributed in the past year, and no company should hold more than two of its five seats.
- A smaller directed fund
- With fewer members paying dues, running as one of the Linux Foundation’s directed funds lets the LF handle finance, accounting and other operations for a fee instead of the foundation keeping its own.
Timeline
- 2009
Project B29 starts at VMware
- 2011
VMware releases Cloud Foundry as open source
- 2014
Cloud Foundry Foundation announced in December
- 2015
Foundation launches in January with more than 40 members
- 2021
Becomes a directed fund of the Linux Foundation; a TOC replaces the project management committees
- 2023
Gold membership tier dropped in a charter effective May 1
- 2026
Agentic Runtime working group added in June; Korifi archived in September
- Cloud Foundry Foundation turns 5 (Project B29, 2011 open source, 2015 launch)
- Linux Foundation: Cloud Foundry Foundation established to advance platform-as-a-service (December 2014)
- Wikipedia: Cloud Foundry (history, 2014 announcements)
- Cloud Foundry Foundation charter, first version (effective January 1, 2021)
- cloudfoundry/community: Reworking project charter to include a TOC and remove the PMCC/PMC (May 2021)
- Cloud Foundry Foundation charter (effective September 15, 2023)
- Cloud Foundry Foundation charter revision history (executive director removed January 2022, Gold tier removed May 2023)
- Open Source For You: Developers are wasting their time with Kubernetes alone (January 2025)
- RFC 0060: Archive the CF on K8S working group
- Korifi repository (archived September 15, 2026)
Sources · facts checked 2026-10-28
- Cloud Foundry Foundation: Who we are (a directed fund of the Linux Foundation)
- Cloud Foundry Foundation: Members (October 2026)
- Cloud Foundry Foundation: Governance
- Cloud Foundry Foundation charter (effective September 15, 2023: projects, membership, Governing Board, TOC, trademarks, G&A fee)
- Cloud Foundry Foundation charter, first version (effective January 1, 2021)
- Cloud Foundry Foundation charter revision history
- Cloud Foundry TOC (members and terms, October 2026)
- Cloud Foundry working groups
- Agentic Runtime working group charter (added June 2026)
- Concourse working group charter (proposed January 2025)
- Cloud Foundry RFCs
- RFC 0060: Archive the CF on K8S working group (started July 10, 2026; accepted)
- Linux Foundation: Cloud Foundry Foundation established to advance platform-as-a-service (December 2014)
- Cloud Foundry Foundation turns 5