Guest WiFi hardware that works with VoqadoWiFi

TP-Link Omada

VoqadoWiFi connects through the Omada controller's external portal feature. Self-hosted software controllers, hardware controllers, and Omada Cloud are all handled by the same integration, and self-signed certificates on a local controller are tolerated.

Ubiquiti UniFi

VoqadoWiFi supports both UniFi generations: UniFi OS consoles such as the Dream Machine and UDM Pro, and the legacy self-hosted UniFi Network Server on port 8443. Which one you have is detected automatically, including installs behind a reverse proxy or Cloudflare Tunnel.

The controller authenticates. It does not build you a list.

Both Omada and UniFi ship perfectly good built-in guest portals. What neither does is keep a durable, exportable customer record, deduplicate returning visitors, or send anything afterwards. That gap is the entire reason an external portal exists.

No hardware replacement, no RADIUS server

The external portal model uses features already present in your controller. You are not buying new access points, running FreeRADIUS, or putting a gateway appliance in front of your traffic.

Self-signed certificates are tolerated

Controllers installed on a local server or a VPS almost always present a self-signed certificate. VoqadoWiFi does not require you to obtain a public certificate for your controller before the integration will work.

A Test Connection button before you go live

When you enter your controller URL, site, and credentials in the VoqadoWiFi dashboard, Test Connection probes the controller and reports what it found. On UniFi it lists the sites the account can see so you can click to fill the site id rather than guessing at an auto-generated string.

Restaurants

Capture the diner at the table, then ask for the review after they leave.

Hotels

Turn the room WiFi login into a direct-booking relationship instead of an OTA one.

Pricing

Starter is free forever with one location. Growth is 49 dollars a month.

Two vendors: TP-Link Omada and Ubiquiti UniFi. Those are the integrations that exist in the product, and a location in VoqadoWiFi is configured as one or the other. We would rather tell you that plainly than publish a compatibility table full of vendors we have not built against.

An external captive portal is a login page hosted outside the controller. The controller redirects the guest to it, the page collects whatever you ask for, and then it calls back to the controller to authorise the device. The built-in portals from both vendors authenticate the guest and stop there. An external portal is what lets the login become a customer record you own, can export, and can market to later.

No. If your existing Omada or UniFi deployment already runs a guest network, it already has the portal feature VoqadoWiFi uses. The change is a redirect URL in your controller plus controller credentials in your VoqadoWiFi dashboard.

Self-signed certificates are tolerated, so you do not need a public certificate on the controller before connecting. What VoqadoWiFi does need is the ability to reach the controller over the network to send the authorisation call. If the controller is only reachable from inside the venue, expose it through a reverse proxy or a tunnel first.

Contact sales and tell us what you run and how many sites are on it. Vendor support is something we expand based on real demand rather than a published roadmap, so we will not promise you a date. What we will do is tell you honestly whether your hardware is something we are working toward or something we are not, so you can plan around a real answer.

Yes. The vendor is set per location, not per account, so a group with Omada in some venues and UniFi in others runs both under one dashboard with one guest database.

Nothing on top of your plan. The Starter plan is free forever and includes one location and 25 logins per month, which is enough to connect a controller and watch a real guest go through the flow. Growth is 49 dollars per month, and Enterprise pricing is quoted for larger estates.