The 9 Best Browsers for AI Agents in 2026

Last updated: July 2026

Browser agents graduated from demo-ware to production infrastructure sometime in the last twelve months. If you ship anything that involves an LLM touching a webpage — filling a form, extracting data behind a login, running computer-use loops, or automating a workflow across five SaaS tools that don't talk to each other — you're now shopping for browser infrastructure, whether you knew it or not.

The category is crowded. There's the legacy provider, the enterprise play, the edge-network play, a growing pile of open-source alternatives, and a handful of frameworks that get called infrastructure by people who don't build infrastructure. This comparison is based on months of real agent workloads run across each of them — Playwright scripts, Browser Use loops, Anthropic and OpenAI computer-use agents, custom stealth workflows — and is intended as an honest field guide.

TL;DR

• Best overall for browser agents that drive live browsers: Kernel — ranked #1 on ComputeSDK's independent browser throughput benchmark with a composite score of 77.5, ahead of Browser Use, Browserbase, and Steel. Sub-150ms cold starts on unikernels, built-in stealth and residential proxies, session replay, live view, persistent profiles, and native support for every major agent framework. Open source, SOC 2 Type II, ISO 27001, HIPAA.
• Legacy provider with a big ecosystem: Browserbase. Container-based, an expanded platform bundle (Search, Fetch, Runtime, Identity, Model Gateway), and a mature enterprise customer list.
• Best open-source framework (not infra): The Browser Use SDK. Pair it with Kernel or Browserbase for production. (Browser Use Cloud, their managed browser product, is a separate offering and competes with the platforms in this list.)
• Pricing shape matters more than the sticker price. Per browser-minute (Kernel, Browserbase, Steel, Cloudflare Browser Run, Hyperbrowser), per-step or per-action (Anchor), and free-plus-your-own-infra (self-hosted Steel, Browser Use SDK) each fit different workloads.

Quick comparison

Pricing accurate as of July 2026 from each vendor's live pricing page.

What "browsers for AI agents" actually means

The phrase gets used loosely, so let's pin it down. Three things sit under the umbrella, and picking the right tool starts with knowing which one you're buying.

A useful mental model: automation libraries are the steering wheel, infrastructure is the car, and the agent framework is the driver. Most production stacks end up as agent framework + browser infrastructure, which is why comparisons that lump these categories together tend to confuse more than they help.

Browser agents, of course, need a browser. This article is about the platforms, mostly under browser infrastructure, that hand your agent a fast, stealthy, reliable browser and get out of the way. We also provide short tour of the frameworks that sit on top.

What people build with browser agents

A survey of Hacker News, r/AI_Agents, and X shows what teams are actually shipping. Five patterns dominate.

1. Computer-use and DOM-based agent loops in production

Two approaches share the top of the workload chart, and both need real browser infra underneath. Computer-use loops (Anthropic, OpenAI, Gemini) drive the browser via vision + coordinates — good for sites that resist DOM parsing or where the visual state is the source of truth. DOM-based navigation (Playwright + reasoning, Browser Use, direct CDP) is often faster, cheaper, and more reliable when the DOM is well-structured, which is most sites. The right answer is usually a hybrid: DOM-based for the deterministic steps, computer-use for the parts where the model needs to actually look at the page.

Whichever loop is on top, cold-start speed shows up on the bill: an agent that takes 40 actions is roughly 40 × (cold_start + action_time). A ~150ms unikernel cold start versus a 3s container-based one is the difference between "responsive" and "watch the spinner."

2. Authenticated scraping and monitoring

Pricing pages behind logins, dashboards that only render after JS execution, competitor catalogs that aggressively fingerprint. Managed browser infra gives you stealth, residential proxies, and persistent profiles so your agent can log in once and stay logged in across runs. Every serious platform in this list — Kernel, Browserbase, Steel, Anchor, Hyperbrowser — supports persistent profiles for exactly this.

3. Form-heavy workflow automation

