Should You Self-Host Your UniFi Controller or Use a Hosting Service?

Last reviewed September 2026.

Short answer: Self-host if you enjoy server administration and your time is free. A VPS costs $10 to 50 a month and the UniFi software itself is free. Use a hosting service if the controller supports a business, because the real cost of self-hosting is maintenance that never stops: OS patching, UniFi upgrades that sometimes break, database care, certificate renewals, backups, and being the person who fixes it at 11pm.

Which software this applies to

Ubiquiti ships two ways to run a controller on your own server:

UniFi OS Server is the current one. It runs the UniFi OS layer with the Network application inside it, the same arrangement as a Dream Machine. New subscriptions with us are set up on it, with the Network Application still available on request. See hosted UniFi OS Server for what changes.
The UniFi Network Application is the older standalone application on port 8443. It still works, a great many controllers still run it, and Ubiquiti still releases updates for it.

The self-hosting workload is much the same for both. Where a detail differs, this page says so.

What a controller needs to run reliably

The software is free to download, and that makes self-hosting look free. Running it reliably means owning all of this:

A server. A VPS ($10 to 50 a month depending on device count), a spare machine, or Ubiquiti hardware such as a Cloud Key.
Operating system maintenance. Security patches, kernel updates, reboots, disk space.
Software upgrades. New releases occasionally break device adoption, change database schemas, or drop support for older device firmware. On the Network Application you choose when to upgrade, so you are the QA team: test first and know how to roll back. UniFi OS Server manages its own updates, which removes both the choice and the testing window.
The database. UniFi keeps device and statistics history in a database that needs disk space management and, occasionally, repair. A corrupted database is the most common way self-hosters lose a controller.
Backups that restore. Automatic backups stored on the same server disappear with the server. Offsite copies are your job.
TLS certificates. Let's Encrypt renewals, or your devices and browsers complain.
Security. A controller exposed to the internet for remote adoption is a target. Firewalling, brute-force protection and keeping the inform port safe are on you.
Availability. When the controller is down you lose visibility, configuration changes, guest hotspot authorisation and statistics. Devices keep passing traffic, but you are flying blind.

None of these tasks is hard on its own. The cost is that they never stop.

When self-hosting is the right choice

Homelab or learning. Running your own controller is a good way to understand UniFi, and downtime only inconveniences you.
You already operate servers professionally and the controller is one more small workload in an existing, monitored, backed-up environment.
Fully offline sites. If the controller must live on a LAN with no internet access, hosting is not an option.

When hosting is the right choice

The network supports a business. If the WiFi going unmanaged for a weekend costs money or reputation, the controller should not depend on one person remembering to patch a VPS.
You manage more than one site. One hosted controller can manage unlimited sites, and devices at each site adopt to it over the internet. No server at each site and no VPN. This is the most common reason people move to a hosted controller.
You want upgrades tested by someone else. We test each Network Application release across our fleet for one to four weeks before rolling it out, and skip releases that do not meet our stability bar.
You value the hours more than the fee. At $50 an hour for your time, two hours a month of server care costs more than most hosting plans.

The middle ground: start self-hosted, move later

Many of our customers started on a self-hosted controller or a Cloud Key and moved when the maintenance stopped being fun. Migration is a well-worn path. UniFi's backup and restore and Site Export tools move your sites, devices and settings without re-adopting hardware:

Move a UniFi controller using Backup and Restorehelp.cloudunifi.com/unifi/move-using-backup-restore/ Migrating sites with Site Exporthelp.cloudunifi.com/unifi/migrating-sites-with-site-export-wizard/ If you are moving from the Network Application to UniFi OS Server at the same time, there is one extra step to plan for: getting your devices talking to the new address.

What Cloud UniFi handles for you

We host a private controller for each customer. Plans start at $15 a month for up to 100 devices, and we take on the whole list above: hardened OS, staged and tested upgrades, nightly encrypted backups to two offsite locations, TLS, firewalling and monitoring. Your controller runs on dedicated bare-metal servers that we operate ourselves, in OVHcloud data centres in Canada, the US, France, Germany, the UK and Australia, with other OVHcloud locations such as Singapore available on request. New controllers are placed in the region that matches your billing country. Unlimited sites on every plan. If you want a hand migrating, contact support or use the chat. Walking people through migrations is a large part of what we do.

How the costs compare, and how we stack up against other hosts:

How Much Does It Cost to Run a UniFi Controller?cloudunifi.com/guides/unifi-controller-hosting-cost/ UniFi Controller Hosting Compared: Cloud UniFi, HostiFi, UniHosted and Ubiquiti's Own Hostingcloudunifi.com/guides/unifi-hosting-comparison/

UniFi and UniFi OS are trademarks of Ubiquiti Inc. Cloud UniFi is an independent hosting provider and is not affiliated with, authorised by or endorsed by Ubiquiti Inc.