LxBox Evolves from VPN Client to Comprehensive Network Traffic Management Ecosystem

LxBox has rapidly evolved from a simple Android VPN client into a complete ecosystem for managing network traffic across phones, desktops, and routers. The project now unifies VPN and proxy protocols under one routing engine, enabling users to handle corporate connections, personal proxies, and home networks through a single interface.

The developer began with a personal goal of creating a client for sing-box that met individual needs while demonstrating strong project management. Market feedback quickly expanded the scope: the core was forked to add AmneziaWG and XHTTP support, later extended to routers via OpenWrt, and then to desktop environments. Users demanded consistent experiences across devices, leading to the current multi-platform approach.

LxBox now supports numerous protocols in one routing table. VPN options include WireGuard, AmneziaWG, OpenVPN, SSL VPN via OpenConnect (covering Fortinet, Cisco, GlobalProtect, F5, and Pulse), and Tailscale. Proxy protocols cover VLESS, VMess, Trojan, Shadowsocks, Hysteria2, TUIC, AnyTLS, NaïveProxy, TrustTunnel, SSH, SOCKS, and HTTP. This integration allows rules such as routing work domains through corporate SSL VPN while sending other traffic via personal proxies.

The project operates along three main tracks: the sing-box-lx core with added features including MASQUE, post-quantum VLESS, and the lxd daemon for routers; the LxBox Android client available on Google Play, F-Droid, and GitHub; and the singbox-launcher desktop tool written in Go that also serves as a router interface.

Security receives particular attention. Default presets block incoming connections from VPN tunnels unless explicitly allowed, preventing unauthorized access from third-party servers or compromised peers. Additional rules catch traffic from excluded applications that might leak server addresses via direct binding to the tunnel interface. No telemetry or analytics SDKs are present in the APK, and subscription requests use only standard headers with optional random identifiers.

The interface follows a progressive disclosure model similar to progressive JPEG encoding. Users start with one-click Cloudflare WARP setup, advance to subscription-based routing with presets, and can reach deep customization through routing rules, per-app controls, diagnostics, subscription filters, and direct JSON editing. Documentation is structured in layers to support both human readers and AI agents.