1. Architectural Divide: Subscription Panels vs Gateway OS
Nine out of ten platforms in this review—3X-UI, X-UI, Hiddify Manager, Marzban, PasarGuard, Remnawave, S-UI, H-UI, and Marzneshin—belong to the class of proxy subscription panels. They wrap Xray-core or sing-box with a web UI, user quota counters, and subscription URL generators. Whenever you need OS-level firewalling, per-user kernel bandwidth shaping, native Windows VPN, or site-to-site router tunnels, the administrator must configure Linux manually.
Apium Cloud OS is engineered as a complete gateway operating layer: a low-footprint Rust daemon directly orchestrating four protocol engines (Xray VLESS Reality, Hysteria 2, accel-ppp SSTP, strongSwan L2TP/IPsec) alongside Linux nftables, tc, Upstream Relay cascading, and real-time metadata DPI inspection.
2. Visual Architecture & Capability Index
3. Structured Comparison by Engineering Domain
Control Plane, Footprint & Failure Domains
Block A • Runtime & StateHow the control plane executes, what dependencies it pulls onto the host, and what happens if a central database or master panel becomes unreachable.
| Platform | Control Stack | Idle RAM Profile | State & Failure Mode |
|---|---|---|---|
| Apium Cloud OS | Rust binary + systemd | ~25–45 MB | Autonomous local node; zero central DB dependency |
| 3X-UI / X-UI | Go binary + SQLite | ~45–80 MB | Single-node SQLite; multi-node via panel API |
| Hiddify Manager | Python + HAProxy + 2 cores | ~280–450 MB | Heavy multi-service stack on single host |
| Marzban / Marzneshin | Python (FastAPI) + SQL/Marznode | ~150–350 MB | Master panel / DB failure blocks provisioning |
| PasarGuard / Remnawave | Python or NestJS + Docker + DB | ~350–700+ MB | Docker orchestration + central DB required |
| S-UI / H-UI | Go binary + SQLite | ~35–65 MB | Autonomous single node; limited enterprise tooling |
Transport Coverage & Clientless Access
Block B • Protocol MatrixComparing modern obfuscated transports (for mobile/desktop apps) against native OS tunnels (for locked-down Windows laptops and hardware routers).
| Platform | VLESS Reality | Hysteria 2 (QUIC) | Windows SSTP | L2TP/IPsec (Routers) |
|---|---|---|---|---|
| Apium Cloud OS | ✓ Native | ✓ Native | ✓ Built-in | ✓ Static IP / Subnet |
| 3X-UI | ✓ Native | ◐ Inbound layer | ✕ No | ✕ No |
| Hiddify Manager | ✓ Native | ✓ Native | ✕ No | ✕ No |
| Marzban / Remnawave | ✓ Native | ✕ / External | ✕ No | ✕ No |
| PasarGuard / Marzneshin | ✓ Native | ✓ Native | ✕ No | ✕ No |
| S-UI | ✓ Native | ✓ Native | ✕ No | ✕ No |
| H-UI | ✕ No | ✓ Only protocol | ✕ No | ✕ No |
Security, Traffic Shaping & Cascade Failover
Block C • Network EngineeringProduction gateways require kernel-level isolation, fair bandwidth allocation, and automatic multi-hop recovery when an upstream ISP degrades.
| Platform | Cascade + Auto Failover | OS Firewall & tc Shaper | DPI Metadata Inspector | Zero-Disk SSH Deploy |
|---|---|---|---|---|
| Apium Cloud OS | ✓ Built-in L3/Relay | ✓ 3-tier nftables + tc | ✓ Real-time | ✓ No secrets on disk |
| All 9 Proxy Panels | ◐ Manual outbounds only | ✕ Manual Linux admin | ✕ No | ✕ Local .env / DB / Docker |
4. Full 10-Platform Matrix
5. Decision Matrix: Which Platform Fits Your Workload?
When Open-Source Proxy Panels Fit Better
- You run a consumer subscription service relying heavily on Telegram billing bots and HWID limits (Remnawave, Marzban, PasarGuard, 3X-UI).
- All end-users install third-party client apps (v2rayN, Hiddify, Nekobox, sing-box) and never use hardware routers or native Windows VPN.
- You specifically need experimental Xray/sing-box transports such as DNS tunneling or custom XHTTP chains.
When Apium Cloud OS Is the Stronger Choice
- You need both modern obfuscated protocols (VLESS Reality, Hysteria 2) AND clientless Windows SSTP / router L2TP/IPsec in one unified gateway.
- Every node must remain 100% autonomous without a central database single point of failure, while supporting Upstream Relay cascade failover.
- You require real-time metadata DPI inspection, 3-tier nftables isolation, per-user tc shaping, and Zero-Disk SSH deployment.