The Independent Web Scraping Vendor Is Getting Smaller
On July 9, 2026, Oxylabs announced a $130 million investment from Warburg Pincus at a $3.6 billion valuation. Their portfolio already included Webshare (acquired 2022) and ScrapingBee (acquired 2025). That's not a coincidence. It's the shape of the market now.
The mid-market web scraping API is disappearing. Not one vendor at a time. All at once.
Three years ago you had a dozen credible options between the enterprise floor (Bright Data, Zyte) and the hobbyist ceiling (a shell script and a proxy list from GitHub). Today most of the names in the middle have either been bought or reshaped their pitch to court a different buyer. The pattern is consistent enough that "who owns this vendor in 18 months" now belongs on the same evaluation checklist as uptime and success rate.
Here's what's actually happening, and what to ask about it.
The Consolidation Pattern
The data infrastructure category, pegged at $1.17 billion in 2026 and projected to reach $2.23 billion by 2031, is growing fast enough to attract private-equity capital but small enough that a $130M round can rewire it. The public framing around the Oxylabs deal makes the intent clear: capital for AI-agent-era product development, with room for more acquisitions. Translation: expect two to four more mid-market deals before the year is out.
Oxylabs isn't alone. Bright Data reports over $300M in annualized revenue and 50% year-over-year growth, driven mostly by data-for-AI demand. Zyte is publishing free industry whitepapers and positioning itself as the compliant-by-default option upmarket. Firecrawl has quietly shipped official SDKs in six languages (Python, Node.js, Go, Rust, Java, Elixir) plus a CLI, pitching itself as "the web data API for AI agents". None of these are neutral moves. Each one is a claim on a specific buyer segment.
What the buyer sees is fewer nouns in the same category. What the buyer doesn't see (and this matters more) is the change in incentives when a formerly independent product becomes a line item inside a larger portfolio.
What You Lose When Your Vendor Gets Acquired
The best case: nothing changes for a year, the founders leave quietly, the roadmap re-prioritizes around the parent's customer segment, and one morning you find out your pricing tier is being sunset.
The realistic case: pricing gets restructured toward enterprise. Response time on niche bugs slows because the specialists you used to email now have three products to look after. The docs stop referencing the old product name in half the places. And your account manager, if you had one, changes twice in six months.
We don't say this to trash the acquiring companies. Oxylabs' post-acquisition pitch for ScrapingBee is coherent and their engineering bench is deep. But if you bought ScrapingBee originally because you wanted the simplest possible API and no enterprise sales motion, the thing you actually bought was the independence, not the endpoint. When the endpoint stays and the independence goes, you kept the wrapper and lost the reason.
The same logic applies to any acquisition. You signed up for a set of tradeoffs the founders were willing to defend. New owners come with new tradeoffs. Sometimes better ones. Rarely the same ones.
The Full-Stack Pitch and Its Cost
The other consolidation story is vertical, not horizontal. Every serious player is racing to become a "full-stack platform" that bundles proxies, requests, browser rendering, AI extraction, dashboards, and MCP integration under one contract.
Browserless' State of Web Scraping 2026 predicts this continues: "the market will also continue consolidating as platforms expand into full-stack solutions, giving teams fewer fragmented tools to piece together." That framing is generous to the vendors. From the buyer's side, one contract also means one price schedule, one bug queue, one place to be down when something goes wrong, and one negotiation partner who now knows exactly how much of your infrastructure they own.
Full-stack has real advantages. Consistency of billing. Fewer integration seams. A single throat to choke when things go wrong. But it changes the answer to a specific question: when a small piece of the stack falls behind the state of the art, do you still have the option to swap that piece out? Full-stack platforms tend to say yes and then quietly discourage you from doing it.
How to Evaluate Vendors in the Consolidation Era
The old evaluation checklist was mostly technical: success rate, latency, proxy pool size, unit price. Those still matter, but they're the easy part. The hard part is now about intent.
Ask the vendor these five questions before you sign anything:
- Who owns the roadmap in 18 months? If the answer includes "we can't say" or "our parent decides," you have your answer.
- What were your last three pricing changes, and who did they help? A vendor that keeps changing tier names and quietly retiring the cheap plans is telling you which customer segment they actually want.
- Show me a bug fix from last month for a customer under $1,000/month. This filters for support quality on customers who aren't the important ones.
- What's your capital source, and what's it optimized for? PE-backed means growth to exit. Founder-owned means growth to independence. Both are legitimate. They're not the same.
- If we outgrow you, or if you get acquired, how do we leave? A vendor confident in the relationship will answer directly. A vendor uncomfortable with the question is telling you something.
None of these are trick questions. They just filter for whether you're buying a product or a portfolio.
Two related pieces we've published are worth reading alongside these: why proxy pool size stopped mattering in 2026 covers the vendor-marketing side of the same story, and the state of web data collection in 2026 sets the broader context we're working from.
What Comes Next
The mid-market will keep thinning through 2026 and into 2027. At least two of the current tier-2 API-first vendors will be acquired or wind down. The buyer who bought the "independent, developer-first, no-enterprise-motion" pitch in 2024 will need to make that choice again by 2027, from a smaller menu.
The upside: the vendors who stay independent through this cycle will be doing it on purpose. That's a signal worth paying attention to. Ask them why they didn't sell. If the answer is "we didn't need to," you probably found what you were looking for.
We build web data infrastructure at FourA. We're not going anywhere, and we didn't need $130 million to say that.