Browser infrastructure
ev3ry / lelantos vs the
browser-BaaS market.
The browser-infra vendors aren’t really our competitors — they’re substitutes for one layer of <Ev3ry/>. Where lelantos does compete head-to-head, here’s the honest scorecard: our durable edges, and where the incumbents are clearly ahead.
Snapshot 2026-06-22. Pricing and limits in this market change monthly — treat every figure as a point-in-time read and verify on the vendor’s own page.
The market in one table
Six providers, the dimensions that matter.
Engines, stealth, per-second billing, self-host, proxy, concurrency and regions — for a representative slice of the market. (We compete most directly with Browserbase, Steel and Kernel as the browser substrate.)
| Dimension | ev3ry / lelantos | Browserbase | Browserless | Steel | Kernel | Bright Data |
|---|---|---|---|---|---|---|
| Engines | Camoufox (stealth Firefox) + Chromiumchosen per Project | Custom Chromium | Chrome, WebKit, Firefoxwidest set among managed | Chromium | Chromium on lightweight VMs | Chromium (scrape-optimized) |
| Stealth / anti-bot | Stealth by engine (hardened Gecko)no managed CAPTCHA solver | Advanced Stealth (Scale) + auto CAPTCHA | Stealth mode + CAPTCHA solve | Built-in CAPTCHA solve + anti-bot | Managed stealth, all tiers | Website unlocker + auto CAPTCHAthe moat |
| Per-second billing | Yes — per-second-per-VM | Per browser-minute | Per 30-s “unit” | Per browser-hour | Yes — per-second by class | Per GB |
| One unified meter | Yes — one credit ledgerbrowser-sec + proxy + LLM + concurrency | Browser + proxy invoices | Units + proxy units | Hours + proxy + CAPTCHA | Per-class + proxy | Per GB |
| Self-host | Yes — same uni-browser backbone+ warm-pool autoscaler | No (managed only) | Yes — OSS + commercial | Yes — fully OSS core | No self-host path found | No (managed) |
| Proxy | Residential, managed or BYOlive per-VM byte metering | Built-in, ~$10–12/GB | Residential / DC, geo (ent.) | Residential, $5–10/GB | Configurable / BYO (Startup+) | 150M+ residential IPsindustry-leading scale |
| Concurrency | 1 → 25 (plan cap)cost control, not a ceiling | 3 → 250+ | 2 → 120 | 5 → 100 | 50 on-demand + 100 pool | “Unlimited” |
| Regions | Single region todayHetzner FSN1 (DE) | US-E/W, EU, UK (+APAC ent.) | SF, London, Amsterdam | Not pinned publicly | Not pinned publicly | Global (proxy footprint) |
| Positioning | Agentic web-data platformbrowser is one metered capability | Default AI-agent browser (Stagehand) | Mature self-hostable headless infra | OSS-core dev-friendly browser API | Sub-300ms agent browsers | Enterprise unblocking at scale |
Hyperbrowser, Cloudflare Browser Run, Anchor and ZenRows are profiled in the full research but omitted here for width. Steel and Kernel engine builds and regions are not pinned on their public pages [unconfirmed]; ev3ry multi-region is roadmap [unconfirmed].
The honest read
Where we win, where they lead, where it’s a wash.
No comparison page is worth reading if it only lists wins. Here are the real tradeoffs — including the gaps we’re still closing.
Where we win
- Stealth by engine, not just hardened Chromium. Nearly the whole market is Chromium-only. ev3ry ships a real second engine — Camoufox, a hardened Gecko build — chosen per Project, a different fingerprint surface Chromium-only anti-bot tuning doesn't anticipate. Only Browserless also offers Firefox, but not a purpose-built stealth one.
- True per-second billing in one ledger. Most of the market bills per-minute, per-30-s unit, or per-GB. Only Kernel and ev3ry meter per-second — and ev3ry folds browser-seconds, proxy GB, LLM tokens and concurrency into a single credit balance, so you see one currency instead of four invoices.
- Real self-host on the same backbone. The self-hosted daemon and the lelantos cloud are two deployments of one backbone behind a single adapter. Only Browserless and Steel offer credible self-host; we match them and add a warm-pool autoscaler that destroys each pod after one use — single-use isolation, no cross-tenant state.
- Owned, real-time proxy metering. lelantos owns the managed residential proxy and exposes per-VM byte counts live, so we bill exactly and can enforce accurate live cost ceilings — where competitor proxy usage is typically reconciled from a dashboard that lags. BYO proxy is unmarked-up.
- We sell the workflow, not the session. Every competitor here sells a browser. ev3ry sells an agentic web-data platform — projects, chat sessions, LLM-free replayable playbooks, schemas, scheduled runs — where the browser is one metered capability. A different, stickier game.
Where they lead
- No managed CAPTCHA solver. Browserless, Steel, Hyperbrowser, Bright Data, ZenRows and Anchor all ship automated CAPTCHA solving. We have stealth-by-engine but no solve service — for hard-gated targets that is a real functional gap, not just a marketing one.
- Proxy network scale. Bright Data (150M+ IPs), Oxylabs (100M+) and ZenRows (55M+) own enormous residential pools with deep geo-targeting. We ride a managed provider via lelantos — fine for agent work, not competitive for industrial geo-distributed scraping.
- Brand, funding, ecosystem, docs. Browserbase (Stagehand), Kernel ($22M, marquee logos), Steel and Hyperbrowser have public docs, SDKs, MCP servers and mindshare. We are effectively pre-launch in market awareness — Stagehand in particular is a moat we have no direct answer to yet.
- Regions. Browserbase (4+ regions), Anchor (US/EU/Asia/AU) and the proxy vendors (global) span the globe. lelantos cloud is single-region today (Germany) — a latency and data-residency limitation for now.
- Provisioning speed / scale claims. Hyperbrowser (sub-50 ms start, 10k+ concurrent) and Kernel (sub-300 ms) publish aggressive burst numbers. Our warm pool helps, but a default concurrency of 10 (pro) is an intentional cost-control choice that reads small next to “10,000+ concurrent.”
About even
- Automation interface. We standardize on NDJSON /rpc (higher-fidelity for Camoufox than a synthesized CDP bridge) and also expose CDP-over-WS. A deliberate choice, not an interoperability win — most SDKs speak Playwright/CDP, so we keep the CDP path solid for any BYO-framework story.
- Session persistence. We capture authenticated browser state for logged-in replay — comparable to Browserbase / Steel / Anchor session persistence. Live-view exists across the market and is on our roadmap.
- Free / OSS posture. Self-host is genuinely $0 because it hosts nothing, matching Steel / Browserless OSS. The cloud product is deliberately never free — the same local-free, cloud-paid funnel the agent vendors use.
Compare it on your own target.
Spin up a Camoufox or Chromium session, run it self-hosted or on lelantos cloud, and watch the per-second meter. 500 free credits, no card.