Mashery is where the commercial API management industry began, and you cannot tell the history of how APIs became a business without starting there. Mashery, founded in 2006, was the first API management service provider — the company that invented the category of selling tools and services to help other companies manage their APIs. Before Mashery, an API was just something you built and ran yourself; Mashery created the idea that there was a whole layer of value — keys, rate limiting, analytics, developer portals, documentation — that could be provided as a service. When I document the history of APIs, Mashery occupies a foundational place as the pioneer that established API management as a commercial discipline, and its arc from pioneer through acquisition to relative obscurity is one of the instructive stories about how the API industry evolved.
The founding insight, which I credited Mashery with from the beginning, was that API management was a distinct layer worth providing as a service. I profiled Mashery in 2010 as an API management service provider offering management, metrics and reporting, and community management — the three pillars that would define the category. Mashery’s model was the proxy: your API traffic flowed through Mashery’s infrastructure, which let them handle authentication, enforce rate limits, capture analytics, and provide the developer-facing portal. This proxy-based model was the original architecture of API management, and it established the pattern that Apigee, 3Scale, and the others would follow. Oren Michels, Mashery’s CEO, was articulating the vision of API management as a business at a time when most companies didn’t yet understand why they’d need it. Mashery was early, and being early meant defining the category.
The Business of APIs Conference was Mashery’s contribution to the industry beyond its product, and it mattered enormously to the field’s development. I covered the Mashery Business of APIs Conference from 2010, with Oren Michels keynoting on the history of APIs, and the conference series running across San Francisco, New York, and London. This was one of the first venues where the business and strategy of APIs — not just the technology — was discussed seriously, with speakers like Twitter’s Ryan Sarver and representatives from Netflix, Best Buy, and PayPal/eBay. The Business of APIs Conference helped establish that APIs were a business concern, not just an engineering one, and it was part of the infrastructure of conversation and community that made the API industry cohere. Mashery wasn’t just selling a product; it was helping build the field’s understanding of itself, which is the mark of a genuine pioneer.
Mashery’s I/O Docs was a real technical contribution to the commons, and I’ve always credited it. In 2011, Mashery open-sourced I/O Docs — one of the earliest interactive API documentation tools, letting developers make live API calls from within the documentation. This was a genuine advance in developer experience, predating Swagger UI, and open-sourcing it was a generous contribution to the broader community rather than a purely commercial move. I/O Docs showed that Mashery understood documentation and developer experience as core to API success, and the decision to release it openly reflected a community-minded ethos that was part of the early API industry’s character. It’s a reminder that the pioneers weren’t just building businesses; they were building shared tools and practices that advanced the whole field.
The competitive evolution is part of the Mashery story, because Mashery’s pioneering position attracted competition that reshaped the market. By 2011, Mashery was responding to competitive pressure — launching an on-premise version alongside its cloud offering, partly in response to Apigee’s moves. The API management service provider roundups I did, like the one for 2011, positioned Mashery alongside Apigee and 3Scale as the dominant players, with Mashery’s developer network reaching well over a hundred thousand developers. The competition among these pioneers drove rapid innovation in API management, but it also meant that being first didn’t guarantee staying ahead. The market Mashery created became contested, and the dynamics of that competition would ultimately shape which players thrived and which faded.
The acquisition arc is the part of Mashery’s story that turned cautionary, and it’s instructive about what happens to pioneers. Intel acquired Mashery in 2013 — I wrote about it as “from CPU to API for Intel,” a chip company buying its way into the API economy, estimated at somewhere between 120 and 180 million dollars. It was a validation of the category Mashery had created: a major technology company paying serious money for an API management pioneer. But the Intel acquisition didn’t go the way anyone hoped. Intel struggled to integrate and capitalize on Mashery, and eventually sold it to TIBCO, where Mashery faded from the prominence it once held. The pioneer that invented API management ended up passed between owners, diminished from its founding significance. This is a recurring pattern in tech history — the pioneer that creates a category often isn’t the one that ultimately dominates or endures it, and Mashery is a clear example. The company that started it all became a footnote that newer players and the cloud giants moved past.
Mashery’s legacy is the entire commercial API management industry, even though Mashery itself didn’t sustain its leadership. The category Mashery invented in 2006 — API management as a service, with keys and rate limiting and analytics and portals — became foundational to how the entire API economy operates. Every API management company that followed, every gateway, every developer portal, every analytics dashboard, traces its lineage back to the model Mashery established. The Business of APIs Conference helped create the field’s self-understanding. I/O Docs advanced developer experience and the open-source commons. And the acquisition arc became a lesson in how pioneers can create enormous value for an industry while failing to capture it for themselves. When I reflect on the history of APIs, Mashery is the company that proved API management was a real business worth building, established the patterns the whole industry would follow, and then — like so many pioneers — got passed by the very industry it created. That’s a poignant but genuine kind of legacy: not the enduring dominance of the founder, but the permanent imprint of the category they invented on everything that came after.
References
- Mashery API Services
- Mashery Business Of APIs Conference
- Mashery Open Sources Their API I/O Docs
- Mashery Now Runs On-Premise Or In The Cloud
- API Management Service Provider Roundup For 2011
- Mashery Plays API Match Maker With Developer Connect
- From CPU To API For Intel
- History Of APIs: Mashery
- My Response On The Department Of Veterans Affairs RFI For The Lighthouse API Management Platform
