Cloud Platforms Subsidize Browser Services
Browserbase
The key pressure from cloud platforms is not just cheaper compute, it is cheaper distribution. Cloudflare and Microsoft can slip browser automation into products developers already use, bill it through the same account, and in Microsoft’s case fold it into Azure testing workflows and credits. That makes browser sessions easier to buy, even if browser automation itself is not the main thing the customer came for.
-
Cloudflare attached Browser Rendering to Workers, so a team already deploying edge code can add screenshots, page interaction, or scraping without adopting a separate vendor. Cloudflare later set pay as you go pricing at $0.09 per browser hour, which is low enough to turn the browser into an add on service rather than a standalone budget line.
-
Microsoft’s offer sits inside Playwright, the standard browser automation framework for many developers, and supports up to 50 parallel browsers. Because it lives inside Azure’s broader testing stack, Microsoft can use browser testing to pull workloads into Azure, not just to maximize margin on each browser minute.
-
Pure play vendors still win where reliability, observability, and workflow tooling matter more than raw session price. Browserbase adds session replay, live human takeover, proxy controls, stealth features, and no code tooling, which matters for customers running production automations instead of occasional tests.
This pushes the market toward a split. Cloud platforms will absorb commodity browser capacity, while independent browser clouds move up the stack into agent orchestration, debugging, security, and repeatable business workflows. The durable revenue pool will come from making flaky web tasks run reliably at scale, not from renting a bare browser by the hour.