FortiGate gets guests online. Spotipo turns them into customers.
Same firewall, very different result. The FortiGate native portal authenticates guests when policy order, DNS exemption and HTTPS interception all line up, but it captures no data and earns no revenue. Spotipo works alongside your FortiGate, delivers the portal reliably, and turns connections into leads.
Venues and MSPs that want marketing from WiFi
Cafes, hotels, retail and MSPs running FortiGate who want automatic email capture, CRM sync, branded splash pages, vouchers and paid WiFi, without the policy and DNS sequencing.
Security-led access with a network team
If FortiGate is already your security stack and you only need authenticated guest access managed alongside your policies, with no marketing or revenue, the native portal fits that setup.
Works with your hardware, 30+ brands
A built-in portal is made to authenticate, not to grow a business. These are the gaps people leave it for.
The native portal authenticates guests but leaves data in FortiGate and FortiAuthenticator. Spotipo captures email, phone and custom fields and syncs them to your CRM and email tools automatically.
No policy-order dependencies, no DNS exemption flags, no NAT routing changes, and no HTTPS interception errors. Spotipo delivers the splash page reliably across every device.
Branded splash pages, bulk vouchers, paid WiFi via Stripe, behaviour-triggered campaigns and a real-time dashboard. None of it ships with the native portal.
Honest, including where the other option wins. The rows that usually decide it: what you capture, how the portal behaves, and what you can do with the data.
It comes down to whether guest WiFi is just access, or a channel.
You want leads and revenue from guest WiFi
You want a branded portal that triggers reliably without policy work, captures contacts and can charge for access, alongside the FortiGate you already run.
You only need security-led guest access
If FortiGate is your security stack and authenticated access managed within your policies is all you need, the native portal does that within your licensing.
The most common cause is traffic matching an IP-based policy instead of the user-based policy with the portal enabled, or DNS not being exempted. Spotipo delivers the portal independently of FortiGate policy sequencing, so it triggers consistently.
Those errors come from HSTS and HTTPS interception with self-signed certificates on the native portal. Spotipo serves the portal with proper HTTPS, which removes the certificate warnings guests would otherwise hit.
Authentication data stays in FortiGate and FortiAuthenticator and has to be exported manually. Spotipo captures emails and custom fields directly and syncs them to your CRM automatically.
Yes. Your FortiGate continues managing network security, and Spotipo handles the guest experience as a separate layer. No FortiGate policy changes are required. Our FortiGate setup guide covers the captive-portal configuration step by step.
Yes. Manage every client site from one dashboard and white-label the splash pages, invoices and admin login. It is a core product, not an add-on.
An enterprise marketing suite versus a self-serve SMB and MSP platform.
An all-in-one single-venue app versus a white-label, multi-vendor platform.
ClearPass guest auth versus a portal with no role setup.
Spotipo vs MikroTik Native Hotspot Raw hotspot config versus a managed splash-page builder with setup help.
A licensed bundle versus a self-serve marketing captive portal.
The controller portal versus a dedicated WiFi marketing layer.
Its built-in guest portal versus a marketing-first platform that runs on it.