Isolated microVM browsers, EU-native
Each Lelantos browser runs in its own Firecracker microVM, where Browserless co-locates sessions on shared workers. Lelantos is EU-native, fuses browse and compute, and is faster warm (~1.5 s /rpc vs ~2.0 s).
The spine of the move
Per-session microVM isolation
Each browser runs in its own Firecracker microVM, fully isolated. Browserless co-locates sessions on shared workers, where, in their own docs, concurrent sessions compete for CPU and RAM.
Fusion: browse and compute in one place
Drive the browser to collect, then clean and analyse with Python in the same sandbox. No second system, no data egress, no glue code.
Faster warm and EU-native
A warm session is usable in about 1.5 s over native /rpc versus Browserless about 2.0 s, and sessions stay in the EU by default.
Standard CDP plus native /rpc
Connect Playwright or Puppeteer over CDP, or use the lighter native NDJSON /rpc for high-level agentic actions and fewer round-trips.
Lelantos vs Browserless, the cells that matter
| Dimension | Lelantos | Browserless |
|---|---|---|
| Isolation | Firecracker microVM per session | shared workers, sessions compete for CPU/RAM |
| 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 |
| Warm session (EU) | ~1.5 s (/rpc), ~1.9 s (CDP) | ~2.0 s |
| EU data residency | native, default | available |
| Protocols | native NDJSON /rpc + standard CDP | CDP only |
The honest note
Browserless is a focused, mature browser-hosting service with a long track record and a large pool of shared workers, which suits high-concurrency CDP fleets where per-session VM isolation is not a requirement. If that is your shape, it fits. We lead on isolation, the fusion of browse and compute, EU residency, and warm session speed.
Questions people ask
- Is Lelantos a Browserless alternative?
- Yes. Browserless hosts browsers on shared workers you connect to over CDP. Lelantos runs a browser inside a full Firecracker microVM sandbox, so you can drive the page and run your code in the same place.
- 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 Browserless 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. Browserless co-locates sessions on shared workers, where concurrent sessions compete for CPU and RAM.
- Is Lelantos faster than Browserless?
- Yes, warm. From the EU, a Lelantos warm session is usable in about 1.5 s over the native NDJSON /rpc protocol, versus Browserless at about 2.0 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.
Isolated, EU-native browsers with compute built in
$50 free credit. No credit card to start. A Firecracker microVM per session, browser and code together.