Private by design. Secure by default. Open source.
Development status: GhostWeb VPN is under active development. The current codebase and development builds are not yet presented as production-ready privacy infrastructure.
Privacy-focused browser routing and VPN tooling for endpoints you control.
GhostWeb VPN is the network-privacy project in the GhostWeb ecosystem.
| Project | Purpose | Status |
|---|---|---|
| GhostWeb Signal | Privacy-focused Android messaging and calling | Public project |
| GhostWeb VPN | Browser, Android and desktop network protection | Under development |
| GhostWeb AI | AI client, agents and delivery tooling | Public project |
| GhostOS | Privacy-focused custom Android ROM | In development |
Project hub: https://ghostweb.bot.cd/
GhostWeb VPN is being actively developed and verified. Architecture, clients, privacy behavior, CI and packaging may change before a stable release.
Do not rely on a development build as your only privacy or security control. A release appearing in GitHub does not by itself mean the project has reached production-ready status; stable status will be stated explicitly when the relevant functionality has been validated.
- Clear connection and disconnection state
- Fail-closed / kill-switch behavior
- Endpoint, public-IP and region verification
- Browser leak hardening, including WebRTC-related controls
- Android system-wide VPN integration
- Desktop client and packaging
- User-controlled or explicitly configured endpoints
- CI, security scanning and reproducible release workflows
The repository contains work toward multiple GhostWeb VPN surfaces:
- Browser: Chromium/Manifest V3 routing and privacy controls.
- Android: native system-wide VPN work using Android VPN APIs and tunnel components.
- Desktop: cross-platform client and packaging work.
The intended model favors endpoints that users explicitly configure or control rather than silently depending on an unspecified bundled network.
Security-sensitive behavior must be treated as unverified until it has passed the relevant implementation, build and runtime gates. In particular, kill-switch behavior, leak prevention, routing correctness and endpoint verification require real-world validation before a stable release claim.
Never expose unauthenticated proxy listeners publicly. Verify your endpoint configuration and network behavior independently when testing development builds.
cd android
gradle assembleDebug
gradle assembleReleaseSuccessful compilation is one development gate; it is not equivalent to verification of network/privacy behavior.
cd desktop
npm install
npm run distFor local development, clone the repository, load the unpacked extension in a Chromium-based browser, configure an endpoint you control, and independently verify routing and leak behavior.
The project uses CI for source checks, linting, security analysis, packaging and Android builds. Development continues through the gate sequence build → test → first real failure → fix → rebuild → verify.
Before GhostWeb VPN is marked stable, the project should verify at minimum build integrity, connection lifecycle, routing behavior, fail-closed behavior, DNS/WebRTC leak handling where applicable, endpoint/IP verification and release artifacts.
Issues, improvements, security reports, documentation updates and pull requests are welcome.
Questions, feedback or support requests: support-ghostweb@proton.me
GhostWeb VPN · network privacy under active development 👻