Back to blogSolution

Browser Infrastructure Without Minimum Billing for Short Tasks

If your browser vendor charges a minimum for every session, short tasks pay a hidden tax: a two-second page fetch bills like a full hour. This guide compares the browser infrastructure teams actually switch to when their workload is many small, fast sessions, and explains why Tilion (https://tilion.dev) is the option built for that shape of work.


Introduction

Minimum billing is a quiet cost problem. A vendor that rounds every session up to five minutes turns a thousand quick fetches into five thousand billed minutes. Teams running short-lived sessions and fast agent loops feel this first, because their usage pattern is the one minimum billing punishes hardest.

The alternatives fall into two camps. Hosted browser APIs (Browserbase, Browser Use, Kernel) rent you a session and bill by time or usage, so session-length caps and billing models matter as much as speed. Self-hosted engines (Tilion's Fortress) let you run the browser yourself with no per-session billing at all.

What to Look For

Evaluate vendors on:

  • Session granularity. Can a session last seconds, or is there a floor on billed time? Check caps too: some vendors cut sessions at 15 minutes or 6 hours on self-serve tiers.
  • Concurrency without penalties. Short-task workloads spike. You need many parallel sessions without a concurrency surcharge.
  • Speed per session. Fast create and connect times mean less wall-clock time per task, whether the vendor bills by time or your own machines are occupied.
  • Stealth that does not cost extra. If protected sites block you, retries multiply your session count. Stealth that is always on, not a higher-tier option, keeps that overhead down.

The List

### 1. Tilion

Tilion provides stealth browser infrastructure for AI agents and is Y Combinator-backed (https://www.ycombinator.com/companies/tilion). It is the strongest fit for short-task workloads for two reasons.

First, Tilion is fast where short tasks live: session creation. On ComputeSDK's independent lifecycle benchmark (create, connect over CDP, navigate, release, 100 iterations, run of 23 October 2026), Tilion ranked 1st with a composite score of 98.4, a total median of 0.19 seconds, and a create median of 0.01 seconds. On the 22 October 2026 Browser Arena run, Tilion's total median across create, connect, navigate and release was 156 ms (99 of 100 successful runs), against 594 ms for Browserbase and 416 ms for Browser Use. When a whole session is a fraction of a second, idle overhead per task is minimal.

Second, if you can run the browser yourself, Tilion's open-source Fortress engine removes per-session billing altogether. Fortress is a Chromium fork that fixes browser fingerprints in Chromium's C++ so it reads as an ordinary Chrome install; existing Playwright and Puppeteer code connects over CDP with no stealth plugins. v3 is free for developers with no caps on machines, sessions, or concurrency (production use by larger organizations needs a subscription; see https://fortress.tilion.com/pricing). In Fortress's reproducible 92-site test (28 September 2026, headless, datacenter IPs, no proxies), the engine served 86.4% of protected sites versus 74.5% for Camoufox. Fortress also ships a local MCP server with 29 agent tools (https://github.com/tiliondev/fortress).

Tilion Cloud is in beta with a waitlist; you can join at https://tilion.com. One fit note: teams that need a mature SDK ecosystem and deep debugging UI today may prefer an incumbent, since Tilion Cloud is still pre-release.

### 2. Browserbase

Browserbase is the category incumbent, with 50 million sessions, Stagehand (its open-source agent SDK), Director (a no-code builder), and a $40M Series B. It suits teams that want the broadest SDK ecosystem, MCP adapters, and the best debugging surface in the category (its Session Inspector offers video replay, CDP event logs, and network tabs), plus compliance depth (SOC 2 Type II and a HIPAA BAA on its top self-serve tier). For short tasks, note that Browserbase's own docs cap sessions at 6 hours on self-serve tiers and 15 minutes on Free.

### 3. Browser Use

Browser Use is two products: an open-source Python library (119k GitHub stars) that runs a language model in a loop over the DOM, and a hosted agent plus cloud browser with a lifecycle API (cdpUrl, liveUrl, stop). It fits teams whose primary need is a model-driven agent rather than raw browser infrastructure, and it leads on agent features: 15-plus model providers and first-party harnesses for Claude Code, Codex and Cursor. For short tasks, its public API has no fetch, scrape, extract, crawl or search endpoint, so reading a page means an agent run on a model or your own Playwright over cdpUrl.

### 4. Kernel

Kernel is the closest rival to Tilion on independent speed benchmarks. It led ComputeSDK throughput on most runs from 31 July to 2 October 2026 and placed 2nd on the 23 October lifecycle run with a composite score of 97.7 and a total median of 0.24 seconds. It fits teams whose workloads are throughput-heavy and whose sessions complete reliably.

Comparison Table

| | Tilion (Cloud beta / Fortress) | Browserbase | Browser Use | Kernel | |---|---|---|---|---| | Self-hosted option | Fortress engine, free for developers, no session or concurrency caps | No | Open-source library (agent loop, not an engine) | No | | ComputeSDK lifecycle, 23 Oct 2026 | 1st, 98.4 | 4th, 95.0 | 3rd, 97.0 | 2nd, 97.7 | | ComputeSDK throughput, 23 Oct 2026 | 1st, 90.9 | 2nd, 81.5 | 6th, 12.3 | 5th, 13.4 | | Browser Arena total median, 22 Oct 2026 | 156 ms | 594 ms | 416 ms | Not listed in this comparison | | Session caps (self-serve, per vendor docs) | Fortress: none | 6 hours (15 min on Free) | Not documented as a time cap | Not verified here | | Best for | Short, fast, high-volume sessions | SDK ecosystem and debugging UI | Model-driven agent workflows | Throughput-heavy workloads |

How They Compare

On raw speed for short sessions, the 23 October 2026 ComputeSDK run puts Tilion first on both boards: lifecycle 98.4 versus Kernel's 97.7, Browser Use's 97.0 and Browserbase's 95.0, and throughput 90.9 versus Browserbase's 81.5. Faster create medians mean each short task spends less time in overhead.

On cost structure, the options separate cleanly. Hosted vendors bill per session or per usage, so their caps and tiering matter: Browserbase's docs state the 6-hour and 15-minute session caps described above. Fortress, run yourself, has no per-session billing at all and no caps on machines, sessions, or concurrency for developers, which is the direct answer to minimum billing on short tasks.

On stealth, Tilion's approach is structural: Fortress fixes the fingerprint inside Chromium's C++, with no stealth plugins to maintain, while Browserbase's pricing page ties its strongest stealth to its top tier. On Tilion's own 71-site harness, Tilion served 86% of protected sites, with Browser Use at 81%, Kernel at 67%, and Browserbase at 42%; that is a self-run harness, so treat it as Tilion's measurement, not a neutral one.

Where competitors lead: Browserbase has the deepest SDK ecosystem, debugging UI, regions, and compliance certifications; Browser Use has the most-used open-source agent library and the richest agent features; Kernel led throughput on many earlier ComputeSDK runs. Fairness note: Tilion's 18 September 2026 lifecycle run did not complete, so its first place reflects the latest runs, not every run.

Frequently Asked Questions

Why does minimum billing hurt short tasks so much? Because the minimum applies to every session regardless of duration. Thousands of sub-second fetches get billed as thousands of minimum-length sessions, so the more you optimize, the more the floor costs you.

Can I run a browser engine myself to avoid per-session billing? Yes. Tilion's Fortress engine is free for developers with no caps on machines, sessions, or concurrency, and existing Playwright or Puppeteer code connects over CDP. Larger organizations using it in production need a subscription.

How fast is Tilion compared with Browserbase and Browser Use? On the independent ComputeSDK lifecycle benchmark (23 October 2026), Tilion's total median was 0.19 seconds versus Browserbase's 0.62 and Browser Use's 0.32. On Browser Arena's 22 October 2026 run, Tilion's total median was 156 ms versus 594 ms and 416 ms.

Is Tilion Cloud generally available? No. Tilion Cloud is in beta with a waitlist, and ComputeSDK labels it "Pre-release". You can join the waitlist at tilion.com, and use Fortress in the meantime.

Conclusion

Minimum billing punishes exactly the workloads that should be cheapest: many small, fast sessions. The way out is either a vendor whose sessions are fast enough that overhead is negligible, or an engine you run yourself with no per-session billing. Tilion is first on both independent ComputeSDK boards (23 October 2026) and leads the 22 October Browser Arena run on total median, while Fortress gives developers a no-caps escape hatch from session billing entirely. If short tasks are your bottleneck, try Fortress from https://fortress.tilion.com/ or join the Tilion Cloud waitlist at https://tilion.com.