For years, managing a business network meant having a physical server in a cupboard somewhere, plugged in, with the configuration stored locally — and a quiet dependency on nobody needing remote access in a hurry. Cloud computing has changed a lot of things, but in network controllers, that transition is still happening more slowly than it should.

What exactly is a cloud network controller

A network controller — the software that centralises the configuration, monitoring and management of all access points, switches and routers on a site — can run in three ways: on a local machine, on an internally managed server, or on a cloud-hosted server run by an external provider. That third option is what's called cloud network management.

In the case of TP-Link's Omada SDN and Ubiquiti's UniFi OS — the two most common platforms in Portugal for business and hospitality use — the controller can be self-hosted or delegated to an external service. The physical network doesn't change. The access points and switches stay in the building. What changes is where the brain that manages them lives.

What changes in practice

The most immediate difference is remote access. With a local controller, accessing the management console from outside the building usually requires a VPN, open firewall ports, or both. With a cloud controller, you access it from anywhere with a simple web connection — no special network configuration. For small teams that need to respond to problems out of hours, or IT managers handling multiple sites, this fundamentally changes response time.

The second difference is availability. A local controller that fails — drive, OS, power cut without a UPS — takes the ability to manage the network with it, even if the network itself keeps running. Any configuration change, any diagnostic, any controlled reboot is blocked until you fix the physical problem. With a cloud controller, that management layer is separated from the physical infrastructure and maintained externally.

When moving to the cloud makes sense

Not always. A restaurant with ten access points and a reliable local technician can perfectly well run a controller on a headless mini PC and never miss a thing. Cloud starts to make clearly more sense when:

  • The IT team needs frequent remote access — multiple sites, out-of-hours support, hybrid working.
  • There is no technical staff on site to deal with controller hardware problems.
  • The site has high dependency on WiFi for critical operations — hospitality, healthcare, logistics.
  • The business model requires scaling quickly to new sites: each new unit is visible in the same console within minutes, without additional infrastructure.

What to check before migrating

Moving the controller to the cloud is not high-risk surgery, but there are things to verify. The existing configuration is exportable and importable — both Omada and UniFi have tools for this — but it is worth testing on a low-traffic environment before the full migration. The physical network has no downtime during the controller migration, but access to the management console is unavailable during the transition window.

For normal configuration operations, the latency difference between a local and a cloud controller is imperceptible. For very specific cases in industrial or security networks with strict low-latency requirements, evaluate case by case.

The Omifi model: hosted controller, your network

Omifi is Flexispectrum's service for hosting network controllers in the cloud — Omada SDN, UniFi OS and UISP — on dedicated servers across 33 global locations. The model is simple: Flexispectrum handles the server, updates, availability and secure access; the physical network and equipment stay yours. No need to buy your own cloud capacity, configure VMs or manage operating systems. The controller is running, accessible, and someone is responsible for keeping it that way.