A browser inside a sandbox, not just a hosted browser
Lelantos runs a browser inside a full EU-native microVM, so the same sandbox that drives the page runs your code on what it collected. Browserbase is a hosted browser you connect to, then ship the data out to separate compute.
The spine of the move
Fusion: browse and compute in one place
A scraping agent does the whole job in one Lelantos sandbox: drive the browser to collect, then clean and analyse with Python in the same place. No second system, no data egress, no glue code.
EU-native by default
Sessions and the data they touch stay in the EU by default. Clean for GDPR.
Standard CDP plus native /rpc
Connect Playwright or Puppeteer over CDP, the same tools you already use, or use the lighter native NDJSON /rpc for high-level agentic actions and fewer round-trips.
Per-session microVM isolation
Each browser runs in its own Firecracker microVM, fully isolated, with your code right alongside it.
Lelantos vs Browserbase, the cells that matter
| Dimension | Lelantos | Browserbase |
|---|---|---|
| Product shape | browser inside a full agentic sandbox | hosted browser (BaaS) |
| Browse and compute in one place | yes, same sandbox | no, ship data to separate compute |
| EU data residency | native, default | available |
| Isolation | Firecracker microVM per session | dedicated VM per session |
| Protocols | native NDJSON /rpc + standard CDP | CDP only |
| Warm session (EU) | ~1.5 s (/rpc), ~1.9 s (CDP) | ~0.9 s |
The honest note
Browserbase creates a session a little faster than us (about 0.9 s vs our about 1.5 s native /rpc) and ships a mature browser-automation stack including Stagehand. If raw session-create speed or that ecosystem is what you need, Browserbase has it. We lead on browse-and-compute-in-one-place and EU residency.
Questions people ask
- Is Lelantos a Browserbase alternative?
- Yes, with a difference in shape. Browserbase hosts a managed browser you connect to over CDP. Lelantos runs a browser inside a full Firecracker microVM sandbox, so the same place that drives the page can also run your code.
- Can I run code in the same sandbox as the browser?
- Yes. On Lelantos you drive the browser and run Python or your own code on what it collected in the same sandbox. On a hosting service like Browserbase you ship the scraped data out to a separate compute system.
- Is the Lelantos browser isolated?
- Yes. Each Lelantos browser runs in its own Firecracker microVM, fully isolated. Browserbase uses a dedicated VM per session.
- How fast is a Lelantos browser session?
- From the EU, a warm session is usable in about 1.5 s over the native NDJSON /rpc protocol, or about 1.9 s over standard CDP. Browserbase creates a session a little faster at about 0.9 s.
- Does Lelantos work with Playwright and Puppeteer?
- Yes. Lelantos exposes standard CDP, so Playwright and Puppeteer connect with the tools you already use, plus a lighter native NDJSON /rpc for high-level agentic actions.
Browse and compute in one EU-native sandbox
$50 free credit. No credit card to start. A Firecracker microVM with a browser and your code in one place.