UniFi controller hosting: Cloud Key, self-hosted or hosted?
A Cloud Key suits one site, self-hosting suits people who enjoy running servers, and a hosted UniFi controller suits anyone managing several sites or clients who would rather not think about the controller at all.
The CloudWLC team at Optaro · · 6 min read
Every UniFi network needs the UniFi Network application running somewhere. Where you run it decides how much of your week goes on the controller rather than the network. There are three choices.
| Cloud Key or console | Self-hosted | Hosted controller | |
|---|---|---|---|
| Where it lives | A box on site | Your server or VM | The provider’s cloud |
| Several sites or clients | One box per location, or VPNs | Yes | Yes |
| Updates and backups | You | You | Done for you |
| If the hardware fails | Management is down until it is replaced | You rebuild it | Not your problem |
| Remote access | Through the vendor’s cloud login | You secure and expose it | Its own HTTPS address |
Cloud Key or console on site
Simple and tidy for a single location. The weakness is that it is a single box in a cupboard: if it fails, or the site loses power or connectivity, management goes with it. For an installer with thirty clients it also means thirty separate controllers to log in to.
Self-hosting the UniFi Network application
Running the application on your own Linux server or virtual machine gives you one controller for every site. It also gives you an operating system to patch, Java and a database to keep in step with each release, certificates to renew, backups to test and a public-facing service to secure. None of that is hard. All of it is time, and it tends to be needed at the least convenient moment.
A hosted UniFi controller
A hosted controller is the self-hosted model without the hosting. With UniFi controller hosting on CloudWLC you get a dedicated controller that is yours alone, at its own address with trusted HTTPS, backed up automatically, updated for you and monitored by network engineers. Your access points and switches stay exactly where they are; only the controller moves.
- For installers and MSPs: every client site in one controller, with as many sites as you need inside your device allowance.
- For multi-site businesses: no dependency on a box in any one branch.
- For hospitality: run by a team that has deployed more than 10,000 access points in hotels and venues.
Moving an existing controller
UniFi has dependable tools for this. Take a backup or a site export from your current controller, restore it into the hosted one, then use UniFi’s site migration to point each site’s devices at the new address. Move a site at a time and check devices have reconnected before moving the next. The CloudWLC portal walks you through each step.
What it costs
CloudWLC’s UniFi plans start at £25 a month for up to 25 devices, £45 for 100, £95 for 300 and £175 for 750, with two months free on annual billing. Larger estates use volume pricing, where the per-device rate falls as you grow. Compare that with the hours you spend on a self-hosted server in an ordinary month.
Quick answers
What is UniFi controller hosting?
A provider runs the UniFi Network application for you in the cloud, on a dedicated controller at its own secure address, and looks after updates, backups and monitoring. Your UniFi devices stay on site.
Is a hosted UniFi controller better than a Cloud Key?
For a single small site a Cloud Key is fine. For several sites or clients, a hosted controller gives you one place to manage everything and removes the on-site box as a point of failure.
How much does UniFi controller hosting cost?
On CloudWLC, from £25 a month for up to 25 devices, with larger plans and per-device volume pricing for bigger estates. Prices exclude VAT.
CloudWLC is an independent service from Optaro. It is not affiliated with, endorsed by or operated by Cambium Networks, HPE Aruba Networking, RUCKUS Networks, Ubiquiti or any other equipment vendor.