WARDEN.
Windows · Android · iOS · open source

WARDEN.

Read everything. Give nothing.

A desktop browser built for the people who audit networks: ad and tracker filtering that cannot be talked around, no cookie jar unless you say so, and the operator tools a security team actually needs — a real shell, a mail client, unified messaging, and Scry, which takes a live site apart and hands back a rebuildable project. The Android and iOS builds carry the same private surfaces in a Capacitor shell.

Windows installer · latest build on GitHub

WARDEN shield icon
Cookie jar
None by default
Enforcement layers
Five, main process
Workspaces
Seven surfaces
Session storage
Memory only
Screen lock
Ctrl + \ · Windows password
Updates
Automatic from GitHub
01

Built for the audit, not the ad economy

Most browsers ask you to trust a settings page. WARDEN makes the refusal structural: requests are cancelled before they leave, headers are rewritten in the main process, and the cookie store is guarded rather than merely configured. The same application is also the workbench — inspect, clone and rebuild what you are looking at without opening four other tools.

▚

Blocking that argues in code

Adblock-Plus syntax over a seeded EasyList-compatible engine, plus HTTPS upgrades and a page-level fingerprint shim. Every decision is a TypeScript function with unit tests, not a checkbox with a promise.

⌘

The console is part of the browser

A real PTY shell, IMAP/SMTP mail, and Slack, Teams, Discord and friends each in their own isolated session — docked beside the page you are reading instead of buried in tabs.

◈

Scry: deconstruct, then rebuild

Attach over CDP or to WARDEN's own tab. Get a recon report, a static clone with rewritten scripts, a Vite + React scaffold, or an "innovate" build that replaces the original behaviour instead of copying it.

◎

Encrypted by default, honest about the rest

DNS over HTTPS from a resolver you choose, a fresh in-memory session per tab, and an egress tunnel through your own SOCKS5 or HTTPS endpoint — labelled direct when there is none. Camera and microphone can be softened, mosaicked, silhouetted or blocked before a page ever sees them.

◼

Cover the screen, keep the shift

Ctrl + \ blurs the page into an opaque lock and disables everything underneath until the Windows password checks out, with an idle timer for the desk you walked away from. Packaged builds update themselves from signed release metadata on GitHub.

02

Seven workspaces, one window

Each surface is a first-class pane with its own state; nothing is a web page pretending to be an app.

WorkspaceWhat it is
BrowseChromium with the full privacy stack: popups blocked by destination, permissions denied, scrollbars that belong to the dark theme.
TRENCHAn embedded shell and ssh client with a SHELL / SSH toggle: a real PTY, scrollback, and the system ssh so host keys, passphrases and agent forwarding work normally.
RelayIMAP and SMTP mail, multiple accounts, remote content withheld until you ask for it.
ConcourseUnified messaging: Slack, Teams, Discord, WhatsApp, Telegram, Element, Mattermost — one isolated session each.
ScryRecon, Clone and Innovate against any reachable target, local tab or remote debug port. The name is the verb — looking into a page to see what is hidden.
GenieA built-in assistant over your own gateway, with tool calls streamed into the UI.
PolicyEvery switch with its enforcement point stated, plus admin palettes and the compatibility list.
03

The privacy model, layer by layer

Electron has no Chrome-style cookie policy switch, so the guarantee is assembled from five independent layers. A site has to get past all of them, and the browsing session is created without the persist: partition — quit WARDEN and there is no cookie database to find.

LAYER 01 Request interception Matched ad and tracker requests are cancelled before transmission; top-level http:// is upgraded first.
LAYER 02 Request headers Cookie is deleted unless the host is allowlisted, Referer is trimmed to origin, DNT and Sec-GPC are asserted.
LAYER 03 Response headers Set-Cookie is stripped for every host the policy rejects, along with Report-To and NEL beacons.
LAYER 04 Cookie store guard session.cookies.set is wrapped to refuse disallowed writes, with a sweep on navigation and on demand.
LAYER 05 Page-level lock The content preload redefines Document.prototype.cookie and removes cookieStore, so page script cannot create one either.
ALWAYS Everything else Permissions denied outright, webview attachment blocked, popups judged by destination, burner tabs on throwaway sessions.
!

Honest limits. WARDEN is not a VPN and does not hide your IP; it does not defeat TLS or DNS fingerprinting. Storage APIs other than cookies (localStorage, IndexedDB, Cache) are memory-only per session but not individually blocked. When a site genuinely cannot work without cookies, the allowlist is the intended answer — not a global "accept all".

04

Compatibility mode, and where it stops

Challenge pages, bank portals and SSO will not load through a privacy stack. One click in the shield panel puts a host — and its subdomains — into compatibility mode: no filtering, headers sent exactly as the page built them, Set-Cookie untouched, and no injected shims. Its cookies are treated as policy-accepted, so a purge does not break it again. Toggling reloads every tab already on that host.

LayerDefaultCompatibility
Ad / tracker filteringonoff
Header rewritingonoff
Cookie stripping + store guardonoff
Fingerprint shims + cookie lockonoff
HTTPS-only upgradeonon
!

It removes WARDEN's obstacles, not Cloudflare's. A managed challenge that refuses Electron still refuses it with every layer disabled — verified against a real site that reaches "verification successful" and is then handed another 403 with no clearance cookie. The browser engine is the variable there, and saying so is more useful than a checkbox that implies otherwise.

05

Build it, run it, ship it

Node 20+ and a Windows host for packaging. The shell needs no caveats: node-pty ships prebuilds for win32-x64, with a pipe fallback everywhere else.

# from source
git clone https://github.com/innotelinc/warden
cd warden && npm install

npm run dev        # electron-vite, hot reload
npm run verify     # typecheck + unit tests + build + smoke

# shipping artifacts
npm run dist       → release/WARDEN-Setup-0.2.0.exe
                   → release/WARDEN-Portable-0.2.0.exe
npm run smoke:dist # drive the packaged binary, 32 checks
Installer
NSIS, per-user. Silent with /S; uninstall entry in HKCU with InstallLocation.
Portable
Single exe. Extracts to temp, keeps its own profile, leaves no installed state.
Android
Signed APK, installed straight from the browser. No Play account, no review, no fee — the link above is the same one after every tag, and the app updates over the build that is already installed. The download route is the release page: releases/latest/download/WARDEN-android.apk.
Profile
%APPDATA%\WARDEN — settings, history, bookmarks. No cookie jar, ever.
Signing
Built unsigned today. Signed free through SignPath Foundation's open-source programme once the project is approved; a self-signed path exists for fleets that deploy their own root.
Fleet tooling
PowerShell install/detect/uninstall script, an Intune win32LobApp definition, and a Graph app creator.
Tests
Unit coverage over the filter engine, cookie policy, clone writer, recon and popup policy; the smoke suite drives the real UI and the packaged binary.
QR code that opens the WARDEN Android APK download
Android · signed APK

Point the phone's camera at the code, or open releases/latest/download/WARDEN-android.apk. It installs straight from the browser — no Play account, no review, no fee — and the next release replaces it in place.

Latest build: on GitHub