Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Pivotal’s “big open-source move” was not one blanket decision to give away all its software. It was a business strategy built around contributing to open-source projects, supporting shared governance in Cloud Foundry’s case, and selling integrated products and services around community software. The distinction matters: open code and commercial offerings can coexist, and Pivotal’s 2014 Cloud Foundry announcement concerned formal governance—not the project’s first release as open source.
What did Pivotal’s open-source move mean?
There were two related but distinct parts to the story:
- A company-wide approach: Pivotal worked on, sponsored, or contributed to multiple open-source projects, then built customer offerings around that software.
- A Cloud Foundry governance proposal: In February 2014, Pivotal and several technology companies announced plans for an independent nonprofit foundation and formal open governance for Cloud Foundry, while retaining the Apache License 2.0.
Neither point means that every project belonged to Pivotal, that all Pivotal products became free, or that the company transferred every software asset to a community. Pivotal’s April 2019 account named Cloud Foundry, Kubernetes, Concourse, Open Service Broker API, Istio, Spinnaker, Knative, Apache Tomcat, Geode, PostgreSQL, RabbitMQ, and Spring among projects it developed, sponsored, or contributed to. That was Pivotal’s project list at the time, not an exhaustive or current ownership roster. Pivotal’s 2019 account of its open-source strategy
What changed for Cloud Foundry in 2014?
Cloud Foundry was already described as an open-source project in Pivotal’s February 24, 2014 announcement. The proposed change was to give it an independent foundation and a formal, shared governance structure. Pivotal said it would work toward that model with EMC, HP, IBM, Rackspace, SAP, and VMware, and that the Apache License 2.0 would remain in place. The announcement reported more than 750 individual contributors at that time; that is a historical figure, not a current count. Pivotal’s February 2014 announcement
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Clear out junk files and repair common Windows errors3Fix the driver behind crashes, sound loss and screen glitchesThe practical distinction is between a project’s code and license on one hand, and its decision-making structure on the other. A license sets legal terms for using and redistributing code; governance concerns how project decisions are made and who can participate. Pivotal’s announcement addressed both dimensions, but it did not establish that every later governance outcome or adoption experience would be the same.
#1 Best Overall
Why combine open-source projects with commercial products?
Pivotal’s explanation was that contributing to shared projects could pool engineering effort, connect its teams with a broad developer community, expose the company to emerging technologies, and make customer adoption less disruptive. It also described a commercial rationale: focus on integrating open-source components and providing support. These were Pivotal’s stated reasons and expected benefits, not independently measured results. Pivotal’s 2019 account
The company’s business model was visible from its launch. In April 2013, Pivotal described a platform strategy based on Cloud Foundry and Spring and listed collaborative support and co-development among its services. Pivotal’s April 2013 launch announcement In April 2019, it described integrated offerings built on open-source software. For customers, open source therefore did not automatically mean “no vendor,” “no paid support,” or “no commercial product.”
Rank #2
- Ideal for Gifting
- Ideal for a bookworm
- Compact for travelling
Project versus distribution
Pivotal called Pivotal Cloud Foundry (PCF) its distribution of the Cloud Foundry open-source project. A community project and a vendor distribution are not interchangeable: a vendor may package and integrate project components, provide support, and offer an operational product while the upstream project remains open source. The project’s license does not, by itself, establish the terms, price, or support commitments of a commercial offering.
Recommended Free Tools
How does open source compare with a proprietary approach?
“Open source” and “proprietary” are not complete descriptions of how a product works in practice. For an organization choosing software, compare the concrete terms and responsibilities:
| Question | What to assess |
|---|---|
| Code access and reuse | Who can inspect, modify, and redistribute the code under its license? |
| Project direction | Who makes decisions, and how can users or contributors influence them? |
| Maintenance and security | Who maintains the software, publishes releases, and handles security fixes? |
| Compatibility and portability | Will the software work with the systems you need, and how difficult would migration be? |
| Support | What help is available, from whom, and under what terms or cost? |
Public code and shared governance may broaden participation and scrutiny, but neither guarantees secure software, easy portability, active maintenance, or a particular support experience. Pivotal itself cautioned that open source does not make software bulletproof. The sources establish the historical governance proposal and Pivotal’s views; they do not demonstrate a universal outcome for adopters.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.What happened after VMware acquired Pivotal?
VMware completed its acquisition of Pivotal on December 30, 2019, according to the Cloud Foundry Foundation’s Q4 2019 report, which also records consolidation of the companies’ Foundation memberships. Cloud Foundry Foundation Q4 2019 report
Rank #4
In March 2020, VMware described Spring, Cloud Foundry, Geode, and Concourse as community projects in discussing project teams previously associated with Pivotal returning to VMware. VMware’s March 2020 open-source blog post That corporate change is a separate chapter from the earlier Cloud Foundry governance proposal; it should not be described as making all associated open-source code proprietary.
Quick Recap
Best Value
- It can be a gift option
- Comes with secure packaging
- Helpful in various ways
How the story developed
- April 2013: Pivotal’s launch announcement placed Cloud Foundry and Spring in its platform plans and listed open-source support and co-development. Launch announcement
- April 2013: Spring’s announcement described Spring and Cloud Foundry as part of the Pivotal Initiative and said contributors to Spring, RabbitMQ, Redis, and Apache Tomcat were part of that effort. Spring’s announcement
- February 2014: Pivotal announced a proposed independent foundation and formal open governance for Cloud Foundry, with Apache 2.0 retained. Governance announcement
- April 2019: Pivotal described its activity across multiple open-source projects and its rationale for building customer offerings around them. Pivotal’s account
- December 30, 2019: VMware completed its acquisition of Pivotal. Foundation report
- March 2020: VMware discussed teams associated with Pivotal and named projects as community projects. VMware blog post
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
