Nicheloom visits: 59,403 all-time · 7,634 in the last 7 days

The opportunity tracker for new startups.

Today: 1,884 launches · Niche of the day: specialized calculation tools · See what launched today →

Browser4

an open-source browser engine for agents and concurrency

Get picks like this daily. Today's launch numbers, the top launches, AI and tech news, and a daily opportunity pick, straight to your inbox.

Want to reach these readers? Sponsor an issue.

Hi HN,I’d like to share an open-source project we’ve been working on for a while: Browser4.The motivation came from a recurring frustration: most browser automation tools (Playwright, Selenium, Puppeteer) are excellent for human-written scripts, but start to show friction when used as a core execution layer for AI agents or at very high concurrency.So instead of building “another wrapper around Playwright”, we experimented with a different direction: designing a browser engine where AI agents are first-class citizens.### What Browser4 isBrowser4 is a browser automation engine built on native Chrome DevTools Protocol (CDP), with a focus on:* Coroutine-safe concurrency (designed to run many browser sessions in parallel)* Agent-oriented APIs (navigation, interaction, extraction as composable actions)* Hybrid extraction: ML agent driven extraction + LLM extraction + structured selectors + an SQL-like DOM query language (X-SQL)* Low-level control without Playwright-style abstraction overheadIt’s written in Kotlin/JVM, mainly because we needed predictable concurrency behavior and long-running stability under load.The project is fully open-source (Apache 2.0).### What it’s not* It’s not a drop-in Playwright replacement.* It’s not a no-code RPA tool.* It’s not “LLM magic” — LLMs sit outside the browser engine.Browser4 intentionally stays close to the browser execution layer and leaves planning/reasoning to external agent loops.### Current use cases we’re testing* Large-scale web data extraction* Agentic workflows (search → navigate → extract → summarize)* Price / content monitoring with frequent revisits* High-concurrency crawling where browser startup and context switching are bottlenecksOn a single machine, we can sustain very high daily page visits, though we’re still validating benchmarks across different workloads.### Open questions (where I’d love feedback)* For agentic systems, does it make sense to bypass Playwright entirely and work closer to CDP?* Where do you see the biggest pain points when combining LLMs with browser automation today?* Is JVM a reasonable choice here, or is Python still the better tradeoff despite concurrency limits* What abstractions would you want in a browser engine built for AI agents?### Links* GitHub: https://github.com/platonai/browser4* Website (light overview): https://browser4.ioHappy to answer technical questions or hear criticism — especially from people running browser automation or agent systems in production.Thanks for reading.

HN · launched Dec 13, 2025 · 7 upvotes (top 64%) · 0 views

Niche: headless browser automation infrastructure · 31 launches, 1 in the last 7 days · Explore this niche →

Category and tags

  • Horizontal
  • Dev tools
  • Developer
  • AI feature
  • Hobby / open-source project

Visit website ↗ Source listing ↗

Could you build this?

No Building an independent browser engine capable of parsing modern HTML, CSS, JavaScript, and handling DOM execution with high concurrency from scratch is an immense systems engineering feat far beyond vibe coding.

What it would actually take: A custom browser engine requires an HTML5/CSS parser, layout/box tree engine, a JavaScript runtime engine (like V8 or QuickJS), and a custom rendering/event loop designed for concurrent headless execution. Teams spend tens of thousands of engineering hours building and maintaining compliance with evolving W3C web platform specs.

Discussion

6 comments analyzed.

Concerns raised: Rate limiting and bot detection triggered by aggressive parallelization, Session isolation and state pollution between concurrent agents, Token-based pricing model inefficient for agent-based workflows

Feature requests: X-SQL based extraction for high-complexity multi-entity data pipelines, ML agent-driven hybrid extraction capabilities, Sequential execution with realistic timing delays for rate-limit compliance

Competitors

Other products that read as similar to this one : 1579 launches clear the similarity bar, closest 8 shown.

Attention rank: #987 of 1580 (itself plus its competitors, highest first, normalized so YC and Product Hunt are compared fairly).

Launched 43 days after the earliest competitor.

The niche, labels, vibe code rating and competitor comparison on this page are analysis by Nicheloom. If you use them, please credit nicheloom.com. How you may use our data.