crystalmasta/unbihex
DevOps & Self-hostingA VPN client and Xray-compatible server for subscription-based proxy networks, with its own Rust core.
Unbihex is a proxy/VPN client for subscription-based servers, built on a self-written Rust networking core and compatible with Xray servers. It targets people who already have VLESS or Shadowsocks subscriptions and want a client that also offers a server binary to replace the Xray core under existing panels.
What it does
On the client side, Unbihex manages subscriptions and servers and offers a system proxy, TUN mode, Android VpnService and an iOS Packet Tunnel. It speaks VLESS (TLS, REALITY, XTLS Vision, XHTTP), Shadowsocks and SOCKS5, so it can point at servers you already run or subscribe to. On the server side, unbihex-server is described as a drop-in replacement for the Xray core under control panels; it implements VLESS/Vision/REALITY, UDP/XUDP and a gRPC API compatible with Xray (Russian README).
The distinguishing mechanism is that the client, engine and server share one Rust core: the server pulls its protocols from the engine via a server feature (README, engine spec). That matters practically because protocol fixes land in one place rather than in separate client and server codebases.
Available builds and requirements
Prebuilt artifacts are published per release (latest release):
- Windows 10/11 x64: installer or portable zip.
- Android 7+ arm64: APK.
- Linux: a static x86_64 or aarch64 CLI tarball.
- Linux server: x86_64 or aarch64 tarball, positioned as an Xray-core replacement under panels.
macOS and iOS are named as client targets, but the README's download table lists no macOS or iOS build, so users on those platforms should check the releases before relying on it. The Windows installer is unsigned enough that SmartScreen may warn about an unknown publisher; checksums are published alongside. Building from source is not a single root command: client and server reference the engine through the relative path ../unbihex-engine, so the directories must sit side by side, and build/test instructions live in the client README (client build docs).
Scope and caveats
This is a young project: the repository was created in October 2026 and the supplied material is essentially the README plus repository metadata. No independent evaluation, benchmark or protocol interoperability testing is provided, so Xray compatibility and the server's behavior under real panels are author claims rather than verified results. The server replacement path is the higher-risk use: swapping an existing core under a panel affects running connections, and the README documents no rollback or upgrade procedure—keep the original core available. The project is under MPL 2.0, and the README links license files in both subprojects (README).
The supplied HotRepo signal is only a single NEW-REPOSITORY board observation on 2026-10-29 (112 total stars, #21, Rust), not a daily growth measurement, and there is not enough history to draw trend conclusions.
Written by AI from the project's README, updated October 29, 2026. The project's own docs are the source of truth.