Phone
Pixel running GrapheneOS. Verified boot, per-app network and sensor permissions.
Monero · EU · upstream open-source
De-Googled phones, sovereign-OS laptops, anti-tracking routers and privacy tools — assembled on top of published open-source projects (GrapheneOS, Qubes, Tails, OpenWRT, blue-merle) and documented without superlatives. Each page states what the device changes, and what it does not. Monero payment.
Three lines
Each line starts from a defined adversary. We assemble to order and document every choice.
Pixel running GrapheneOS. Verified boot, per-app network and sensor permissions.
ThinkPad with coreboot + Heads. Measured boot, attestation via a secret only you know. Qubes or Tails.
OpenWRT with WireGuard and a kill-switch. No traffic leaves if the tunnel drops.
Our approach
We do not invent cryptography. We reduce attack surface on top of auditable work — and we show the limits with the same weight as the features.
What we do
What this does not protect against
Threat models
A device is only useful against a defined adversary. Start from the profile closest to yours.
Transparency
The only payment method. No visitor IP logs, no analytics, no trackers.
Every build links to published open-source projects, with a last-verified date.
The site loads only from its own origin: no external fonts or CDNs, no third-party scripts.
The shipping address is encrypted and decrypted only to print a label; email is optional, then purged.
Start from your threat model, then compare what each line actually changes.