Open source is the foundation that the entire API tooling ecosystem is built on, and the business dynamics around it are some of the most important and most contested in the API economy. From the specifications that define how we describe APIs, to the tools that lint and test and document them, to the clients we use to consume them, the API world runs substantially on open source — and yet the relationship between open source and commercial interests in the API space is a constant negotiation. I’ve watched open source drive adoption, enable ecosystems, and democratize capabilities that would otherwise be locked up, while also watching the perennial tension between the open-source community ethos and the commercial imperatives of the vendors who fund much of it. Understanding the business of open source in APIs means understanding both its enormous generative power and the strategic dynamics that determine who benefits from it.
The specifications are the clearest case of open source’s foundational role, and they prove its generative power. OpenAPI, AsyncAPI, JSON Schema, Spectral — the specifications and tools at the core of the modern API world are open, and that openness is precisely why they became universal. An open specification that anyone can implement, extend, and build tooling around generates an ecosystem in a way a proprietary one never could. I documented the open-source community tooling built on OpenAPI, on AsyncAPI, on GraphQL, on JSON Schema, and the pattern is consistent: an open specification spawns a rich ecosystem of open-source tools, which drives adoption of the specification, which attracts more tooling, in a virtuous cycle. The business lesson is profound: openness drives adoption, and adoption is the foundation of value. The specifications won by being open, and the entire ecosystem of value — including the commercial products built on top — exists because of that openness.
The open-source-versus-proprietary tension in API management and tooling is a recurring business story I’ve tracked for fifteen years. I asked in 2012 where the open-source API platform was, because the early API management market was dominated by proprietary providers, and I wanted an open alternative. 3Scale’s open-source API proxy built on NGINX in 2012 was an important step, and over the years open-source alternatives emerged across the stack. The business models around this are genuinely interesting: companies like Restlet built models combining open-source tooling with commercial cloud services, and the open-core model — open-source foundation with commercial features on top — became common. The strategic question every API tooling company wrestles with is how much to open and how much to keep proprietary, because openness drives adoption while proprietary features capture revenue. Getting that balance right is one of the central business challenges of the API tooling industry.
The design editor and client stories show open source as a competitive and community force. I wanted an open-source visual API design editor for years, and when Apicurio arrived in 2017, I celebrated it as the open-source editor I’d been looking for — because the proprietary, locked-in design tools were holding the space back, and an open foundation everyone could build on was what the ecosystem needed. The Bruno API client, which I championed starting in 2024, is the most recent and most striking example: an open-source, local-first, Git-native client that emerged as a direct response to Postman’s increasingly heavy, commercial, cloud-centric platform. The “great unbundling of the API client” I wrote about is substantially an open-source story — open-source tools pulling functions back out of the proprietary platform, offering focus and control where the commercial platform offered convenience at the cost of lock-in. Open source is the competitive force that keeps the commercial platforms honest, and the cycle between proprietary consolidation and open-source unbundling is one of the defining business dynamics of the API tooling space.
The “what does open mean” question is where the business of open source gets genuinely contested, and I’ve interrogated it directly. I wrote in 2021 about what “open” means in the world of APIs — because “open” has been so thoroughly appropriated by commercial interests that the word itself requires scrutiny. A company can call its API “open” while retaining the right to close it, call its tooling “open source” while controlling the project tightly, or use the language of openness as marketing while the reality is proprietary control. The business of open source includes a lot of strategic positioning around the open label, because openness has genuine value and companies want to claim it whether or not they’re delivering it. The honest version of open source — genuinely open licenses, genuine community governance, genuine freedom to fork and build — is different from the marketing version, and distinguishing them is part of reading the API tooling business clearly.
The machine-readable and forward-looking dimension is where I’ve pushed open source recently, and it connects to the deeper commons argument. I wrote in 2024 about how you articulate that an API is open source in a machine-readable way — because if openness is a property that matters, it should be discoverable and verifiable, not just a claim. This connects open source to my broader commons beliefs: open source is the commons applied to tooling and code, the same instinct that drives my advocacy for open specifications, open data, and the API commons. The business case for open source in APIs, at its deepest, is the same as the commons case: openness generates more total value than enclosure, even if it captures less of that value for any single party, because the ecosystem that openness enables is worth more than the control that proprietary lock-in provides. The API tooling companies that have thrived have mostly understood this — building open foundations that drive adoption, then building sustainable businesses on the services, support, and commercial features that the open foundation makes possible. Open source isn’t charity in the API world; it’s a business strategy grounded in the recognition that in a connected, ecosystem-driven economy, openness drives the adoption that creates the value, and the companies that contribute genuinely to the open foundation are positioned to capture a fair share of the enormous value that foundation generates. The whole API economy runs on open source, and the businesses that understand open source as a generative strategy rather than just a cost have been the ones that built the most durable value on top of it.
References
- Where Is The Open Source API Platform
- 3Scale Launches Open Source API Proxy Built On NGINX
- The Restlet Open Source And APISpark Cloud Business Model
- Apicurio Is The Open Source Visual API Design Editor I Was Looking For
- Postman Open Source
- The Open Source Community Tooling Built On OpenAPI
- What Does Open Mean In The World Of APIs
- Open Source Educational Resources On Modern APIs
- Elevating The Bruno API Client As A Cornerstone Of API Operations
- How Do You Articulate That An API Is Open Source In A Machine-Readable Way
