The archive · Developer & Business Tools · Technical decision · 2023-2026
Lightpanda bets a from-scratch Zig browser, not Chromium, will power AI web automation
Lightpanda builds a from-scratch Zig headless browser and a managed-cloud business around it, betting AI agents leave Chrome; Show HN Jan 2025, 34.4k stars
Lightpanda
What the business is
Lightpanda builds an open-source headless browser for AI agents and automation, with a managed cloud, browser-as-a-service business model: a from-scratch Zig engine (no Chromium, WebKit or rendering) exposing a CDP server that Puppeteer and Playwright clients can drive.
How it started
Francis and Pierre wrote Lightpanda from scratch in Zig over roughly two years before sharing it, and the Show HN post explains why: at their previous company they scraped millions of web pages per day with Chrome headless, which was powerful but heavy on CPU and memory, with high overhead for scraping at scale, building AI agents, or automating websites. They asked what a browser that only did what headless automation absolutely needs would look like - an HTTP loader, an HTML parser and DOM, a JavaScript runtime and just enough Web APIs - with no graphical rendering at all. The company's stated business model was a managed cloud, browser-as-a-service, initially powered by Chrome and meant to transition to Lightpanda as Web API coverage grew; the Show HN went up on 2025-01-24.
What happened
The Show HN drew 319 points and 137 comments on 2025-01-24, with commenters questioning whether the memory advantage would survive as Web API coverage grew toward Chrome's; the team answered that skipping graphical rendering should keep the gap significant. The project then moved fast: by the 2026-09-05 snapshot the repository had 9,213 commits, 34.4k stars and 1.6k forks, plus nightly Homebrew and Arch packages, official Docker images, and a benchmark across 933 real pages claiming about 9x faster execution and roughly 16x less peak memory than headless Chrome (123MB versus 2GB for 100 pages). It also grew an agent mode that drives the browser from plain-English tasks through Anthropic, OpenAI, Gemini, Mistral, Hugging Face or local models, exports reusable PandaScript that runs without an LLM, and ships a native MCP server with HTTP transport and per-session isolation.
No ending yet — it is still running.
Background
Lightpanda is the wager that AI agents and large-scale scraping will not run on Chrome. In the Show HN post, Francis and Pierre said they had built the browser from scratch in Zig for roughly two years before sharing it, and explained the origin: at their previous company they scraped millions of web pages per day with Chrome headless, which was powerful but heavy on CPU and memory, with high overhead for scraping at scale, building AI agents, or automating websites.
Their answer was a browser that only does what headless automation absolutely needs - an HTTP loader, an HTML parser and DOM, a JavaScript runtime, just enough Web APIs, and no graphical rendering - announced as 'Show HN: Lightpanda, an open-source headless browser in Zig' on 2025-01-24. The thread drew 319 points and 137 comments, with critics pressing whether the memory edge would survive as Web API coverage grew toward Chrome's. The founders also described a managed cloud, browser-as-a-service model, meant to shift from Chrome to Lightpanda as coverage grew.
By the 2026-09-05 snapshot the repository had 9,213 commits, 34.4k stars and 1.6k forks, nightly Homebrew and Arch packages, official Docker images, and a benchmark across 933 real pages claiming about 9x faster execution and roughly 16x less peak memory than headless Chrome. The project has since added an agent mode that drives the browser from plain-English tasks through multiple model providers and exports PandaScript that runs without an LLM, plus a native MCP server, while still describing itself as in beta.
What has to be true
- The team had lived the cost firsthand: a previous company scraped millions of pages a day with Chrome headless, so the problem was theirs to solve, not a market they were guessing at
- JavaScript made plain HTTP fetching obsolete for automation, while Chrome's graphical rendering was useless headless - leaving an obvious slice of the product to cut away
- Writing from scratch in Zig kept the engine small: the project's own benchmark put peak memory near 123MB versus 2GB for headless Chrome on 100 pages
- Staying wire-compatible with the Chrome DevTools Protocol meant Puppeteer and Playwright users could try Lightpanda without rewriting their automation
What can be applied
A costly incumbent that ships far more than your workload needs invites subtraction: build the minimal engine, keep existing tooling wire-compatible, and price the coverage gap as the real risk
Aftermath
As of 2026-09-05 Lightpanda still describes itself as in beta, with stability and Web API coverage improving and crashes still possible; the repository publishes daily Web Platform Test results. The open-source browser is distributed through nightly Homebrew and AUR builds and Docker images, while the managed cloud business described at launch is not detailed in the public materials reviewed here - no funding or revenue figures appear in them.
Sources
- Lightpanda Browser - headless browser in Zig
- Show HN: Lightpanda, an open-source headless browser in Zig
spotted an error? The archive wants to know.
Your turn
You just read one. Describe what you are building, and see who is betting on the same thing.
Free account · 3 free questions · no card