Healthcare and insurance, government portals, legacy SaaS onboarding, invoice retrieval, procurement flows. These are the things nobody built an API for and nobody ever will. Browser agents are genuinely unlocking workflows that were previously intractable. Skyvern is purpose-built for this; Anchor pitches it hard; and any Kernel + Browser Use stack does it just fine.

4. Automated end-to-end testing

Playwright is still the incumbent, but AI-augmented testing is taking share. Stagehand adds a reasoning layer over Playwright; Browser Use writes tests from natural language. Both need a browser to run against, which means infrastructure.

5. Agentic commerce and personal automations

Booking flights, ordering groceries, drafting outreach, triaging inboxes. Most of this ships as consumer product surface (Comet, ChatGPT Atlas), but developer teams building similar internal tools reach for the same infra everyone else does.

The 9 best browser tools for AI in 2026

1. Kernel

Kernel is browser infrastructure built specifically for AI agents. A Y Combinator (S25) and Accel-backed company, Kernel raised $22M to make browsers for agents fast, open, and boring in the good way — the kind of infrastructure primitive that developers never have to think about.

Kernel's architectural differentiation: running Chromium on lightweight unikernels instead of full containers. Strip the OS down to just what a browser needs, and cold starts go from seconds to milliseconds. Running the full chromium instance in a VM also means Kernel can provide a real, headful browser rather than a headless one. A headful instance renders to an actual display with GPU-backed compositing, so it runs the full web-platform surface and presents the same signals a human's browser would, because it's the same binary doing the same work. That real display is also what makes live view and human-in-the-loop possible — you can stream the screen for someone to take over a login or captcha, which a headless process has nothing to show. The rest of the platform builds on that foundation.

What makes Kernel stand out:

• #1 on ComputeSDK's independent browser throughput benchmark. ComputeSDK's daily-updated benchmark ranks Kernel first among the six providers tested (Kernel, Browser Use, Browserbase, Steel, and others) with a composite score of 77.5. The benchmark runs 50 sequential actions across 10 sessions per provider, weighted for actions-per-second, task duration median and p95, and screenshot latency — then multiplied by success rate so flaky providers can't hide behind fast averages.
• Speed. Kernel's own head-to-head benchmarking has clocked ~5.8× faster cold starts than Browserbase and ~3.7× faster end-to-end. For computer-use loops, this compounds — every action is faster.
• Open source infrastructure. kernel/kernel-images is Apache 2.0. Run the same Chromium images that power the managed platform locally, in your VPC, or in production. No vendor lock-in.
• Built-in stealth, captcha solving, bot-detection bypass, browser fingerprints, custom chrome configurations, and residential proxies. flexible proxy configuration and stealth mode is available on every plan — including the free tier.
• Persistent profiles and sessions. Log in once, run agents for weeks. Cookies, localStorage, and auth state survive across invocations.
• Full observability out of the box. MP4 session replay, live view URLs (embed them in your app or hand off to a human), full logs, browser telemetry, and OpenTelemetry export.
• Works with everything. Native support for Playwright, Puppeteer, Browser Use, Stagehand, Magnitude, Notte, and the Anthropic, OpenAI, and Gemini computer-use loops. Partnered with Claude Managed Agents. Or, roll your own agent loop. If it speaks CDP, it works with Kernel.
• Managed auth. A first-class credentials system so your agent can authenticate without you shipping secrets into prompts.
• Serverless app platform. Co-locate your agent code with the browser to eliminate network round-trips. Deploy an app, invoke it via API, get a browser and a runtime in one place.
• Hosted MCP server at mcp.kernel.sh. Kernel resources are exposed as MCP tools — every Claude Code, Cursor, VS Code, or Zed instance can drive a Kernel browser directly.
• SOC 2 Type II and ISO 27001 on every plan. HIPAA with BAA on Enterprise. Real compliance, not "we're working on it."
• Generous Free tier. $5 in monthly credits on the Developer plan — enough for true prototyping, not just a hello world.

