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 minutes.

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 or SVG, minimum 200×200px, transparent background preferred

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 externally

Static IP or DNS hostname, firewall rules allow HTTPS inbound

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)
  • Controller accessible via static IP or DNS hostname
  • Guest network/SSID already created

Configuration Steps

  1. Navigate to Settings → WiFi → Guest Hotspot
  2. Enable Guest Portal and select External Portal Server
  3. Set the portal URL to your CaptiFi splash page URL (provided in your partner dashboard)
  4. Configure Pre-Authorization Access — add CaptiFi domains to the walled garden
  5. Set guest authentication expiry (recommended: 24 hours)
  6. Enable RADIUS if using CaptiFi RADIUS auth (optional)
  7. Save and apply. Connect a test device to verify.

Walled Garden Domains

Add these to pre-authorization access:

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

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. Open Omada Controller → Authentication → Portal
  2. Select the guest SSID/network
  3. Set Portal Type to External RADIUS Server or External Portal Server
  4. Enter CaptiFi portal URL and shared secret (from partner dashboard)
  5. Configure pre-auth ACL to allow CaptiFi domains
  6. Save and test with a guest device

Configuration Steps

  1. Open Meraki Dashboard → Wireless → Access control
  2. Set Splash page to Click-through or Sign-on with external server
  3. Under Custom splash URL, enter the CaptiFi splash URL
  4. Add CaptiFi domains to Walled garden
  5. Save changes. Test with a guest device on the configured SSID.

Setup Steps

  1. Connect the CaptiFi device to the venue's existing network via Ethernet
  2. Power on the device — the LED will flash during boot (about 60 seconds)
  3. The device automatically connects to CaptiFi cloud and pulls its configuration
  4. A new guest SSID appears within 2 minutes
  5. Connect a phone to the guest SSID — the splash page should load automatically
  6. No controller, no static IP, no firewall changes needed

LED guide: solid blue = connected and ready. Flashing = booting. Red = error (contact support).

Need Help?

Partner Support SLA

  • P1 Critical: 4-hour response
  • P2 High: 8-hour response
  • P3 Normal: next business day
  • P4 Low: 2 business days

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 free demo licence.

Apply to Become a Partner