Legacy Baseline
X-UI (Stagnated)
Active Fork
3X-UI (Go + Xray)
State Storage
SQLite vs Rust Engine
Router Support
Apium Only (L2TP/IPsec)

1. Why Original X-UI Stagnated & How 3X-UI Took Over

The original X-UI was a compact Go web interface writing JSON configs for Xray-core. As anti-censorship protocols evolved rapidly toward VLESS-Reality, XTLS-Vision, and XHTTP, the upstream repository slowed down. 3X-UI filled that gap with active maintenance, multi-node management, HWID device limits, automatic Let's Encrypt issuance, and a built-in Telegram bot.

2. Architectural Limits of Pure Xray Wrappers

Even at its best, 3X-UI remains scoped to what Xray-core can do in userspace:

  • No clientless corporate access: Windows laptops under restricted IT policies and hardware routers (MikroTik, Keenetic) cannot run VLESS Reality natively without client software or custom firmware.
  • No kernel bandwidth shaping: Xray handles traffic quotas (bytes transferred), not fair per-user Mbps shaping via Linux tc HTB/FQ_CODEL queues.
  • No OS-level metadata inspection: Administrators cannot inspect live SNI/port/protocol metadata across all gateway interfaces from a single panel.

3X-UI / X-UI vs Apium Cloud OS

Structured Comparison

Direct engineering comparison across transport layers, OS integration, and operational security.

DimensionX-UI (Original)3X-UI (MHSanaei)Apium Cloud OS
Core ArchitectureGo + legacy Xray-coreGo + modern Xray-coreRust + Xray + Hysteria2 + accel-ppp + strongSwan
ProtocolsBasic VLESS/VMess/Trojan/SSFull Xray matrix + WG + Hysteria2 layerVLESS Reality, Hysteria 2, Windows SSTP, L2TP/IPsec
Hardware Routers✕ Not supported✕ Not supported✓ L2TP/IPsec + Static IP
Cascade & Failover✕ None◐ Manual Xray routing✓ Upstream Relay + Auto Failover
Host Hardening✕ Manual◐ Basic fail2ban/UFW✓ 3-tier nftables + tc + DPI Inspector

Stick with 3X-UI when:

  • You manage personal or small-scale Xray nodes with Telegram bot quotas.
  • All users connect via mobile/desktop proxy apps.

Upgrade to Apium Cloud OS when:

  • You need Windows SSTP or MikroTik/Keenetic L2TP/IPsec alongside VLESS Reality & Hysteria 2.
  • You want automated cascade failover, per-user Mbps shaping, and Zero-Disk SSH deployment.