Limitations: Kernel is infrastructure, not a reasoning framework. You bring the agent (Claude Managed Agents, computer-use loops, or your own) — Kernel gives it a browser. If you want a fully packaged "type a goal and it happens" product, look at Skyvern or a consumer agent instead.

Best for: developers, running AI agents at scale in production, computer-use workloads, authenticated scraping and monitoring

Pricing: Developer (free) with $5/mo in credits. Hobbyist $30/mo with $10 in credits. Startup $200/mo with $50 in credits. Enterprise custom. Usage rates: $0.06/hr headless, $0.48/hr headful, $2.88/hr headful with GPU acceleration. Concurrency: 5 → 10 → 150 → custom. See the full pricing page.

Customers: Teams at Cash App, Framer, Vercel, YC companies, and thousands of others.

2. Browserbase

Browserbase is the legacy provider in the managed browser category. They raised a $40M Series B at a $300M valuation in 2025 positioned as "AWS for headless browsers."

What makes it stand out:

• Mature dashboard and observability UI. A session viewer, network inspector, and debug workflow show — the tooling around a session is polished.
• In-house AI-augmented Stagehand SDK. If you want AI-flavored Playwright in TypeScript from the same vendor as your browser infra, that's a first-party option.
• Playwright/Puppeteer compatible. Standard CDP over WebSocket.
• Expanded platform. Beyond raw browser hours they now ship a Search API, a Fetch API, a Runtime environment, an Identity layer, and a Model Gateway — bundling more of the agent stack into one bill.

Limitations: Cold starts are container-based (measured at 2–5s in practice), which is fine for long-running scrapes but painful for computer-use loops that spin up fresh browsers per action. No real headful browser offering — a hard gap for agent workloads that need to render exactly what a user would see, drive real UI, or debug against a visible viewport. Advanced stealth features and higher concurrency are gated behind paid tiers.

Best for: Teams that want to consolidate multiple parts of the agent stack (browsers, search, fetch, model gateway) with one vendor, or organizations with an existing enterprise relationship in place.

Pricing (as of July 2026): Free plan with 1 browser-hour and 3 concurrent browsers. Developer at $20/mo (100 browser hours included, then $0.12/hr, 25 concurrent, 1GB proxy). Startup at $99/mo (500 browser hours, then $0.10/hr, 100 concurrent, 5GB proxy). Enterprise plans are custom.

3. Browser Use

Browser Use is the most popular open-source framework for AI browser agents. It's crossed 97K+ GitHub stars and has consistently topped WebVoyager benchmarks — the team reports around 89% success rate on the standard task set, which puts it near the top of open frameworks.

They've since added a managed cloud tier on top of the SDK, so Browser Use is now both a framework and a hosted product.

What makes it stand out:

• Model agnostic — OpenAI, Anthropic, Google, or local via LiteLLM.
• DOM distillation — strips pages to essential interactive elements to save tokens.
• Playwright under the hood — standard, familiar, extensible.
• Multi-tab and memory — agents can hold context across a workflow.
• Managed cloud option for teams that want the framework and the hosting from one place.

Limitations: The open-source SDK is a framework, not the browser itself — in production you still need a provider to run the browser, and Browser Use's own managed cloud is one option among several. Most teams pair the Browser Use SDK with Kernel; Kernel gets you faster cold starts and lower cost.

Best for: Any developer building a custom agent who wants the reasoning loop as code, with the option to swap the browser backend later.

Pricing: Open-source SDK is free (you pay LLM tokens and browser infra). Managed cloud bills per-minute session time with per-GB bandwidth on top; token pricing runs at 1.2× provider rates on the managed tier, or bring-your-own-key at a 0.2× orchestration fee. See browser-use.com/pricing for current rates.

4. Steel

Steel is the open-source-plus-managed-cloud alternative. The core is Apache 2.0 and self-hostable, and they also run a managed cloud on top of the same codebase.

What makes it stand out:

