Galileo
The people, the engineering process, and the public record behind the work. This is the project that brings the engine and browser together.
Why Galileo existsGalileo / built from Servo
We are a small European team using AI to move open-source development faster without handing over the engineering decisions. Our first project is Galileo Engine and Galileo Browser, built from Servo. The next goal is a genuinely usable alpha; compatibility, security, and release readiness still have to be earned.
01Work in progress
How Galileo fits together
Galileo is the project. Galileo Engine is the technical foundation, derived from Servo. Galileo Browser is the desktop product built on top. Each name has one clear job.
The people, the engineering process, and the public record behind the work. This is the project that brings the engine and browser together.
Why Galileo existsOur Servo-derived engine work. This is where integration, web compatibility, media, extensions, and the tests around them are developed.
Inside the engineThe desktop product built on Galileo Engine. It brings the shell, navigation, profiles, settings, and user experience into one browser.
See the browserFrom Servo to Galileo
Galileo does not begin from a blank file. It begins with Servo and more than a decade of work by Mozilla Research, maintainers, and the open-source community.
A browser engine in Rust, with a real rendering pipeline, serious standards work, and an architecture designed to be embedded and extended.
Maintainers — later with the Linux Foundation — develop Servo into a serious embeddable engine. Galileo inherits that work and credits it directly.

Galileo Engine develops that foundation toward a desktop product. The team owns the review, testing, and every claim made about the result.
Where the work stands
The current build is useful for engineering and testing. Compatibility, security, reliability, and packaging still have to pass before Galileo Browser can be offered as an everyday browser.
The project starts from Servo and keeps that technical ancestry explicit.
The shell, engine integration, compatibility work, extensions, and release tooling are being developed together.
An alpha comes after the published gates, not after a date chosen for presentation.
The method
AI can carry volume and shorten iteration. The team remains responsible for architecture, review, testing, evidence, and the decision to release.