QuicFuscate is an MIT-licensed open-source VPN transport written in Rust.

It uses QUIC/HTTP/3 as the base transport and targets high-loss/high-jitter links and DPI-heavy/restrictive networks.

What's different:

  - Adaptive FEC: hybrid RLNC + streaming (Tetrys-like), with loss-driven mode switching (incl. Fountain/LT mode).

  - Coherent stealth presets: deterministic browser/OS TLS ClientHello profiles + HTTP/3 masquerading + QPACK shaping + DNS-over-HTTPS.

  - Optional cover paths: MASQUE (HTTP/3 CONNECT-UDP) and domain fronting (provider/CDN-policy dependent).

  - Traffic obfuscation: configurable traffic padding + timing jitter (presets for Stealth / Anti-DPI modes).

  - Active-probe mitigation: probe-signal detection with escalation + "reality fallback" proxying.

  - Performance: SIMD-optimized hot paths, zero-copy buffer pools, and UDP fast paths (batching / GSO-GRO / io_uring where available).

Included apps (beta):

  - Desktop client: apps/desktop (Tauri + React) for tunnel management, settings, logs, hardware detection.

  - Web admin UI: apps/web-admin-ui for QKey (server-issued access key / auth token) provisioning and policy management.

How to try:

  - Clone the repo and `cargo build --release` (CLI is usable without the apps).

  - See the docs for minimal server/client commands and tuning options.

Repo: https://github.com/Christopher-Schulze/QuicFuscate

Docs: https://github.com/Christopher-Schulze/QuicFuscate/blob/main...

Looking for feedback on:

  1. threat model / detection surface

  2. sane defaults (stealth + FEC) and config ergonomics

  3. test reports from restrictive networks or lossy mobile networks

Motivation: open access to information.

Recent large-scale shutdowns (e.g., Iran’s January 2026 blackout) are exactly the kind of scenario this is built for.

Please use responsibly and within your local laws.