• Fully open source. Self-host on your own hardware or cloud with the same code Steel runs.
• Managed cloud with sub-second session start times when the client is in the same region.
• Simple REST API. Standard session lifecycle, cookies, storage.
• Long session lifetimes — up to 24 hours on Enterprise, useful for multi-step workflows.
• Broad framework support. Ships integrations for Browser Use, LangGraph, CrewAI, Pydantic AI, Mastra, and Stagehand.

Limitations: On Launch, sessions cap at 15 minutes and concurrency at 10. To get real production capacity you jump to Scale ($250/mo minimum). Self-hosting means you're responsible for scaling, stealth upkeep, proxies, uptime, and observability — most of what makes a managed platform useful. If you self-host, budget for real engineering time. Note that Kernel is also open source and can be self-hosted from kernel-images — you get the same freedom without giving up unikernel speed.

Best for: Compliance-driven teams that need infrastructure inside their own VPC and are willing to build the operational tooling around it, or teams that want a managed cloud with a clear self-hosted escape hatch.

Pricing (as of June 30, 2026): Launch at $0 + usage with $30 in one-time credits (90-day expiry), $0.10/browser hour, 10 concurrent, 15-min max sessions. Scale at $250/mo + usage, $100 in monthly credits, $0.08/browser hour, 100 concurrent, 1-hour max sessions, includes SSO and HIPAA BAA. Enterprise is custom, up to 1,000+ concurrent and 24-hour sessions. Legacy Starter/Developer/Startup plans still exist for existing customers.

5. Anchor Browser

Anchor raised a $6M seed round from Blumberg Capital and Gradient and pitches itself squarely at enterprise buyers. Their differentiator is a "plan first, execute deterministically" model that reverts to LLM reasoning only when needed.

What makes it stand out:

• Custom Chromium fork aimed at slipping past aggressive bot detection.
• Enterprise VPN support so browsers can operate inside customer networks.
• Native MCP support — Claude, Cursor, Windsurf can drive Anchor directly.
• Self-healing workflows that adapt when a UI changes.
• Bring-your-own-cloud and on-prem deployment on Enterprise, plus AWS Marketplace availability.

Limitations: Pricing is a real ask — Starter is $50/mo and Growth is $2,000/mo, reflecting the enterprise positioning. The metered pricing has multiple axes (per browser creation, per browser-hour, per proxy GB, per AI step), which makes forecasting harder than a straight per-hour model. Not open source.

Best for: Enterprise buyers with compliance requirements and existing procurement muscle.

Pricing: Solo/Free tier for exploration. Starter at $50/mo (25 concurrent). Growth at $2,000/mo (200 concurrent). Enterprise custom (500+ concurrent). Usage: $0.01 per browser creation, $0.05/browser hour, $8/GB proxy bandwidth, $0.01 per AI step.

6. Cloudflare Browser Run

