Skip to contentLaunching on Friday 25 SeptemberOur own controller for Cambium access points launches on Friday 25 September. Add new devices, with no licence server in the way.Learn more
CLOUDWLC

MSPs & installers

Your clients' wireless estates, organised.

One CloudWLC account, as many controllers as your business needs. Deploy a controller in a few clicks, migrate a client with a guided workflow, and stop rebuilding servers for a living.

Where you are today

  • Every self-hosted controller is another VM to build, patch, certificate and back up
  • Client migrations are manual: exports, spreadsheets and re-keying configuration
  • Controllers and credentials are scattered across clients and engineers

With CloudWLC

  • Controllers deployed on demand, each with its own address and trusted HTTPS
  • A guided migration you can run for client after client
  • One dashboard showing every controller, its status and its subscription

What you get

Specific benefits, not a feature list.

01

One account owns every controller

Your CloudWLC account is the top of the tree. Each controller underneath it has its own name, address, status and subscription.

02

Separate clients properly

Keep client estates apart within one controller — as sites on UniFi, or with Managed Accounts on cnMaestro — or give a client a controller of their own.

03

Deployment without the build sheet

Name the controller, pick a plan, and CloudWLC provisions the server, configures the controller, issues HTTPS and checks readiness.

04

Migration as a routine

Pair the extension, collect, review, switch. The same steps and the same clear summary for every client estate.

05

Show the client what will move

A readable scope — groups, WLANs, devices and items needing attention — that you can walk a client through before the change window.

06

Dedicated to you

Your controllers are yours. Unrelated CloudWLC customers never share a controller with you or your clients.

Account → controllers → sites

One account. Several controllers. Client estates inside each.

Start with a single controller, UniFi Network or cnMaestro, and keep each client separate inside it. Add controllers when a client, a region or a maintenance schedule deserves its own.

Client separation
On UniFi, each client is its own site with its own administrators. On cnMaestro, Managed Accounts keep each client's devices, configuration and users apart; availability depends on your cnMaestro software entitlement.
More controllers
Useful for geographic separation, scale, different maintenance schedules, or when a client contract calls for stronger isolation.
Your account
Owns all of it: every controller, hostname, status and subscription on one dashboard, with one place to add the next.

Getting started

A workflow you can repeat for every client

Cambium and UniFi estates are self-service from sign-up to switch. Running Aruba or Ruckus? Tell us what you run.

  1. 01

    Create

    Deploy a controller for the client, or choose an existing one and add the client to it.

  2. 02

    Connect

    Link the client's existing estate: you sign in to their current platform in your own browser.

  3. 03

    Import

    CloudWLC prepares the destination and gives you a scope you can share with the client.

  4. 04

    Switch

    Run the switch in the agreed window and watch devices check in.

Get early accessSee the full walkthrough

Questions

Asked by MSPs.

Read the full FAQ
Do all my clients share one controller?

Only if you want them to. You can keep several clients separate inside one controller — as sites on UniFi, or with Managed Accounts on cnMaestro, subject to the applicable cnMaestro software entitlement. You can also give any client a dedicated controller under your account. Either way, your controllers are dedicated to you and never shared with unrelated CloudWLC customers.

How many controllers can one account have?

As many as your business needs. Each is deployed from the dashboard, has its own address and subscription, and appears alongside the others.

Do I need the client's controller password?

You need access to the client's existing controller in your own browser, in the same way you manage it today. CloudWLC itself never asks for that password; the extension works through the session you have signed in to.

We manage some very large estates. Where do we start?

Talk to us. We'll look at device counts, regions and how you want clients separated, and suggest how to lay out controllers before you begin.

From the network assurance specialists

Run by the people who build hospitality networks.

CloudWLC is built and operated by Optaro. We have deployed more than 10,000 access points for major hospitality venues around the world, and we build the platforms that monitor and assure those networks every day. Hosting your controller is the same discipline, applied to the part of the network you would rather not run yourself.

Network assurance

Optaro Assure

Monitoring across Wi-Fi, switches, endpoints and security. A clearer cause when service degrades, a targeted response, and a way to check recovery.

Explore Assure

Optaro Assure

Wireless RF Audit

Radio, client, access point and service-path evidence for your wireless network. A useful baseline before you move a controller, and proof afterwards.

About RF audits

Hotel Wi-Fi

Optaro Connect

Cloud-managed HA gateways, branded guest portals and a private network per room. The guest's side of a hospitality network.

Explore Connect

Put your client estates on CloudWLC.

The portal opens soon. Reserve your place now and your first hosted controller is a few clicks away on launch day. Your access points stay exactly where they are.

Get early accessPrice your estate

30-day money-back guarantee · No server to install