Browserbase raises preemptive Series B led by Notable Capital, launches Director AI for web automation
Jun 17, 2025 with Paul Klein
Key Points
- Browserbase raises over $50 million in preemptive Series B led by Notable Capital, with CRV and Kleiner Perkins participating, as CEO Paul Klein targets $100 million ARR before closing the funding chain.
- The company launches Director.ai, a tool that converts plain-language prompts into repeatable browser automation scripts, positioning itself as the infrastructure layer for developers building agents in platforms like Lovable and v0.
- Browserbase is negotiating partnerships with authentication providers including WorkOS, Clerk, and Okta to solve anti-bot friction by proving bots act on behalf of verified human users, framing itself as an arbiter of trustworthy agents.
Summary
Browserbase has closed a preemptive Series B led by Notable Capital (formerly GGV Capital), with CRV doubling down and early seed investor Pler Perkins also participating. Glenn Solomon of Notable Capital led the deal after an existing relationship dating to the company's earliest days. Every Browserbase funding round to date has been preemptive. The company has now raised over $50 million in total. CEO Paul Klein IV has set an internal milestone of $100 million ARR before considering the funding chain retired.
Director.ai and the Web Automation Stack
Alongside the raise, Browserbase launched Director.ai, a consumer-facing tool that lets users prompt in plain language and receive a repeatable automation script capable of clicking buttons, filling forms, and downloading files across any website. The product targets developers building in vibe-coding environments like Lovable, v0, and Bolt. Example use cases include pulling earnings call schedules from NASDAQ and monitoring political prediction markets on Kalshi.
Director sits at the top of a three-layer stack Klein describes as analogous to Vercel and Next.js. The infrastructure layer is Browserbase itself. Above it is Stagehand, an open automation framework that generates browser automation functionality natively within Browserbase. Director then generates Stagehand code at the application level. The strategy is deliberate: owning the framework creates stickiness and first-party integration advantages that pure infrastructure cannot.
B2B vs. Consumer Agentic Use Cases
Klein draws a clear line between where consumer and enterprise agentic browsing will live. Consumer automation, such as booking flights, will route through platforms with existing distribution, likely Google or Apple on-device AI. B2B automation is the Browserbase opportunity. The example cited is Ramp using a browser agent to collect invoices from supplier websites that lack direct API connections, then routing them through bill pay. Klein positions Browserbase as the "integration of last resort" for agents encountering the billions of websites that will never have dedicated APIs.
The Good Bot Problem and Partnership Strategy
Anti-bot infrastructure is a structural risk and a strategic opportunity. Browserbase is building partnerships with authentication and CAPTCHA providers including WorkOS, Clerk, Stitch, and Okta, all of which maintain significant CAPTCHA presence online. The thesis is that agent authentication, proving a bot is acting on behalf of an authenticated human user, will neutralize most anti-bot friction. Klein frames this as "proof of humanhood" for bots, and points to activity at Agentic OAuth as a near-term catalyst.
Klein explicitly positions Browserbase as a potential arbiter of verified, KYC-cleared bots, vouching for customers with defined use cases and restricted domain access to the broader anti-bot ecosystem. The Plaid parallel is instructive but bounded: Plaid could build integrations for a tractable number of banks, while the web has billions of sites, meaning browser-based fallback remains necessary regardless of how many direct integrations exist.
Competitive Moat Against Hyperscalers
On the risk of cloud platform competition, Klein acknowledges infrastructure commoditizes but argues the moat sits in developer experience and framework ownership. AWS, Azure, and GCP have not demonstrated the ability to build developer-loved frameworks or the application layers that generate them. The stack from infrastructure to framework to application generator is the durable differentiator, and Klein is betting the hyperscalers will not execute credibly at all three layers.