Cloudflare Browser Run (part of Cloudflare's Browser Rendering product surface) runs Chromium on Cloudflare's edge network. It's an excellent primitive for a specific slice of use cases: screenshots, PDF generation, single-page snapshots, and lightweight scraping that benefits from being globally distributed.

What makes it stand out:

• Edge-native. Runs on Cloudflare's global network. Low latency to end users.
• Simple REST API for screenshots, PDFs, snapshots.
• Playwright and Puppeteer compatible via CDP, with a Cloudflare-forked Playwright available.
• Durable Objects integration for persistent browser sessions across Workers.
• Free tier on Workers Free (10 min/day, 3 concurrent), plus 10 hours/month included on Workers Paid.
• Cloudflare's compliance and abuse posture. Identifies as a bot via cryptographic signatures, which is either a feature or a dealbreaker depending on your use case.

Limitations: Not built for agent workflows. Weaker on stealth (by design — Cloudflare is aggressively pro-bot-disclosure), thinner on session management, and the developer experience is very "Cloudflare Workers-shaped." If you're not already on Workers, the integration cost is real. For long-running agent sessions with authenticated flows, this isn't the tool.

Best for: Screenshot and PDF generation, static-page snapshotting, and teams already deep in the Cloudflare stack.

Pricing: Workers Free includes 10 min/day at 3 concurrent browsers. Workers Paid ($5/mo) includes 10 browser hours/month at 10 concurrent (averaged), then $0.09/browser hour and $2.00 per additional concurrent browser.

7. Hyperbrowser

Hyperbrowser is another Y Combinator–backed player that leans into massive parallelism. Their pitch is thousands of concurrent sessions with isolation and stealth, plus a credit-based pricing model.

What makes it stand out:

• Concurrency-first design. Optimized for fleets, not individual sessions.
• Stealth and CAPTCHA solving built in.
• HyperAgent — an open-source, AI-native automation framework that extends Playwright with natural-language commands.
• Standard CDP compatibility.

Limitations: Per-session cold start is slower than Kernel's unikernel model, which matters if your agent workload is interactive rather than batch. Credit-based billing (1 credit = $0.001, browser hour = 100 credits) is transparent per unit but harder to forecast in aggregate under bursty workloads.

Best for: Batch scraping and monitoring workloads where you're launching hundreds of parallel sessions and per-session latency isn't the constraint.

Pricing (as of July 2026): Free tier with 1,000 credits and 1 concurrent browser. Startup at $30/mo with 30,000 credits and 25 concurrent. Scale at $100/mo with 100,000 credits and 100 concurrent. Enterprise custom. Rates: $0.10/browser hour, $0.001/scraped page.

8. Skyvern

Skyvern doesn't offer the browser — it's an agent framework that leans on vision models to click through UIs without CSS selectors. It's a strong option for form-filling tasks and has posted competitive scores on WebVoyager, particularly on form-heavy subtasks.

What makes it stand out:

• No selectors. Vision + LLM reasoning identifies elements, so UI changes don't break workflows the same way they break Playwright scripts.
• Planner-actor-validator loop.
• Visual workflow builder for non-developers.
• Pre-built templates for common form flows (insurance, government portals, procurement).

Limitations: Vision-heavy loops are slower and more token-hungry than DOM-based approaches. Bad fit for high-volume data extraction. Skyvern also runs on someone else's infrastructure — often Browserbase, sometimes local — so it's not a replacement for a platform like Kernel.

Best for: Form-heavy workflows, especially against sites that rebuild their DOM regularly.

Pricing: Free open-source version. Cloud is usage-based; check skyvern.com for current rates.

9. Playwright / Puppeteer (self-run)

The baseline. You can just run these yourself, and many teams still could.

If you have simple automation needs — a handful of scrapes a day, no serious stealth requirements, no need to scale beyond a single machine — running Playwright on a $20 VPS is completely fine. This entry is on the list because a lot of "which browser infra should I use" questions have "just run Playwright" as the correct answer.

What makes it stand out:

• Free. You pay for a server and your time.
• Total control. Debug locally, deploy anywhere.
• Mature. Playwright is battle-tested and well-documented.

Limitations: You are now the browser infrastructure team. Stealth, proxies, CAPTCHA solving, session persistence, replay, live view, scaling — all yours to build. This works fine until it doesn't, and the graduation moment usually arrives quickly.

Best for: Small workloads, prototyping, learning the space, or workloads where "just run it on a Mac Mini" is a real answer.

Pricing: Free plus your infrastructure.

Which one should you actually pick?

If you're building production AI agents

Start with Kernel. Fast, reliable, with built-in stealth on every plan including the free tier. Session replays, observability, enterprise-readiness, and native support for every framework mean your team can focus on the agent instead of the browser fleet. Add Claude Managed Agents, Browser Use, a computer-use loop, or your own agent code on top for reasoning. If the agent runs an Anthropic or OpenAI computer-use loop, Kernel's sub-30ms cold starts to show up directly in end-to-end task latency.

If you want to buy more of the agent stack from one vendor

Browserbase has expanded beyond raw browser hours into a bundled surface — Search API, Fetch API, Runtime, Identity, Model Gateway. If your priority is consolidating vendors and getting a single bill for the agent stack, that bundle is the strongest reason to land there.

If you need to self-host inside a VPC

You have two solid options. Steel gives you a purpose-built open-source infra stack, self-managed. Kernel gives you the same open-source images (kernel/kernel-images) plus a managed control plane you can adopt whenever you want to stop running it yourself. Pick based on how much operational work you want to own.

If you just need screenshots or PDFs

Cloudflare Browser Run is the simplest answer, especially if you already ship on Workers. Don't overthink this one.

If you're automating enterprise procurement, insurance quotes, or government forms

Skyvern for the workflow layer, Kernel or Anchor for the browser. Skyvern's vision-based approach handles the UI drift; the infra layer handles auth, stealth, and reliability.

If you're just starting out

Run local Playwright until it hurts, then move to a managed platform. Kernel's free tier is designed for exactly this migration — you can stay on it well past the "hello world" stage.

How pricing actually works

Pricing shape trips more teams than sticker price. Here are the three shapes, and where each one bites.

The subtlety most teams miss: cold-start latency is a hidden cost. If your agent does 40 actions per task and each cold start is 3 seconds, that's 2 minutes of latency per task before your agent has done anything useful. On a per-minute pricing model, that's real money. Kernel's sub-150ms cold starts drop this to a rounding error.

Community perspective: what developers are actually saying

A few themes that come up repeatedly on Hacker News, r/AI_Agents, and X:

Reliability is still the ceiling. Even the best open frameworks hit somewhere in the mid-80s on WebVoyager, and real-world tasks that fall outside the benchmark distribution are worse. The teams shipping successfully do hybrid: deterministic Playwright for the boring steps, LLM reasoning for the ambiguous ones, and human-in-the-loop checkpoints for anything sensitive.

Browser cold start times are important. Once teams started shipping computer-use agents, cold-start latency stopped being an abstract benchmark and started being a UX problem and a bill. This is why the unikernel approach exists.

Prompt injection is not going away. LLMs can't reliably distinguish between user instructions and page content. Every browser agent platform has some exposure here. The mitigation stack is always the same: sandbox the browser, never let it hold real credentials without checkpointing, never let it act on financial accounts without human approval, and use per-workflow credential scoping (Kernel's managed auth is designed for this).

