infosave2007 /aivpn
AI-VPN that makes your traffic invisible to deep packet inspection
★ 906⑂ 77👁 18⑃ 28● 71▤ 18
+5
Daily
906
stars
77
forks
18
watchers
28
prs
71
issues
18
releases
README
Experimental Project. AIVPN is an engineering research project exploring network protocols and methods of protecting data in transit. It does not guarantee the ability to bypass network restrictions, anonymity, or protection against detection and blocking. The project has no political objectives. The project is not intended for unlawful use. Users must comply with the laws applicable where they are located and use the software at their own risk. The author does not endorse unlawful use of the project. Third-party claims about the project's guaranteed effectiveness or political purpose do not represent the author's position. 🌐 Русский | 中文 | 日本語 AIVPN !Rust !Platforms --- Overview AIVPN combines UDP tunnel encryption with traffic masking. Masks define the outer protocol, packet sizes and send intervals. Being recognized as STUN or QUIC does not by itself prove statistical indistinguishability from a specific application. Key technical properties: - InitialV2 and PFS - the initial exchange confirms a fresh server key; data and management commands travel only after PFS. Bound and privileged devices must also prove their persistent key and, when mTLS is required, present a valid certificate. - O(1) session lookup — no session ID is transmitted in the clear. Every packet carries an 8-byte resonance tag derived from a timestamp and a per-session secret. The server resolves the session in constant time via a DashMap. - Perfect Forward Secrecy — in-flight session key rotation via X25519 ratchet. Compromising the server key does not expose past traffic. - Neural Resonance module — per-mask micro-MLP (~66 KB) monitors live traffic statistics; high reconstruction error triggers automatic mask rotation without disconnecting clients. - Generative mask distributions - profiles support multimodal packet-size and inter-arrival models fitted from captured traffic with a BIC-selected Gaussian mixture. Clients sample the stored model; its presence does not establish similarity to a named application. - Written in Rust — memory-safe, no GC pauses. Client binary ≈ 2.5 MB. Runs on a $5 VPS. --- Architecture Workspace layout crates/aivpn-common/ — shared crypto, protocol, mask profiles (no I/O) crates/aivpn-server/ — Linux-only VPN gateway and management CLI crates/aivpn-client/ — cross-platform VPN client (Linux / macOS / Windows) crates/aivpn-android-core/ — JNI bridge for Android (Rust → Kotlin via C FFI) crates/aivpn-ios-core/ — iOS Rust staticlib (C FFI), linked by PacketTunnelProvider crates/aivpn-windows/ — Windows GUI (egui/eframe 0.31, manages aivpn-client.exe subprocess) crates/aivpn-linux/ - Linux GUI (Iced 0.14, wraps aivpn-client subprocess) platforms/android/ — Android Kotlin app (MVVM: MainViewModel + RecyclerView) platforms/ios/ — iOS SwiftUI app + NetworkExtension PacketTunnelProvider platforms/macos/ — macOS SwiftUI menu bar app + privileged helper daemon platforms/aivpn-web/ — Web
Top issues
#47Если отвпливается, не проходит подключение2 comments · 2026-05-10#66Одновременная работа 2х и более клиентов1 comments · 2026-06-23#45Сборка клиента под macOS "Big Sur"1 comments · 2026-05-04#99Docker стартует и тут же падает0 comments · 2026-11-03#97Вопрос по добавлению клиента (Windows, Android)0 comments · 2026-11-03#96Connection falls down at the start on win client app0 comments · 2026-11-02#95AIVPN вызывает зависание сервера0 comments · 2026-11-01#94Не работает установка в режиме systemd по SSH через windows клиент0 comments · 2026-10-31
Latest release
AIVPN 1.2.0 v1.2.0 2026-10-27Dual-stack networking, signed distribution and application hardening. 1.2.0 extends IPv6 across the tunnel, adds large management messages and new bootstrap and mask distribution channels, and fixes session, storage and platform security issues. Inter-server connections now use masked handshake sessions throughout. [!IMPORTANT] Breaking release. The initial exchange moves to InitialV2 and is incompatible with 1.1.0 and earlier 1.2.0 development builds. There is no automatic fallback. Update servers, pool/site/chain nodes and every client, including embedded mobile cores, together. Highlig