Ubiquiti launches UniFi OS Server for self-hosting

Original Article ↗ Hacker News Discussion ↗

Scope of UniFi OS Server / What’s New

  • Clarified as the self-hosted version of the “UniFi OS” layer that runs on Dream Machines / Cloud Keys, not just the old UniFi Network controller.
  • Hosts multiple “apps” (Network, Identity, InnerSpace now; SD‑WAN / Teleport support) and is expected to enable more apps (e.g. Protect, Talk, Access) later.
  • Distributed as a single Linux executable that sets up podman containers; some find this odd and would prefer a VM image or published OCI/Docker images.
  • Several commenters were initially confused, thinking this was just a rename of the existing self‑hosted Network controller.

Privacy, Cloud Dependence, and Accounts

  • Many welcome self‑hosting plus the ability to run with a purely local account (no persistent cloud login, possible to operate air‑gapped).
  • Others are uneasy that some features (e.g., Protect “AI” smart detections) still require enabling cloud connectivity or extra hardware (AI Key).
  • Past issues (forced activation, devices needing internet/phone app to initialize, security incidents, cross‑tenant data exposure) make some users unwilling to “temporarily” enable cloud access.

Cameras, Lock‑In, and Pricing

  • Strong demand for fully self‑hostable UniFi Protect on generic hardware; older UniFi Video could do this.
  • Current state: Protect can ingest third‑party ONVIF cameras, but UniFi’s own cameras don’t expose ONVIF and advanced detections are tied to proprietary AI/cloud.
  • Mixed views on value: some think camera prices are far too high and report premature failures; others cite years‑long uptime and superior NVR software as justifying the premium.

Software Quality, Reliability, and UX

  • Enthusiasts praise the “Apple‑like” integrated experience, central management, and ease of VLAN/SSIDs/VPN/Site‑to‑Site setup; many report multi‑year uptime.
  • Critics describe:
    • Buggy or incomplete features (VLANs, firewall, IPv6, mdns, trunking on some APs).
    • Networks dropping for minutes when changing Wi‑Fi settings, or after power events; some resort to UPSes just to avoid recovery bugs.
    • Flaky updates and “production” releases that feel like betas; workarounds include disabling auto‑update and lagging behind on firmware.
  • UI is seen as clean but constantly changing; settings move around, docs lag, and advanced workflows (e.g., NAT, DNS, multi‑WAN IPv6) still feel hacky compared with OPNsense/Mikrotik/OpenBSD.

Positioning vs Alternatives / Use Cases for OS Server

  • UniFi is widely viewed as prosumer/SMB gear: far nicer than typical consumer routers, much cheaper and simpler than Cisco/Aruba/Ruckus, but not true enterprise‑grade.
  • Some use hybrid setups: UniFi APs/switches with other routers (OPNsense, pfSense/Netgate, Firewalla, Mikrotik, OpenWRT) or have moved entirely to TP‑Link Omada, Ruckus, etc.
  • UniFi OS Server mainly appeals to:
    • Users with only UniFi APs/switches (no UniFi gateway).
    • Those needing multi‑site management without UniFi’s cloud.
    • Homelab/SMB admins who already have always‑on servers and want central control without buying another appliance.