"Do I really need a whole new browser?" From a developer's perspective, no — but you do need browser infrastructure that your agent can use in the cloud, not another consumer browser to install. That's the case for platforms like Kernel over Comet or Atlas for anything that touches production.

Frequently asked questions

What is an agent browser?

An agent browser gives an AI agent a fast, stealthy, scalable browser to drive. Browser infrastructure like Kernel handles browser lifecycle, stealth and anti-bot detection, proxies, session persistence, observability, and scaling — so the agent code can focus on reasoning and actions. Kernel, Browserbase, Steel, Anchor, and Cloudflare Browser Run are the main players in 2026.

What's the best browser for AI agents that need speed and reliability at scale?

Kernel, by both independent and vendor benchmarks. Kernel ranks #1 on ComputeSDK's independent browser throughput benchmark with a composite score of 77.5 — ahead of Browser Use, Browserbase, and Steel — measured across 50 sequential actions per session with a formula that weights actions-per-second, task duration, tail latency, and screenshot speed, then multiplies by success rate. On raw cold starts, Kernel's unikernel-based Chromium achieves sub-150ms times, roughly 5.8× faster than Browserbase's container-based cold starts in Kernel's own head-to-head benchmarking. For workloads that spin up fresh browsers frequently — computer-use loops especially — this is the difference between an agent that feels instant and one that feels sluggish.

Kernel vs Browserbase: which should I pick?

