Skip to main content
MSP Deployment Guide

Deploy CaptiFi for Your Clients

Step-by-step deployment checklists for UniFi, Omada, Meraki and more. Get your first client site live in under an hour.

Three Deployment Paths

Existing Controller

Configure CaptiFi as the external captive portal on your existing UniFi, Omada, Meraki or Aruba controller.

CaptiFi Hardware

Plug in our pre-configured device. Connects to any existing network. No controller needed. Go live in about 5 minutes with the CaptiFi device.

Partner Hardware

Use your own compatible router or AP. Configure external portal redirect to point to CaptiFi.

Master Deployment Checklist

Complete every item before marking the site as live. This checklist applies to all deployment paths.

Client details confirmed

Business name, address, contact person, email, phone

Venue logo uploaded

PNG, JPG or WebP, minimum 200×200px; a PNG or WebP with a transparent background works best.

Splash page configured and approved

Branding, colours, login method, terms/privacy links

Controller type selected

UniFi, Omada, Meraki, Aruba, MikroTik, DrayTek, or CaptiFi hardware

Controller reachable by CaptiFi, if your set-up needs it

Only where CaptiFi talks to a controller you host. UniFi on the API key or username and password path, and an on-site Omada controller, need a public IP or hostname plus a firewall rule or port forward for HTTPS from CaptiFi. A Cisco Catalyst 9800 or AireOS controller needs UDP 1700 (9800) or 3799 (AireOS) open inbound from CaptiFi. The UniFi Remote Tunnel, Omada's paid Cloud-Based Controller and Meraki need no inbound access, and the CaptiFi device needs no static IP or firewall change.

Guest network configured

Separate SSID for guests, VLAN isolation from business network

Captive portal URL configured

External portal redirect pointing to CaptiFi splash URL

Test device connected successfully

Connect a phone/tablet to guest SSID, verify splash page loads

Data capture verified

Complete splash form, verify email/name appears in CaptiFi dashboard

Post-login redirect tested

After login, guest should reach the internet or a custom landing page

Client handover completed

Client briefed on dashboard access, data capture, and support process

Platform-Specific Guides

Prerequisites

  • UniFi Network Application running (self-hosted or Cloud Gateway)
  • CaptiFi can reach the controller: a public IP with a firewall rule or port forward, or the Remote Tunnel on a UniFi OS console, which needs no inbound ports
  • Guest network/SSID already created

Configuration Steps

  1. In Settings → WiFi, open the guest network and scroll to Hotspot Portal (older builds call this Settings → Guest Hotspot)
  2. Set Hotspot Portal to Enabled and the portal type to External Portal Server
  3. Enter CaptiFi's portal: IPv4 address 46.62.168.7 and domain site.app.captifi.io. On the API key and Remote Tunnel connections CaptiFi writes these settings for you
  4. Configure Pre-Authorization Access - add CaptiFi domains to the walled garden
  5. In the landing page settings, tick Show Landing Page, HTTPS Redirection Support, Encrypted URL and Secure Portal
  6. Switch off UniFi's own Password, Voucher, Facebook, Payment and RADIUS methods on the hotspot portal: CaptiFi authorises guests through the UniFi Controller API, so no RADIUS is needed
  7. Save and apply. Connect a test device to verify.

Walled Garden Domains

Add these to pre-authorization access:

site.app.captifi.io
app.captifi.io
fonts.googleapis.com
fonts.gstatic.com
*.captifi.io

The first four are required; the wildcard covers anything CaptiFi adds later, if your firmware accepts wildcards.

Troubleshooting

  • Splash not loading: Check walled garden includes CaptiFi domains
  • Redirect loop: Ensure only one portal is active (disable built-in UniFi portal)
  • Guest can't reach internet after login: Check VLAN routing and firewall rules

Configuration Steps

  1. Create an open guest SSID with Omada's Guest Network option off, and use a separate VLAN to keep guests away from your own devices
  2. Open Network Config → Authentication → Portal (Omada 5: Settings → Authentication → Portal), click Create New Portal, switch it on for the guest SSID and set Landing Page to Original URL
  3. On the Authentication tab, set Authentication Type to External Portal Server with a URL custom portal server: choose https:// and enter app.captifi.io/guest/omada?site_id=YOUR_SITE_ID
  4. On the Access Control tab, turn on Pre-Authentication Access and add app.captifi.io, 46.62.168.7 (IP range, mask 32), fonts.googleapis.com and fonts.gstatic.com. Omada does not accept wildcards
  5. Under Hotspot → Operators, add an operator account for CaptiFi, then enter the Controller URL, the 32-character Controller ID and the operator login for the venue on my.captifi.io
  6. Save and test with a guest device. With an Admin-role Open API app, CaptiFi can set up the portal and pre-authentication list on the controller for you

Configuration Steps

  1. Open Meraki Dashboard → Wireless → Configure → Splash page, pick the guest SSID and enter the CaptiFi splash URL under Custom splash URL, with Include the client MAC address in the splash URL switched on
  2. In Wireless → Configure → Access control, set Splash page to Click-through and Captive portal strength to Block all access until sign-on is complete
  3. Under Advanced splash settings, enable the walled garden and add app.captifi.io, site.app.captifi.io, *.captifi.io, network-auth.com, *.network-auth.com, fonts.googleapis.com and fonts.gstatic.com. Without the two network-auth.com entries Meraki never grants access
  4. Save changes. Test with a guest device on the configured SSID.

Setup Steps

  1. Connect the CaptiFi device to the venue's existing network by Ethernet and power it on
  2. The light flashes yellow while it boots (30 to 60 seconds), then turns solid purple: it is waiting to be activated
  3. Join the "CaptiFi Setup" network from a phone and enter the venue's 8-digit activation PIN
  4. The light pulses blue while the device pulls its configuration from the CaptiFi cloud, then turns solid green
  5. Connect a phone to the guest SSID and the splash page loads automatically
  6. The whole setup takes about five minutes from start to finish, with no controller, static IP or firewall change

Light guide: flashing yellow is booting, solid purple is waiting for the activation PIN, pulsing blue is configuring, solid green is live. Red means no internet, so check the cable into the router.

Need Help?

Partner Support

You provide first-line support to your clients. Email partners@captifi.io to escalate a technical issue to CaptiFi as second-line support, and say if a venue is down so we know it is urgent.

Before Escalating

  • Confirm it's not a local network issue
  • Verify controller connectivity
  • Test with a clean device (no cached portal)
  • Include screenshots and logs
Contact Partner Support

Not a Partner Yet?

Apply for the MSP Partner Programme to access wholesale pricing, deployment tools, and a 6-month internal demo licence for one internal test venue (testing and demos only).

Apply to Become a Partner