How to actually get each service running on your own device. Point at the existing, mature ecosystem wherever one already exists (WHITEPAPER §5.1) — only the pieces unique to this project get their own tool.
📱 Official WireGuard app — Android, iOS, desktop
No custom app to install for the direct-VPN case at all. /connect hands you either a QR code (scan it straight into WireGuard's own "Add Tunnel → Scan from QR code") or a plain .conffile, generated fresh per device from the broker's live signed directory.
🐧 Native connect CLI — Linux
The one piece of custom client software this project actually ships (WHITEPAPER §5.1) — scoped to VPN connection management only, Mullvad-app-style: kill switch (blocks all non-tunnel traffic if the connection drops), auto-reconnect (detects a drop, re-fetches the directory if needed, reconnects on its own), split-tunneling, and DNS-leak protection — all on by default. Statically built, no install step, no dependencies to pull in beyond standard Linux tooling (wg-quick, nft, ip) it shells out to rather than reimplements.
/connecthands you a ready-to-run command per host — pick one and click "Connect via CLI" — or grab the binary directly:
curl -fsSL http://bitphase.tech/downloads/connect-linux-amd64 -o connect && chmod +x connect
Requires root (wg-quick/nft/ip all need it) — sudo ./connect -broker-url ... -broker-pubkey ... -vpn-connect <host> -up. Ctrl-C disconnects cleanly (tears down the kill switch and routes).
🧅 Anonymous onion-circuit mode — not yet available
The multi-hop circuit backend (streaming circuits, diversity/rotation) is built and tested against real interfaces. The client that would actually capture your device's traffic into it — a phone app using Android's VpnService + a tun2socks-style bridge into the circuit — isn't built yet. Stated plainly, not hidden: see /checklist's "Native client scope" section.
💬📁 Chat & File Share — web client, not hosted on this site yet
Both are vanilla JS/HTML — no framework, no build step, no app to install once it's wired up here. The server side (identity, encryption, transport) is built and tested; this website doesn't serve the client pages yet, which is why they're not linked as a "go do this now" button above. See /services for status.