Our main project, in progress
Project Ghost is our main project at the moment. We are building an open-source desktop browser on Chromium around a clear direction: privacy protections should belong to the product, and accounts and browsing contexts should be separable without depending on a collection of extensions. This is product and engineering work, documented publicly on GitHub.
Ghost is a working name. The final product name will be chosen before a public release. The project is pre-alpha, covering foundations and early development builds. The documentation records a baseline Chromium build and an initial traffic audit of a Ghost development build. These are implementation milestones; they do not mean the browser is ready for public use or that the roadmap's features have already shipped.
Why we start with Chromium
Chromium gives us an existing foundation for rendering pages, web compatibility and browser security. We are not developing a new rendering engine. Our changes need to stay close enough to the upstream project for security updates to remain practical to integrate and verify.
That is why the roadmap puts building, distributing and updating the browser before more complex privacy features. Windows 11 x64 is the first target. macOS and Linux follow the alpha in the public plan. A browser requires continuous maintenance: producing a build that starts is an early step, while the ability to update it safely has to be demonstrated separately.
Separate identities and disposable sessions
A central direction is the separation of browsing identities. The proposed model allows several accounts on the same site in distinct contexts, with cookies, storage, permissions and network routes managed per identity. The documentation defines what needs to be isolated and what remains shared by design. Each boundary will need its own implementation checks.
Ghost sessions serve a different purpose: temporary contexts, isolated from each other, whose state the browser discards when they close. They aim to reduce persistent data and connections between sessions. This does not automatically hide an IP address, remove downloaded files or erase traces retained by the operating system. The privacy model states these limits explicitly.
Built-in protections, explained through mechanisms
The plan includes tracker and ad blocking inside the browser, removal of tracking parameters and fingerprinting protections. Blocking is designed around adblock-rust with EasyList and EasyPrivacy. For fingerprinting, the documentation proposes standardizing values where possible and deterministic per-site variation for selected hardware-derived data. These are implementation directions, not guarantees attributed to the current development build.
A per-page privacy report is also on the roadmap. Its proposed score uses a public formula and explains each deduction. It describes observable exposure during that page load, without claiming to assess what a site does with data on its own servers. Chrome Web Store extension compatibility is planned, while the core protections are intended to work independently of extensions.
What we check before a release
No telemetry is a goal that needs verification through actual traffic. The egress audit launches the browser with a fresh profile and compares network destinations with a reviewed allowlist. The first development audit recorded in the roadmap identified Chromium connections that must be removed or justified before the phase can close. Publishing these findings is part of how we track progress.
The next stages cover the branded build, distribution and updates, followed by network protections, sessions, identities and the privacy report. Each phase has exit criteria. Project Ghost aims to give people more control over browsing and local data; it does not promise anonymity against a network observer. The repository, privacy model and roadmap remain the places to follow what exists, what changes and what we plan to build next.
Sources and progress
Status checked against the public documentation on 30 September 2026. Follow the repository for subsequent changes.
Key takeaways
- Project Ghost is our main project in development.
- Pre-alpha: development builds are not a public release.
- Identities, sessions and protections follow a verifiable roadmap.
- Privacy claims need support from implementation and tests.