Hydrat Project Builds Automated WireGuard Gateway for Resilient VLESS and Tor Routing

A developer has released Hydrat, a self-hosted gateway that connects devices via WireGuard while automatically managing VLESS and Tor backends to survive server blocks and quality degradation. The system maintains a pool of tested proxies, performs continuous health checks, and switches routes without requiring client-side profile changes. Two Go processes handle control logic and network enforcement separately, using SQLite for state and nftables plus Xray for traffic routing. TCP and UDP can be assigned independent exits, with geoip.dat support and custom rules to keep marketplace apps functional. The project emphasizes stability over direct connections and is designed for deployment on servers in Russian jurisdiction.

HabrTranslated from Russian

Read at source

A developer has introduced Hydrat, an automated WireGuard gateway designed to maintain connectivity when VLESS servers become blocked or degraded. The project allows users to keep a single WireGuard profile on phones, laptops, and routers while the server handles proxy selection and failover.

The gateway accepts VLESS links, subscription feeds, and Tor bridges through an admin panel. Candidates undergo preliminary and full testing that checks access to Cloudflare, YouTube, ChatGPT, OpenAI API, and Telegram services, including UDP performance. Up to 10,000 candidates can be stored, with a working pool limited to 200 high-quality routes.

Active monitoring detects outages through fast HTTP and DNS probes, while a separate QoE loop measures time-to-first-byte and throughput against historical baselines. Routes enter degradation status after three poor results out of five and recover only after four good measurements. Two confirmed failures within a 20-measurement window also trigger alerts.

Client assignment uses weighted rendezvous hashing for initial selection. Planned route changes require a sustained 30 percent advantage, at least 30 minutes on the current path, and confirmation across three checks. Failover prefers pre-assigned backups before scanning the pool, and transport-level blocking occurs only when no viable alternative remains.

Network changes are applied sequentially: a new Xray outbound is created first, nftables rules are updated next, and old exits are removed last to avoid transient client disconnection. Separate counters ensure that only newer test results update route state.

The service runs in Docker, supports obfs4 and webtunnel Tor bridges, and preserves the last applied routing plan across restarts. The author notes that the server must remain reachable via WireGuard and therefore recommends placement within Russian jurisdiction.

Meridian digestThe week's most consequential security stories, distilled into one briefing.See the digest

More in Privacy & Surveillance

Maximizing iPhone Privacy: Essential Settings to Enable, Disable, and Verify Immediately
Top 10 Secure DNS Servers for Privacy, Threat Blocking and Ad Filtering in 2026
WebRTC IP Leaks Explained: Why Disabling the Protocol Harms Anonymity in Anti-Detect Browsers