Frequently asked questions

When is it coming?

Our first Alpha for macOS and Linux is coming later this year. It will be aimed at developers and early adopters.

How many people are working on the browser today?

We have a small full-time engineering team working on Ladybird, supported by community testing, bug reports, security reports, and technical feedback.

What's the hiring plan?

Our team size is stable for now. We will revisit hiring as the project's needs evolve.

We will strive to maintain 18 months of runway at all times.

What do you mean by "not a fork of an existing engine"?

The focus of the Ladybird project is to build a new browser engine from the ground up. We don't use code from Blink, WebKit, Gecko, or any other browser engine.

For historical reasons, the browser uses various libraries from the SerenityOS project, which has a strong culture of writing everything from scratch. Now that Ladybird has forked from SerenityOS, it is no longer bound by this culture, and we make use of 3rd party libraries for common functionality (e.g. image/audio/video formats, encryption, graphics, etc.), including some of the same libraries used by other browsers.

Will Ladybird work on Windows?

Our CI already builds and tests the JavaScript engine on Windows. Full browser engine support on Windows will follow in time.

Our full-time engineers are currently focused on macOS and Linux, with Windows support planned for a later stage of the project.

Will Ladybird work on mobile devices?

Mobile platforms are not a current focus. More effort will be put into Android and iOS once the desktop versions are in a good state.

How can you be "independent" if you have sponsors?

All sponsorships are in the form of unrestricted donations. Board seats and other forms of influence are not for sale, and sponsors have no say in our technical roadmap or product direction.

Why build a new browser in C++ when safer and more modern languages are available?

Ladybird began as part of SerenityOS, a C++ project, so the codebase started and largely remains C++. We have since adopted Rust as our C++ successor language and are incrementally porting subsystems to Rust. See our announcement post for more details.