Requestly
Winter 2022AcquiredOpen-Source Postman alternative
Pressure-test this opportunity
Explore the risks and possibilities with a prompt for ChatGPT, Claude, or your agent.
Open-Source Postman alternative
Explore the risks and possibilities with a prompt for ChatGPT, Claude, or your agent.
Requestly turned a developer's workaround into a durable testing tool. Sachin Jain first built a Chrome extension to redirect JavaScript files, then he and Sagar Soni expanded it into an open-source system for intercepting, modifying, mocking, and recording HTTP traffic across browsers and desktop apps. By 2024, Requestly said it was used by more than 250,000 developers in 14,000 organizations.[1]
This is an acquisition story, not a failure story. Requestly proved strong individual-developer demand, but its own evolution kept pulling it from a focused browser utility toward team collaboration, API testing, and enterprise controls. That placed it beside better-capitalized testing suites. BrowserStack acquired the company in May 2025 for an undisclosed amount and kept the product open source and independently available.[2]
Requestly began with a specific irritation. In 2014, Jain was debugging an intermittent flash-of-unstyled-content problem in Adobe Target. He needed to serve a local JavaScript file in place of the production asset, so he built a Chrome extension and shared it with his team. TechCrunch described Jain as a decade-long veteran of Google, Adobe, and Grofers, and Soni as a repeat builder of web, mobile, and desktop products.[3][12]
The first product did one narrow job: redirect JavaScript. Requestly's later product history records a sequence of expansions, from redirects and header modification to interception of all HTTP requests, a lightweight debugging proxy, team collaboration, browser and mobile interception, API mocking, and enterprise readiness.[4] Soni, then pursuing a master's degree, contacted Jain after discovering the extension; YC says they met at a coworking space before both committed full-time. The company joined Y Combinator's Winter 2022 batch after the utility already had real usage. YC now describes it as an “Open-Source Postman alternative” with more than 200,000 active installs.[5]
Jain later stated the origin plainly: “Charles & Fiddler were hard to set up so I built a simple Chrome extension to do this.”[6] In the 2022 Hacker News launch, he described the early distribution as “completely organic” and said the side project had crossed 40,000 monthly active users before the founders went full-time.[12] Those comments capture the original wedge: remove proxy configuration from a task developers performed every day.
Requestly let a developer change network behavior without changing the application or standing up a conventional proxy. A user could install the browser extension, define a rule, match a URL, and redirect it, modify headers, replace request or response bodies, inject scripts, block calls, or introduce mock responses. A frontend engineer could therefore continue work before a backend endpoint existed, reproduce an error response, or load a local script on a production page.
The product grew beyond rules. SessionBook recorded network traffic and supported converting captured calls into mocks. The API client handled REST and GraphQL requests, collections, environments, pre- and post-request scripts, and collection runs. A desktop client extended interception beyond one browser to applications and devices. Teams gained shared workspaces and configuration sharing.[1]
Its distinction was proximity to the developer's actual workflow. Requestly's Chrome Web Store listing says the extension does not configure a browser proxy, avoiding common VPN conflicts and latency. The current listing has 300,000 users and a 4.5 rating from roughly 1,700 ratings.[9] The code is open source, allowing security review and self-hosting, while paid collaboration and enterprise features created a commercial layer.[10]
The initial user was a frontend developer blocked by an unavailable API or awkward production debugging. The scope widened to QA engineers, full-stack teams, and organizations that needed repeatable mocks, shared rules, captured sessions, and controls. Public case material names use cases ranging from brand-personalized sales demos to testing hardware-dependent software, but customer-level results are vendor-authored and should not be treated as audited performance.
No credible public estimate isolates the market for browser-native HTTP interception. Broader API testing and software-testing figures would overstate Requestly's addressable wedge, so this report does not substitute them. The strongest demand evidence is product-specific: 250,000-plus developers across 14,000 organizations in 2024, followed by a current open-source claim of 300,000-plus developers.[1][8]
Requestly sat between several categories. Chrome extensions such as ModHeader handled narrower rule types. Charles Proxy and Fiddler offered deep traffic inspection but required proxy configuration. Postman dominated general API-client workflows. Browser developer tools provided built-in inspection but weak persistence, sharing, and scenario simulation. Requestly competed by combining fast browser installation with a broader catalog of traffic manipulation and mocking tools.
That middle position was both its advantage and its strategic constraint. A narrow extension could spread cheaply but had a modest willingness to pay. A full API and testing platform could support team subscriptions, but it competed with vendors that already owned enterprise budgets and adjacent workflows. BrowserStack's acquisition joined Requestly's developer-facing interception wedge to a testing company that says it serves more than 50,000 customers and runs over two million tests per day.[11]
Requestly used open-source and free distribution to acquire individual developers, then charged for higher limits and team capabilities. Its 2019 pricing ranged from free to $8 monthly Lite, $15 per-member Basic, and $23 per-member Professional tiers.[7] Current historical revenue, margins, funding totals, headcount, and acquisition consideration were not publicly verified in this research pass, so unit economics cannot be responsibly estimated.
The model's tension is visible even without those figures. Open source and a useful free extension reduced adoption friction and built trust for a tool with access to sensitive traffic. Revenue required converting some of those users into collaborative or enterprise accounts. The later product roadmap added the capabilities needed for that conversion, but each addition also moved Requestly closer to the crowded API and testing-platform market.
Requestly reported more than 250,000 developers in 14,000 organizations in February 2024.[1] YC cites more than 200,000 active installs and customer use at Google, Amazon, Workday, and Indeed.[5] The Chrome Web Store currently shows 300,000 users and approximately 1,700 ratings.[9] These are meaningful distribution signals, though the organization and customer names are company-reported, not proof of paid contracts.
Requestly's acquisition followed from the product's success. The original extension solved a sharp problem with near-zero setup and spread through the Chrome Web Store. But a browser utility and an enterprise testing business reward different behavior. Individual adoption favors breadth, free access, and local control. Enterprise sales favor administration, collaboration, support, and integration into larger testing workflows.
Requestly tried to bridge those economics by adding workspaces, desktop interception, mocks, an API client, session recording, and enterprise controls. The attempted remedy was sensible, and the usage figures show that it did not destroy developer appeal. Yet the remedy also increased product surface and placed the company in direct competition with Postman, proxy tools, and testing suites.
The non-obvious mechanism is wedge-to-suite gravity: the stronger Requestly became as an organization-level product, the less its browser-extension distribution alone constituted a defensible company boundary. BrowserStack already sold testing infrastructure to large teams. It could preserve Requestly's open-source wedge while connecting it to enterprise distribution and mobile-device infrastructure. BrowserStack said it was drawn to Requestly's “browser-native approach and passionate developer community.”[11]
The strongest counter-explanation is that Requestly could have remained independent and grown into a broad API platform. Its user base, open-source repository, and increasing enterprise feature set support that view. No public evidence found here shows distress, shrinking usage, or a failed financing.
The acquisition still resolved a structural mismatch. Requestly supplied a popular developer entry point; BrowserStack supplied a large commercial customer base and device cloud. BrowserStack identified API mocking as Requestly's strongest product-market fit and promised resources for expansion while keeping it independent and open source.[13] The announced roadmap extended interception and mocking to mobile devices and simulators, a capital- and infrastructure-heavy direction that fits the acquirer better than a standalone extension company.[11] The price and employee terms remain undisclosed, so the financial quality of the exit cannot be judged.