TL;DR

Ladybird is a pre-alpha web browser being built from scratch — not a Chrome or Firefox fork [website].
BSD-2-Clause licensed, backed by a 501(c)(3) non-profit with no ads, no search deals, no data monetization [website].
61,362 GitHub stars, 8 paid full-time engineers, targeting an alpha for Linux and macOS in 2026 [website][README].
You cannot use this as your daily browser today. It handles basic pages and can manage GitHub issues, but that’s roughly the ceiling right now [5].
The project is adopting Rust as the C++ successor (announced Feb 2026) [website].
For non-technical founders: this is a bet, not a product. Bookmark it, don’t install it.

What is Ladybird

Ladybird is a new web browser with its own engine. Not a reskin of Chromium. Not a Firefox fork with a different logo. A genuinely new engine written from scratch, descended from work that started inside SerenityOS in 2018 and split into its own project in 2022 [5][website].

The technical shape of the project is straightforward once you look at it:

A multi-process architecture — the main UI process talks to separate WebContent renderer processes (one per tab), plus out-of-process ImageDecoder and RequestServer helpers for security isolation [README][5].
Core libraries inherited from SerenityOS: LibWeb (rendering), LibJS (JavaScript engine), LibWasm, LibCrypto/LibTLS, LibHTTP, LibGfx, LibUnicode, LibMedia, LibCore, LibIPC [README].
Runs on Linux, macOS, and Windows via WSL2. Windows is explicitly not a priority. Mobile (Android/iOS) is explicitly not a priority until desktop is stable [README].

The stated rule: no code from other browsers. Ladybird will use third-party libraries for codecs, crypto, and graphics (it already does) but will never ship another browser engine under the hood [website]. That distinction matters because it separates Ladybird from every “new browser” that is really just Chromium with a paint job.

The project is led by Andreas Kling, funded through the Ladybird Browser Initiative — a 501(c)(3) non-profit. Sponsors include Guillermo Rauch (Vercel), Mitchell Hashimoto (HashiCorp co-founder), Paul Copplestone (Supabase CEO), and The Primeagen [website]. Sponsorship tiers go from $1K Copper up to $100K Platinum, and the project explicitly states that board seats are not for sale and all donations are unrestricted [website]. They target 18 months of runway at all times [website].

Why people are watching it

Honest answer: there is not much third-party review coverage to summarize. Most of the written-up analysis comes from developer publications, not end-user reviewers — because there is no end-user product yet.

The substantive third-party writeup is daily.dev’s “What is Ladybird? Everything we know about the new browser & web engine” [5], which walks through architecture, origin, and a comparison table putting Ladybird against Chrome, Firefox, and Safari on open-source status, privacy focus, ad-blocking, non-profit backing, and custom engine. On that table Ladybird is the only one checking all five boxes [5].

Beyond that, the signal is community interest: 61,362 GitHub stars, 62 likes on AlternativeTo, and a sponsor list full of people who usually know what they’re looking at [website][4]. On AlternativeTo, the top “alternatives” listed for Ladybird are Firefox and Brave [4] — which is a fair read on what problem people think Ladybird is trying to solve.

What people are actually watching for is simpler than most browser news:

A web engine that isn’t owned by Google, Mozilla, or Apple.
A browser with no ad business attached to it.
An independent rendering engine that other projects could eventually build on.

Whether Ladybird gets there is the open question. The team is 8 full-time engineers plus volunteers [website]. That’s small for a browser. Chromium has hundreds of full-time engineers. The honest framing is that Ladybird is a generational project — it will take years, and it might not make it. That’s why people watch it instead of using it.

Features: what the engine actually does

Ladybird today is a browser that renders pages. Here’s the concrete list of what the engine is built to do, based on primary sources:

Architecture

Per-tab sandboxed renderer (WebContent process) [README][5].
Out-of-process image decoding (ImageDecoder) and networking (RequestServer) for security isolation [README][5].
Inter-process communication via LibIPC [README].

Web platform

