Where to host
the UniFi controller

Ubiquiti’s UniFi networks are everywhere: offices, professional firms, hospitality, manufacturing. And everywhere the same question keeps getting postponed: where should the controller run? On the CloudKey in the rack, on a virtual machine, on Ubiquiti’s official hosting or on a managed service? It is not a detail for tinkerers: the controller is the management plane of the entire network, and where it lives determines who updates it, who backs it up and where its data ends up. Let us look at the four options with honest pros and cons — and the criteria for choosing.

The controller is a critical asset, not an accessory

The UniFi controller holds the complete network configuration — SSIDs, VLANs, rules, users, captive portal — and governs provisioning and firmware updates for access points, switches and gateways. Whoever compromises it controls the network; whoever loses it without a backup rebuilds it by hand.

That this is no theoretical risk is confirmed by the May 2026 Operational Summary from CSIRT Italia, which reports five critical CVEs in UniFi OS — the platform behind UDM, UDM-Pro, UDM-SE, UDR, UNVR and Cloud Gateway. Like any management software, the controller needs disciplined patching: a controller installed once and forgotten in the rack is exactly the kind of legacy system attackers look for.

The four options compared

• 1On-site hardware (CloudKey or UniFi gateway) — simple, everything local, data in house. Cons: it is another device to power, update and back up; if it fails or gets encrypted by ransomware together with the rest of the network, the management plane goes with it. Suitable for small networks with someone who genuinely looks after it.
• 2Self-hosted on a VM or server — with UniFi OS Server (the new standard for self-hosting) the controller runs wherever you want: maximum flexibility, multi-site, full control over versions and data. Cons: you are the service provider — OS and controller patching, backups, monitoring, secure exposure. The right choice only if this responsibility has an explicit owner.
• 3Official UniFi Hosting (Ubiquiti) — the vendor’s option: no hardware, access from unifi.ui.com, management of up to 1,000 UniFi Network devices, monthly fee. It is a serious option and sufficient for many. Points to weigh: the documentation does not state where the data resides nor lets you choose the region — a concrete issue for those with GDPR or contractual data-residency constraints; control over update windows is limited; and it remains hosting — network management is not included.
• 4Managed hosting by an IT provider — the controller runs in the provider’s cloud, which takes on backups, updates, monitoring and secure access — and, in the full model, management of the network itself: configuration, segmentation, firmware, alerts. The criteria for evaluating a provider: where the data resides (European datacentres?), with what guarantees (verifiable security certifications), and what the contract actually covers — just the VM, or the network.

The criteria that really matter

Preferences aside, the choice comes down to four concrete questions. Who takes the backups — and where they end up: the controller backup is the most important asset of the network, and it must live outside the controller itself. Who applies the updates — May’s five CVEs do not patch themselves, and not at 2 a.m. when it suits you, unless someone schedules it. Where the data resides — the controller handles network data and, with captive portals and hotspots, personal data of users too: European residency is not a flag, it is a contractual and compliance simplification. Who manages the network — hosting solves where the software runs, not who answers when the warehouse Wi-Fi disappears.

Our model: the managed network, not just the controller

Our approach is the fourth option taken all the way: the controller runs in our European cloud, on infrastructure managed according to ISO/IEC 27001 — automatic backups, scheduled updates, monitoring, secure access, no CloudKey to maintain on site. And around the controller we manage the network: design, segmentation, device firmware, alerts. For clients with a management contract, controller hosting is included in the service — details on the managed hardware page. And the controller backup follows the same rules as any serious backup: verified and restorable.