When an enterprise picks a browser-infrastructure vendor, it is betting on more than today's feature list. Browser automation programs run for years. The vendor's roadmap decides whether the platform underneath you keeps deepening in the direction you need, or shifts toward a different customer. The most reliable way to read a roadmap is to look at what the vendor has actually shipped, in order, in their own words.

Here is that exercise for Browserbase, using their own announcements, followed by where Anchor's roadmap points. Both directions are rational. They are just different bets, and buyers should know which one they are making.

The Browserbase release timeline

June 17, 2025: Director, launched alongside the $40M Series B. Director is a no-code application that lets non-developers automate the web by describing tasks in plain language (browserbase.com/blog/introducing-director; press release). The tagline was "web automation for everyone." This is an end-user product, and the funding announcement was built around it.

October 8, 2025: Secure Agentic Autofill with 1Password. A partnership that delivers credentials from a 1Password vault into Browserbase sessions at runtime, with a zero-knowledge model so secrets never pass through the AI (1Password press release). This is a genuine security improvement for agent workflows, delivered through a partner integration.

March 11, 2026: the Fetch API. Send a URL, get page content back, no browser session involved, priced around $1 per 1,000 pages (browserbase.com/changelog/browserbase-fetch-api). Expanded on May 21, 2026 with markdown and JSON output and a 5MB cap.

March 17, 2026: the Search API. A web search endpoint for agents, powered by Exa, returning ranked URLs so agents know where to navigate (browserbase.com/blog/search). Browserbase describes the intended flow: Search discovers where to go, Fetch retrieves content, browsers handle deeper interaction.

April 5, 2026: the Stagehand Model Gateway. Unified LLM access across OpenAI, Anthropic, and Google inside the Stagehand framework (browserbase.com/changelog).

June 30, 2026: Browserbase Agents. A managed service where you describe a goal in natural language, make one API call, and get structured results with no infrastructure to run (browserbase.com/blog/introducing-browserbase-agents). The launch language is explicit about the ambition: "one agent covers 200 portals instead of 200 scripts," and the product "improves as you run it, the first step toward agents that get better largely on their own."

Reading the pattern

Classify each release by who it serves. Director and Agents are application-layer products: they perform the automation for you. Search, Fetch, and the Model Gateway assemble a full agent stack, and Browserbase's own homepage now describes the platform as headless browsers plus identity, search, fetch, sandboxed runtime, and a model gateway behind a single API key (browserbase.com). Stagehand releases and features like MP4 session recording (July 15, 2026) continue serving developers, so the infrastructure work has not stopped. But every marquee launch since the Series B has moved up the stack, from browsers as a primitive toward complete agents as the product.

This is a sensible strategy. Agents that do the whole job command more value than sessions billed by the minute, and Browserbase deserves credit for executing it well. The question for an enterprise buyer is narrower: if you are embedding browser infrastructure into your own product or internal systems, is your use case the vendor's main character for the next five years?

Where Anchor's roadmap points

Anchor Browser is built for the buyer who needs the infrastructure layer itself, and its releases concentrate there:

• Deployment flexibility. Cloud, bring-your-own-cloud, and on-premise deployment, including running in your own cloud environment with your own inference provider (anchorbrowser.io).

• Compliance. SOC 2 Type II, ISO 27001, GDPR, CCPA, and HIPAA with BAA availability, verifiable at Anchor's trust portal (trust.anchorbrowser.io).

• Credential handling. OmniConnect, Anchor's end-to-end authentication infrastructure for computer-use agents, built in partnership with 1Password, plus managed identities and secure autofill documented at docs.anchorbrowser.io.

• Data controls. Customizable retention policies and a zero-data-retention mode on enterprise plans (anchorbrowser.io).

• Operational depth. Multi-region deployment across EU, Asia, and Australia, built-in enterprise VPN routing for reliable access to geo-specific and login-gated sites, 500+ concurrent browsers, dedicated support channels, and implementation support (anchorbrowser.io).

None of this is glamorous, and that is the point. It is the roadmap of a company whose customer is the enterprise platform team, and whose releases compound in that direction.

The takeaway

Both companies publish their trajectories in plain sight. Browserbase's releases since mid-2025 build toward complete, managed agents for a broad audience. Anchor's build toward browser infrastructure an enterprise can deploy in its own environment, certify to its auditors, and hand credentials to safely. Read the timelines, decide which curve your program needs to be on, and pick the vendor whose next five releases are for you.