HTML, CSS, and JavaScript via LibWeb and LibJS [README].
WebAssembly via LibWasm [README].
TLS/crypto via LibCrypto and LibTLS [README].
HTTP via LibHTTP [README].
Graphics and font rendering via LibGfx and LibUnicode [README].
Media handling via LibMedia [README].

Design intentions stated by the project

Built-in ad blocker [5].
Third-party cookie blocking as a default design goal [5].
No telemetry, no search deals, no monetization path through the user [website].

Practical capability today

The daily.dev writeup notes that Ladybird can currently handle basic web tasks and was able to manage GitHub issue and PR browsing as a real-world test [5]. That’s roughly where the ceiling is right now. It is not a browser you load Gmail in. It is not a browser you do your banking in.

What it does not have yet: the long tail of web-platform features that took Chromium 15+ years to accumulate. Extensions, sync, password management, profiles, DRM-protected video, full media codec coverage — these are future work, not current state.

Pricing: cost reality

There is no pricing table to compare because browsers don’t charge money. The honest comparison is what you pay in non-cash cost:

Browser	Cash cost	What you actually pay with
Chrome	$0	Browsing data → ad targeting
Edge	$0	Browsing data → ad targeting
Safari	$0	Locked into Apple ecosystem; search deal with Google
Firefox	$0	Mostly clean; funded partially by Google search deal
Brave	$0	Crypto/ads model (opt-in)
Ladybird	$0	Your time to build from source [website][README]

Ladybird’s cost story is unusual: because there are no official binaries for end users yet, the real cost is the time and technical skill needed to build it from source on Linux or macOS [README]. That’s not a dollar cost, but it’s a genuine cost — and it’s the reason this browser is currently only usable by developers.

The project’s funding model avoids the usual trap. Because the Ladybird Browser Initiative is a 501(c)(3) non-profit funded by unrestricted donations with board seats not for sale [website], there is no built-in pressure to monetize the user. Compare that to Firefox, where Mozilla’s revenue is heavily tied to a default-search deal with Google — that arrangement works, but it shapes incentives.

If you want to support the project, sponsorship tiers are Copper $1K, Bronze $5K, Silver $10K, Gold $50K, Platinum $100K per year [website]. These are organizational tiers, not subscriptions.

Deployment reality check

This is the section non-technical founders should read twice.

There is no installer. The browser has no stable release. To run Ladybird today, you clone the GitHub repo, install a long list of build dependencies (CMake, a recent Clang or GCC, Qt on some targets, plus platform-specific pieces), and compile from source [README]. On Linux and macOS this is an hour or two if everything cooperates and much longer if it doesn’t. On Windows you need WSL2, and Windows is not a priority target [README].

It will break. This is a pre-alpha. Pages crash. Layout breaks. JavaScript-heavy sites may not work. Video may not play. Logins may fail. This is not a bug — this is the project being exactly as mature as it says it is.

The alpha is targeted for 2026, for Linux and macOS only [website]. Even that alpha is explicitly aimed at developers, not general users. A public release suitable for a non-technical user is multiple years away.

What this means practically:

If you are a founder reading this because you want to switch browsers this quarter — Ladybird is not an option. Period.
If you want to get it running to play with, you need a developer on your team, or you need to be comfortable with a terminal and a compiler.
If you want to support the mission, the actionable step right now is to donate or sponsor, not install [website].

Pros / Cons

Pros

Truly independent engine — not a Chromium or Gecko reskin [website].
Non-profit governance, no ad/data monetization model baked in [website].
Clear multi-process security architecture from day one [README][5].
BSD-2-Clause licensed — commercially usable, forkable [4][website].
Real funding and real full-time engineers (8 paid) [website].
Notable technical sponsors (Rauch, Hashimoto, Copplestone) suggest serious people take it seriously [website].
Adopting Rust as C++ successor — sensible modern direction for a browser [website].
Small but growing contributor base; 61,362 GitHub stars [website].

Cons