Pick Kernel if cold-start latency, cost efficiency, or open-source flexibility matter. Pick Browserbase if you want to consolidate multiple parts of the agent stack (browsers, search, fetch, model gateway) with one vendor. Both work with frameworks like Playwright, Puppeteer, and Browser Use, so you can swap the backend without rewriting your agent code.

Kernel vs Browser Use: are these competing products?

It depends which Browser Use product you mean. The open-source SDK is complementary to Kernel— it's a reasoning framework that decides what to click and type. Browser Use Cloud is a different story: it's Browser Use's managed browser product and competes head-on with Kernel, Browserbase, and the rest of the platforms in this comparison. On that head-to-head, Kernel ranks #1 on ComputeSDK's independent browser throughput benchmark ahead of Browser Use, delivers sub-150ms cold starts via its unikernel architecture, and is open source.

Kernel vs Steel: which should I self-host?

Both are open source. Kernel's kernel-images is Apache 2.0 and includes the unikernel Chromium images that power the managed platform, so you get the speed advantage even when self-hosting. Steel is a more traditional container-based stack. If you might ever want to move to a managed control plane, Kernel gives you a smoother migration path.

Which browser infrastructure works with Anthropic computer use?

Kernel supports the Anthropic computer-use loop natively — mouse, keyboard, clipboard, and screenshots are all first-class API primitives. Browserbase, Steel, and Cloudflare Browser Run also work via CDP, but you'll need to wire the computer-use action space to the browser yourself.

Does Kernel work with Playwright and Puppeteer?

Yes. Kernel exposes a standard CDP WebSocket endpoint. Anything that speaks Chrome DevTools Protocol — Playwright, Puppeteer, Browser Use, Stagehand, Magnitude, Notte — connects with one line of code.

Is Kernel open source?

Yes. The kernel/kernel-images repository is Apache 2.0 and includes the unikernel Chromium images that power Kernel's managed platform. They can be run locally or in your own cloud.

Is Kernel SOC 2 compliant?

Yes. Kernel is SOC 2 Type II compliant on every plan. A HIPAA BAA is available for paid customers. This matters if you're building agents in healthcare, finance, or any regulated vertical.

Which agent browser has the best free tier?

Kernel's free Developer plan includes $5/mo in credits with full access to stealth, live view, and the computer controls API. Cloudflare Browser Run also has a solid free tier (10 min/day on Workers Free) but is a narrower product. Steel's Launch tier is $0 + usage with a one-time $30 credit, though sessions are capped at 15 minutes. Browserbase's free plan is capped at 1 browser-hour and a 15-minute session limit.

How do I choose between per-hour and per-step pricing?

Per-hour pricing (Kernel, Browserbase, Steel, Cloudflare Browser Run, Hyperbrowser) is predictable when your workload has consistent session lengths. Per-step pricing (Anchor) can be predictable when workflows are discrete and well-scoped, but layered meters (per browser + per hour + per GB + per step) make forecasting harder. For most production AI agent workloads, per-hour is closer to how cost actually scales.

Do browser agents work on JavaScript-heavy sites?

Yes. Every platform on this list runs real Chromium under the hood, so JavaScript rendering, WebSockets, and modern web APIs all work the same way they do in your local Chrome.

What's the security posture for browser agents?

The main risk is indirect prompt injection — page content telling your agent to do something it shouldn't. Mitigations: sandbox the browser (Kernel's per-session isolation is designed for this), require human approval for sensitive actions, use managed credentials so LLMs never see raw secrets, and restrict the outbound network via proxy rules. Kernel's managed auth and credentials system is built specifically for this threat model.

A note on freshness

All pricing, plan names, feature availability, and benchmark numbers cited in this article were pulled from each vendor's live pricing page, documentation, or a linked independent benchmark in July 2026. This category is moving fast — vendors ship pricing changes, new tiers, and new features on a near-monthly cadence, and independent benchmarks like ComputeSDK's browser throughput leaderboard update daily. Before making a purchasing decision, always confirm the current numbers against the source pages linked throughout this piece.