Self-hosting vs managed UniFi controller hosting
Running your own UniFi controller gives you control over its server and maintenance. Managed hosting transfers agreed server responsibilities to a provider. The choice depends on who will handle updates, backups and recovery when something goes wrong.
This comparison covers your own hardware, a self-managed cloud VM and managed hosting.
Watch the comparison
Running the controller on your own hardware
You provide the server and maintain the controller software. This can suit a home lab or an IT team with the time and skills to operate it.
What you control
- The hardware and software configuration.
- Update timing and maintenance windows.
- Backup storage and recovery procedures.
- How you allocate resources as the deployment grows.
What you take responsibility for
You handle operating-system updates, controller updates, access security, monitoring and recovery. Existing hardware may reduce the initial cost, but electricity, replacement equipment and staff time still count.
A single server without a tested recovery arrangement can leave management unavailable when it fails. Self-hosting can scale, but someone must plan and maintain that capacity.
Our installation guides cover self-hosting on Debian, installing the controller on Windows and installing it on a Mac.
Running the controller on a cloud VM
A cloud VM lets you rent server resources instead of buying local hardware. You still operate the controller and its operating system unless you purchase a separate management service.
What changes
- The infrastructure provider operates the physical server.
- You choose a VM size and pay the provider’s charges.
- Resource upgrades depend on the provider, VM type and available capacity.
- You still configure access, updates, monitoring and backups.
Include storage, backup and transfer charges in the comparison. Plan resource changes and recovery before you need them. Renting a VM does not establish an automatic backup policy or remove the possibility of outages.
Using managed hosting
A managed provider takes responsibility for the services included in your plan. Compare the actual scope: update handling, backups, monitoring, migration assistance and support.
What to check
- Which server maintenance tasks the provider handles.
- What is backed up and how restoration works.
- How updates are selected and rolled out.
- What support your plan includes.
- How capacity upgrades and contract terms work.
Your team still manages the client’s network configuration and physical equipment. A managed service can reduce server work, but it should not be described as immune to hardware failures or attacks.
Responsibilities compared
| Approach | Server maintenance | Backup responsibility | Capacity planning |
|---|---|---|---|
| Your own hardware | Your team | Your team | Size and expand your equipment |
| Self-managed cloud VM | Your team manages the OS and controller | Configure and test it yourself | Check the provider’s upgrade options |
| Managed hosting | Provider, within the agreed service scope | Check the plan and recovery process | Agree on the upgrade process with the provider |
Compare the work and costs against your team’s capacity. For provider prices, see our comparison of UniFi hosting costs. Broad labels such as “high risk” or “low risk” do not tell you whether a specific deployment has working backups or a tested recovery process.
When UniHosted fits
Self-hosting can work well for a personal network or a team that wants to operate its own servers. For MSPs looking to hand over controller maintenance, UniHosted’s paid plans include dedicated controller hosting, updates, backups and migration assistance.
Core includes email and chat support. Scale includes founder-led support. Enterprise SLA terms depend on the contract. The Free plan uses a shared controller for up to five devices on one site and does not include support or backups.
Book a demo to discuss your setup. Paid plans include a 30-day money-back guarantee.