Pre-alpha. Not suitable for daily use by anyone, including developers [5][website].
No official binaries — build from source only [README].
Windows is not a priority; mobile is not a priority [README].
8 full-time engineers is small for a browser project. Chromium has hundreds.
Thin third-party review coverage — most writeups are developer-focused, not user-focused.
Long tail of web-platform features (extensions, sync, DRM video, full codec coverage) is future work.
2026 alpha is for Linux and macOS and is explicitly developer-targeted [website].
Roadmap to a general-user release is measured in years, not months.

Who should follow this / who shouldn’t

Follow it if:

You’re a developer who cares about web-engine diversity.
You’re a privacy-focused user who is willing to wait 2–3+ years for a genuinely independent option.
You run an open-source or developer-tools company and are thinking about who to sponsor.
You want to contribute to a browser and don’t want to wade into Chromium’s or Firefox’s governance.

Don’t follow it (yet) if:

You need a browser to switch to this quarter. Use Firefox, Brave, or LibreWolf.
You’re a non-technical founder looking to replace Chrome for your team. This is not that product. It may become that product in a few years.
You need extensions, sync, password management, or reliable video playback today.
You want a polished UI. Ladybird today is function over finish.

The honest line: Ladybird is a project to watch, donate to, and maybe contribute to — not a browser to install on your laptop in 2026.

Alternatives worth considering

Since Ladybird is not shippable to end users yet, here’s what to actually use while you wait. On AlternativeTo, the top-listed alternatives are Firefox and Brave [4], and that matches the practical answer:

Firefox — The closest thing to Ladybird’s mission that actually ships today. Independent-ish engine (Gecko), open source, works everywhere. Funded partially by the Google search deal, which is the main asterisk. If you want “not Chromium, not Safari, available right now,” this is it.
LibreWolf — A Firefox fork with privacy defaults turned up. Removes telemetry, disables Pocket, hardens settings. Same engine as Firefox. Good pick if you like Firefox but don’t trust Mozilla’s defaults.
Brave — Chromium-based, so the engine diversity argument doesn’t apply. But it ships with aggressive tracking and ad blocking built in, and the default experience is cleaner than Chrome’s. Crypto/ads model is opt-in. Good pick if you want Chromium compatibility without Google’s defaults.

None of these three give you what Ladybird is trying to give you — a non-Chromium, non-Gecko, non-WebKit engine with no corporate parent. That combination does not exist in a shippable browser today. That’s the gap Ladybird is trying to fill.

Bottom line

Ladybird is the most credible attempt in a decade to build a new web browser from scratch. Non-profit governance, clear technical architecture, real funding, serious sponsors, and a stated rule against taking code from other browsers [website][README][5]. On paper, it’s the browser a lot of people have been asking for.

In practice, it is pre-alpha software that you cannot use for your actual work, built by a team of 8 paid engineers, targeting a developer-only alpha for Linux and macOS in 2026 [website]. A general-user release is years out.

For a non-technical founder, the right action is: bookmark the site, consider donating if the mission matters to you, and keep using Firefox, LibreWolf, or Brave in the meantime. For a developer, the right action is: try to build it, file issues, and decide whether you want to contribute.

Ladybird is not a tool you adopt. It’s a project you back. That’s a perfectly good answer — just don’t confuse it with the other thing.

Sources

[4] AlternativeTo — Ladybird listing: https://alternativeto.net/browse/all/?tag=unix
[5] daily.dev — “What is Ladybird? Everything we know about the new browser & web engine”: https://daily.dev/blog/what-is-ladybird-everything-we-know-about-the-new-browser-and-web-engine
[website] Ladybird official site: https://ladybird.org
[README] Ladybird GitHub repository: https://github.com/LadybirdBrowser/ladybird

Note on source coverage: The provided third-party articles [1], [2], and [3] were a holiday cottage listing, a ladybird insect house product page, and a Montessori nursery — none about the browser. This review is based on [4], [5], and primary sources only. Thin review coverage is itself an honest signal about where the project stands.