A private, encrypted mesh between devices you already own. Pair them in person once. Reach them from anywhere. No accounts. No VPN provider. No exit nodes.
What makes it different QEV downloadsScan a QR code between two of your devices. Compare a 30-digit safety number out loud. You've just created a permanent trusted link.
WireGuard wire protocol (same Noise-family primitives QEV uses) carries packets between paired devices. Line-rate, auto-rekey, replay-protected.
LAN-direct on the same network; hole-punched UDP when not; the QEV relay as last-resort store-and-forward. Relay only ever sees ciphertext.
Your private key stays in the OS keystore (macOS Keychain, Android EncryptedSharedPreferences). Packet routing uses WinTun on Windows, utun on macOS, VpnService on Android.
Identical QR + safety-number process as QEV device pairing. If you already use QEV, you already know how to set up Qira Link.
When direct UDP fails, tunnel traffic routes through the QEV relay. It still sees only ciphertext — no plaintext, no metadata beyond pk-to-pk.
Every line auditable. No back door. No telemetry. Same license as QEV.
No subscription. No tiers. No locked features. The same promise as QEV because Qira Link is the same philosophy at a different layer.
Rust library implementing the WireGuard wire protocol wrapped with QEV pairing as the sole trust source. Target: 1.5 weeks.
macOS utun, Windows WinTun, Linux /dev/net/tun. Target: 2 weeks.
VpnService + JNI into the Rust core. Target: 1.5 weeks.
STUN + hole punching, QEV relay fallback. Target: 1 week.
Tauri app, tunnel toggle, peer list, connection status. Target: 1 week.
Signed DMG, MSI with WinTun, signed APK. Target: roughly 10 weeks from spec (2026-04-17).
Qira Link v0.1.0 will appear on the downloads page when it's ready. No mailing list, no tracking — same as everything else here.