1. Hiddify Manager: Maximum Transports at Higher Complexity
Hiddify Manager runs both Xray-core and sing-box behind HAProxy, automated by Python services. This delivers impressive transport breadth—CDN profiles, DNS tunnels, XHTTP, Hysteria 2, TUIC, and WireGuard—plus automated Telegram backups. The trade-off is a dense multi-process stack that consumes significant RAM, complicates manual troubleshooting, and lacks native SSTP/L2TP/IPsec.
2. Remnawave: Polished TypeScript Provider Platform
Remnawave stands out with a modern React UI, NestJS backend, libXray config validation, HWID limits, visual routing, and official migration scripts from Marzban and 3X-UI. However, it requires a full Docker Master-Node infrastructure (NestJS, database, node agents) and targets Xray client apps exclusively.
Hiddify Manager & Remnawave vs Apium Cloud OS
Engineering ComparisonEvaluating runtime footprint, auditability, protocol strategy, and corporate gateway readiness.
| Dimension | Hiddify Manager | Remnawave | Apium Cloud OS |
|---|---|---|---|
| Runtime Stack | Python + HAProxy + Xray + sing-box | Docker: NestJS + React + DB + libXray | Single Rust control binary + 4 native cores |
| Resource Footprint | High (~300–450 MB idle) | High (~400–700+ MB stack) | Ultra-low (~25–45 MB idle) |
| Experimental Transports | ✓ Widest (DNS, CDN, XHTTP) | ◐ Xray transports via libXray | ◐ 4 battle-tested production cores |
| Clientless Windows / Routers | ✕ No | ✕ No | ✓ Windows SSTP + L2TP/IPsec |
| OS Hardening & DPI Inspector | ✕ No | ✕ No | ✓ 3-tier nftables + tc + DPI Inspector |
Choose Hiddify or Remnawave when:
- You need automated CDN/DNS-tunnel fallback profiles (Hiddify) or a polished multi-node Xray provider UI with migration from Marzban (Remnawave).
Choose Apium Cloud OS when:
- You want minimal Rust RAM/CPU overhead, zero Docker/Python bloat, native Windows & router support, and full OS-level firewall/tc/DPI visibility.