- Purple
- Captive portals: a complete guide
- How to Set Up Purple WiFi for the First Time: A Technical Overview
How to Set Up Purple WiFi for the First Time: A Technical Overview
You will be able to take a guest WiFi network from first login to live service in seven steps. You will apply Purple's RADIUS and walled garden settings to your existing access points, choose a sign-in method with marketing, and segment guest traffic away from payment systems. You will also learn to test on real devices and fix the faults that most often stall a first deployment.
📖 14 min read3,241 words3 worked examples3 practice questions12 key definitions
Video overview
Listen to this guide
View podcast transcript
How to Set Up Purple WiFi for the First Time: A Technical Overview
A Purple Platform & Data Podcast
[INTRODUCTION & CONTEXT - approximately 1 minute]
Welcome back. If you're listening to this, you're probably either evaluating Purple as your guest WiFi platform, or you've just signed a contract and you're wondering what the next 48 hours look like for your IT team. Either way, you're in the right place.
I'm going to walk you through exactly what it takes to get Purple live - from the moment you register your account to the moment your first guest connects and your analytics dashboard starts populating. We'll cover the technical architecture, the hardware integration, the portal configuration, and the compliance considerations that your legal team will want to see addressed.
This isn't a sales pitch. Think of it as a briefing from a solutions architect who's done this deployment dozens of times across hotels, retail chains, conference centres, and public-sector venues. I'll tell you what works, what trips people up, and what you should absolutely do before you touch a single access point.
Let's get into it.
[TECHNICAL DEEP-DIVE - approximately 5 minutes]
First, let's establish what Purple actually is at a technical level, because understanding the architecture makes the setup process make a lot more sense.
Purple is a cloud-hosted guest WiFi intelligence platform. The key word there is cloud-hosted. Unlike legacy captive portal solutions that required you to run a dedicated on-premise server - a RADIUS box, a portal server, the whole stack - Purple runs its authentication and portal management infrastructure in the cloud. Your access points communicate with Purple's cloud platform to handle authentication, session management, and data collection. That means your on-site hardware footprint is minimal. You're essentially configuring your existing access points to redirect unauthenticated traffic to Purple's captive portal endpoint, and Purple handles everything from there.
Now, let's talk about the captive portal mechanism itself, because this is where a lot of IT teams have misconceptions. When a guest connects to your WiFi SSID, their device's operating system - whether that's iOS, Android, Windows, or macOS - automatically sends a probe request to a known endpoint. On iOS, that's captive.apple.com. On Android, it's connectivitycheck.gstatic.com. Your access point intercepts that request and redirects it to Purple's splash page. This is the Captive Network Assistant, or CNA, triggering the familiar login popup that guests see.
The critical configuration element here is the Walled Garden. Before a guest authenticates, their device can only reach a pre-approved list of URLs. This list must include Purple's portal domain, any social login providers you're using - Facebook, Google - and any other resources required for the authentication flow to complete. If your walled garden is misconfigured, guests will see a portal that fails to load, or social login buttons that don't respond. This is the number one cause of support tickets in new deployments, so get your walled garden right from the start.
Now, let's walk through the actual setup sequence. There are seven distinct phases.
Phase one is account registration. You fill out the registration form on purple.ai, verify your email within 24 hours - that's a hard deadline, the link expires - and set your portal password. Straightforward, but don't skip the email verification step and then wonder why your account isn't active.
Phase two is venue configuration. In Purple's terminology, a Venue is the top-level entity that maps to a physical location. You'll enter the venue name, address, and type - hotel, retail, stadium, whatever applies. This matters because Purple's analytics engine uses venue metadata to contextualise the data it collects. If you're a multi-site operator, you'll also be configuring Groups, which allow you to manage multiple venues under a single hierarchy and apply consistent policies across your estate.
Phase three is splash page design. Purple gives you two splash page types. The Offline Splash Page is what guests see immediately upon connecting, before they've authenticated. This is your captive portal - the login screen. The Online Splash Page is what guests see after successful authentication, essentially a landing page confirming they're connected. For the offline page, you have two editor options: the standard drag-and-drop builder, which is perfectly capable for most deployments, and the Custom HTML editor for teams that need pixel-perfect brand alignment or complex form logic.
Phase four is access journey configuration. An Access Journey in Purple is essentially the end-to-end authentication flow - it ties your splash page to your authentication method, your terms and conditions, any data capture forms, and your post-authentication redirect URL. You can configure multiple access journeys for different user segments. A hotel might have one journey for leisure guests, another for conference delegates, and a third for long-stay residents. Each journey can have different authentication requirements, data capture fields, and session duration policies.
Phase five is hardware integration. This is where it gets interesting from a network engineering perspective. Purple supports over 50 hardware vendors - Cisco, Cisco Meraki, Aruba, Ruckus, Juniper Mist, Fortinet, Extreme Networks, Ubiquiti, TP-Link Omada, Huawei, Mikrotik, and many more. The integration method varies by vendor, but the general pattern is consistent: you add your access point or controller in the Purple portal by providing its MAC address and hardware type, and Purple generates the specific placeholder settings - RADIUS server address, shared secret, captive portal URL - that you then configure on your hardware.
For Cisco Meraki, for example, you'd configure a new SSID in the Meraki dashboard, set the splash page type to "Click-through" or "Sign-on with Purple", enter the RADIUS server details Purple provides, and configure the walled garden entries. For Aruba Instant APs, the process involves configuring a guest SSID with external captive portal settings pointing to Purple's portal URL. Each vendor has a dedicated setup guide in Purple's support portal, and you can also access the full guide directly from within the Purple portal under Management, then Venues, then Hardware.
Phase six is testing and validation. Before you go live, connect a test device to your guest SSID and verify the full authentication flow. Check that the captive portal appears correctly on iOS, Android, and Windows devices - they all handle the CNA differently. Verify that your walled garden is correctly configured by attempting to access a social login provider before authenticating. Check that your post-authentication redirect URL is working. And confirm that authenticated sessions are appearing in your Purple analytics dashboard.
Phase seven is going live and monitoring. Once you're satisfied with the test results, publish your access journey in the Purple portal. From this point, every guest who connects will flow through your configured journey, and their session data will begin populating your analytics dashboard in near real-time.
[IMPLEMENTATION RECOMMENDATIONS & PITFALLS - approximately 2 minutes]
Let me give you the three things that consistently separate smooth deployments from painful ones.
First: plan your network segmentation before you touch Purple. Your guest WiFi should be on a dedicated VLAN, completely isolated from your corporate or operational network. This isn't just best practice - it's a compliance requirement under PCI DSS if you're processing any card payments on the same network infrastructure, and it's strongly recommended under GDPR for data minimisation purposes. If you're deploying in a hotel environment, your property management system, your point-of-sale terminals, and your back-office systems should be on entirely separate network segments from your guest WiFi. Get this right in your network design before you configure a single Purple setting.
Second: don't underestimate the walled garden configuration. I've already mentioned this, but it bears repeating. Every authentication provider you enable in Purple needs to be whitelisted in your walled garden. If you're using Facebook social login, you need to whitelist Facebook's CDN domains, not just facebook.com. Purple's support documentation provides the complete list of domains for each authentication method, and I'd strongly recommend copying that list verbatim rather than trying to infer it.
Third: address MAC address randomisation proactively. Modern iOS and Android devices randomise their MAC address by default when connecting to WiFi networks. This is a privacy feature, but it has implications for how Purple tracks returning visitors. If a guest's device presents a different MAC address on each visit, Purple will treat them as a new user each time, which affects your return visitor analytics and can cause issues with seamless reconnection features. Purple has mechanisms to handle this - including the Purple App, which uses a persistent identity rather than MAC address for recognition - but you need to understand this limitation before you promise your marketing team that you'll have accurate return visitor rates from day one.
[RAPID-FIRE Q&A - approximately 1 minute]
Let me run through the questions I get asked most frequently.
"Do I need to replace my existing access points?" Almost certainly not. Purple works as an overlay on your existing hardware from over 50 vendors. You're configuring your existing infrastructure to redirect to Purple's cloud platform, not replacing it.
"How long does a typical deployment take?" For a single venue with existing compatible hardware, most IT teams complete the Purple configuration in under two hours. The network segmentation and VLAN configuration on your existing infrastructure is typically the longest part of the process.
"Is Purple GDPR compliant?" Yes. Purple is ISO-certified and provides GDPR and CCPA-compliant data capture mechanisms, including explicit consent collection and data minimisation controls. Your legal team will want to review the data processing agreement, which is available on request.
"Can I manage multiple venues from a single account?" Yes. Purple's multi-venue management allows you to manage your entire estate from a single portal, with role-based access control so different team members can manage specific venues or venue groups.
[SUMMARY & NEXT STEPS - approximately 1 minute]
To summarise: Purple WiFi setup is a seven-phase process - register, verify, configure your venue, design your splash pages, set up your access journeys, integrate your hardware, and go live. The technical complexity is manageable for any competent IT team, and Purple's cloud-hosted architecture means you're not maintaining any on-premise server infrastructure.
The three things to get right before anything else: network segmentation and VLAN isolation, walled garden configuration, and understanding how MAC address randomisation will affect your analytics.
If you're deploying across multiple venues, I'd recommend starting with a single pilot venue, validating the full guest journey end-to-end, and then using that configuration as your template for the broader rollout.
Purple's support portal at support.purple.ai has detailed hardware-specific guides for every supported vendor. If you're working with a solutions partner, they'll have access to Purple's partner resources for enterprise deployments.
Thanks for listening. If you found this useful, the full written guide with architecture diagrams, worked examples, and a hardware compatibility reference is available on the Purple platform. Good luck with your deployment.
Part of our core series: Captive Portal Guide →
- What does a Purple WiFi setup actually do?
- How a guest gets online
- What the captive portal does not do
- What do you need before you start your Purple WiFi setup?
- Hardware Purple supports
- Network prerequisites
- Compliance decisions to settle first
- How do you set up Purple WiFi, step by step?
- Step 1: create your account and verify it
- Step 2: add your venues and group them
- Step 3: design the captive portal pages guests see
- Step 4: choose how guests sign in
- Step 5: apply Purple's settings to your hardware
- Step 6: test before you go live
- Step 7: go live and watch the first sessions
- How do you check your Purple WiFi configuration works?
- What does a first deployment look like in practice?
- Worked scenario: a 200-room hotel on Cisco Meraki
- Worked scenario: a 40-store retail chain on mixed hardware
- What goes wrong, and how do you fix it?
- What does Purple WiFi cost, and what do you get back?
- What you get back
- Frequently asked questions
- Do I need new access points to set up Purple WiFi?
- How much does Purple WiFi cost?
- Can we move from our current captive portal provider without downtime?
- Is Purple GDPR compliant?
- Can guests connect without seeing a captive portal?
- How is Purple different from the splash page built into my access points?
- Does adding guest WiFi affect our PCI DSS scope?
Interactive Hardware Onboarding Tool
Purple WiFi Multi-Vendor Deployment Configurator
Select your wireless hardware vendor and deployment model to generate exact RADIUS endpoints, walled garden domain allowlists, redirect parameters, and ready-to-use CLI/GUI scripts.
24 APs
Primary RADIUS Host (EU / US Anycast)
<purple-radius-primary>
Auth Port: 1812 UDP
Acct Port: 1813 UDP
Shared Secret: From Purple Portal
Acct Interim: 600s
Secondary RADIUS Host (Redundant Failover)
<purple-radius-secondary>
Auth Port: 1812 UDP
Acct Port: 1813 UDP
Shared Secret: From Purple Portal
CoA Support: RFC 3576 (3799)
Vendor Specific External Redirection Target
https://portal.purplewifi.net/?res=notyet&client_mac=$MAC&node_mac=$APMAC&called=$SSID
UI Location: Wireless > Configure > Access control > SSID > Splash page: Sign-on with "my RADIUS server"
Architectural Insight: Meraki Cloud automatically handles client redirection and MAC parameter encapsulation without needing custom firmware.
Deploying Purple across 24 Access Points in your enterprise?
Have our certified network architects review your RADIUS configuration and captive portal policies before going live.
Useful? Link to this tool
Purple WiFi setup takes seven steps. Create your account, add each venue, design the splash page and choose a sign-in method. Apply Purple's RADIUS and walled garden settings to your access points, test on iOS, Android and Windows, then go live. Purple runs as a cloud overlay, so Cisco Meraki, HPE Aruba or Ruckus hardware needs no on-site server.
What does a Purple WiFi setup actually do?
Purple layers on top of the access points you already own. You keep your radios, your controller and your switching. Purple adds three cloud services: the captive portal guests sign in through, a cloud RADIUS service that approves each session, and the WiFi Analytics that record each visit. Nothing new goes into your comms room.
Two definitions first. A captive portal is the web page a network shows a device before it grants internet access. RADIUS (Remote Authentication Dial-In User Service, defined in RFC 2865) is the protocol your controller uses to ask an outside server whether a device may connect.
How a guest gets online
Every Purple Guest WiFi session follows the same sequence, whatever hardware you run:
- The guest joins your guest SSID, the network name shown in their device's WiFi list.
- The device's captive network assistant (CNA) probes a known address to test for open internet. Apple devices request captive.apple.com. Android devices request connectivitycheck.gstatic.com.
- Your controller intercepts that probe and redirects the device to the Purple-hosted splash page.
- Until the guest signs in, the device sits inside a walled garden. This is a firewall allow list of the only domains reachable before authentication. It holds Purple's portal domains, plus any social login providers and their content delivery networks.
- The guest signs in. Purple's cloud RADIUS returns an Access-Accept message, and your controller releases the device to the internet.
- Your controller sends RADIUS accounting records (RFC 2866) to Purple when each session starts and stops. Those records feed session length and visit data into your dashboard.
What the captive portal does not do
A captive portal controls who gets on. It does not encrypt traffic. Guest SSIDs that use a splash page are usually open networks. Traffic between the device and the access point is therefore not encrypted at the radio layer. Plan for that rather than assuming the sign-in step protects data in transit.
Where you need encrypted guest access, Purple's SecurePass add-on uses IEEE 802.1X. This standard requires every device to authenticate before the network passes its traffic. It runs with WPA2-Enterprise or WPA3-Enterprise, which derive unique encryption keys for each session. No splash page is involved. You can run both on separate SSIDs: a captive portal for walk-in guests, and SecurePass for corporate visitors or long-stay guests.
What do you need before you start your Purple WiFi setup?
You need four things: supported hardware, a segmented network, open paths to Purple's cloud and agreed decisions on data. Settle all four before step 1.
Hardware Purple supports
Purple is hardware-agnostic. You do not rip and replace anything. You configure the management plane you already use. The table shows where your Purple settings go for each supported vendor.
| Vendor | Where you apply Purple's settings | What you configure |
|---|---|---|
| Cisco Meraki | Meraki Dashboard | Guest SSID, splash page redirect, RADIUS servers, walled garden |
| HPE Aruba | Aruba Central, Instant AP cluster or Mobility Controller | External captive portal profile, RADIUS servers, walled garden |
| Ruckus | SmartZone controller | Hotspot WLAN with external portal, RADIUS servers, walled garden |
| Juniper Mist | Mist cloud dashboard | WLAN with external guest portal, RADIUS servers, allowed hostnames |
| Ubiquiti UniFi | UniFi Network application | Guest hotspot with external portal server, pre-authorisation access list |
| Cambium | cnMaestro | Guest access with external hotspot, RADIUS servers, walled garden |
| Extreme | ExtremeCloud IQ | Captive web portal, RADIUS servers, walled garden |
| Fortinet | FortiGate wireless controller | SSID with external captive portal, RADIUS servers, exempt destinations |
Purple generates the values for your venue and hardware. These cover the RADIUS server addresses, the shared secret, the portal URL and the walled garden list. Use those values exactly as issued. Never copy them from another venue or an old configuration. The step-by-step guide for each vendor sits in the Purple support centre.
Network prerequisites
- A dedicated guest VLAN. A VLAN (virtual LAN, IEEE 802.1Q) splits one physical network into isolated logical segments. Give guest traffic its own VLAN with internet-only firewall rules.
- A DHCP scope sized for peak. Size the address pool for your busiest hour, not your average day. Short lease times free addresses as guests leave.
- DNS that works before sign-in. Guest devices must resolve the CNA probe domains and Purple's portal domains while still inside the walled garden.
- Outbound RADIUS from your controller. Standard RADIUS uses UDP 1812 for authentication and UDP 1813 for accounting. Open the ports and addresses Purple issues for your venue.
- Admin rights and a change window. You need write access to your controller or cloud dashboard. You also need time to test before guests depend on the network.
Compliance decisions to settle first
Segmentation also sets your PCI DSS scope. PCI DSS v4.0 does not mandate segmentation. Without it, though, every connected system falls into scope for assessment. Keep payment terminals, the property management system and back-office systems off the guest VLAN. The same logic protects clinical systems in Healthcare settings. Patient and visitor WiFi must never route to them.
Data capture needs the same care. Under GDPR Article 4(11), consent must be freely given, specific, informed and unambiguous. Agree three points with marketing before you build: the fields you collect, the consent wording and the privacy notice link. Purple's conscious-choice opt-ins mean a guest actively chooses marketing consent. It is never bundled into the terms that get them online.
How do you set up Purple WiFi, step by step?
Order matters. Build the venue, pages and sign-in rules in Purple first, then point the hardware at them. Your first test then lands on a finished page.
Step 1: create your account and verify it
Register at purple.ai and confirm your email address from the verification message. The link is time-limited, so act on it the same day. Set a strong password and store it in your password manager. Give each administrator their own login rather than sharing one account.
Step 2: add your venues and group them
A venue in Purple maps to one physical site. Enter its name, address and category, such as hotel, store, stadium or conference centre. Purple uses this metadata to compare sites in your analytics, so complete it accurately.
Multi-site operators add a group above their venues. A group applies the same splash pages, sign-in rules and reports to many sites at once. A 40-store chain creates one group and adds each store as a venue beneath it. You manage centrally and still report store by store.
Step 3: design the captive portal pages guests see
Purple portal setup covers two pages. The offline splash page is the captive portal itself, shown before sign-in. It must load fast inside the walled garden, carry your brand and make the sign-in action obvious.
The online splash page appears after sign-in. Use it to confirm the connection or send guests to a useful address. A booking engine, a loyalty sign-up or today's offers all work well.
The drag-and-drop editor covers most venues. Teams that need exact brand control or custom form logic can use the custom HTML editor. Host every image, font and script on an allowed domain. Anything outside the walled garden will not load before sign-in.
Step 4: choose how guests sign in
Next, tie the splash page to a sign-in method, terms and conditions, session length and post-login redirect. One venue can run several of these configurations side by side. A conference centre might give the public a click-through, delegates a form with marketing consent, and exhibitors a voucher.
| Sign-in method | What you capture | Effort for the guest | Encrypted over the air | Best fit |
|---|---|---|---|---|
| Click-through terms | Terms acceptance, device and session data | One tap | No | Libraries, stations, Trains, high-volume public spaces |
| Form | The fields you choose, plus opt-in marketing consent | Short form | No | Hotels, Retail, restaurants |
| Social login | Profile details the provider shares with consent | Two or three taps | No | Bars, leisure venues, events |
| Voucher code | Code issued by staff or at booking | Code entry | No | Conference exhibitors, premium bandwidth tiers |
| SecurePass (IEEE 802.1X) | Verified identity credential | One-time setup, then automatic | Yes, WPA2- or WPA3-Enterprise | Corporate visitors, long-stay guests |
Agree the choice with marketing before you build. Click-through maximises connections but yields little data. Forms yield the data you choose but add friction. Social login data is only as accurate as the guest's profile.
Step 5: apply Purple's settings to your hardware
Network engineers own this step. Register each access point or wireless LAN controller against its venue in Purple, with vendor, model and MAC address. Purple then generates the values for that hardware. These are the RADIUS server addresses and shared secret, the external captive portal URL and the walled garden domain list.
Apply the values in the management plane from the hardware table above. On Cisco Meraki, you configure the guest SSID in Meraki Dashboard. On HPE Aruba, you add an external captive portal profile and RADIUS servers to the Instant AP cluster or controller. On Ruckus, you build the WLAN on the SmartZone controller.
Follow the vendor guide in the Purple support centre field by field. Paste values rather than retyping them. One wrong character in a shared secret rejects every sign-in.
Enable RADIUS accounting as well. Without it, guests still get online, but your analytics stay empty.
Step 6: test before you go live
Run the full checklist in the next section on every device type. Do not publish until each check passes.
Step 7: go live and watch the first sessions
Publish the configuration and broadcast the guest SSID. From then on, Purple handles every sign-in on that network. Watch the dashboard through the first busy period. Check active sessions, the sign-in method breakdown and new versus returning visitors. Schedule reports for venue managers, marketing and IT.
Got questions about your specific setup?
Our team works with venue operators, IT managers, and network engineers across 80,000 venues. Book a 20-minute call and we will show you how others like you solved it.
How do you check your Purple WiFi configuration works?
Test with real phones, not only a laptop on the bench. Each operating system handles captive portals differently.
- The portal appears unprompted. Join the SSID on an iPhone, an Android phone and a Windows laptop. The splash page should open automatically on each.
- Every sign-in method completes. Run each method you configured end to end, including social login and voucher entry.
- The redirect lands. After sign-in, the online splash page or target address loads correctly.
- Sessions reach the dashboard. Test sessions appear in Purple in near real time. Disconnect and confirm each session closes, which proves accounting works.
- Segmentation holds. From a signed-in guest device, try to reach an internal address, such as a printer. The attempt must fail.
- Returning devices behave. Reconnect a device that has already signed in. Confirm Purple treats it according to the session length you set.
- Peak load is covered. Check the DHCP pool against your busiest hour. Confirm the uplink can carry the per-device bandwidth you allow.
What does a first deployment look like in practice?
The two scenarios below are worked examples built from the steps above. They show the decisions an IT team makes and the outcomes it can measure.
Worked scenario: a 200-room hotel on Cisco Meraki
Situation. A 200-room hotel runs Cisco Meraki access points across one flat network. Guests, the restaurant's card terminals and the property management system all share it. Marketing collects no consented guest data from WiFi.
What was done. IT created a guest VLAN with internet-only rules. Card terminals and the property management system moved to their own segment. The team built one venue in Purple, with form and social sign-in. The online splash page links to the booking engine. IT applied Purple's RADIUS and walled garden values in Meraki Dashboard. They then ran the seven-point checklist on iOS, Android and Windows.
Outcome. The PCI DSS assessment scope narrowed from the whole property network to the payment segment. Two legacy guest SSIDs were retired, leaving one. Every sign-in now creates a first-party record. Marketing consent exists only where the guest chose to give it.
Worked scenario: a 40-store retail chain on mixed hardware
Situation. A 40-store fashion retailer runs HPE Aruba in large stores and Ubiquiti UniFi in small ones. Each store ran its own vendor splash page. Consent records sat in 40 separate places.
What was done. IT created one group in Purple, with one set of splash pages and form plus social sign-in. They piloted one representative store first. The pilot exposed a missing content delivery network domain in the walled garden. That gap broke social login on Android. IT fixed the domain list once. The pilot configuration then became the template for the other 39 stores.
Outcome. The walled garden gap was fixed in one store instead of surfacing in 40. Consent records moved from 40 local systems into one platform. Store-by-store reports now compare shopper visits across both hardware brands in one dashboard.
What goes wrong, and how do you fix it?
Check three places first: the walled garden, the RADIUS values and device privacy features. The table maps each symptom to its fix.
| Symptom | Likely cause | Fix |
|---|---|---|
| Splash page never appears on iPhones | DNS or firewall blocks the CNA probe to captive.apple.com, or the redirect rule is not attached to the SSID | Allow DNS for the probe domain on the guest VLAN and attach the redirect rule to the guest SSID |
| Certificate warning instead of the portal | The guest opened an HTTPS site, and the controller cannot redirect encrypted traffic cleanly | Let the CNA probe trigger the redirect; ask guests to wait for the sign-in sheet rather than opening a browser |
| Social login button spins or fails | Provider API or content delivery network domains are missing from the walled garden | Add every domain on Purple's list for that provider, then retest on iOS and Android |
| Every sign-in is rejected | Shared secret or RADIUS server address does not match Purple's values | Paste the values again from Purple and confirm UDP 1812 is open outbound |
| Returning guests must sign in again | Short session length, or MAC randomisation: iOS 14 and Android 10 onwards use a private address per network by default | Extend the session length; offer the Purple app or SecurePass for recognition across visits |
| Slow browsing after sign-in | Saturated uplink or a per-device limit set too tight | Measure peak demand and adjust the per-device bandwidth limit |
| Dashboard stays empty while guests connect | RADIUS accounting is off, or UDP 1813 is blocked | Enable accounting, match Purple's accounting server and port, and open the port outbound |
| Guests can reach internal devices | Guest SSID tagged to the wrong VLAN, or a missing firewall deny rule | Re-tag the SSID and deny guest traffic to private RFC 1918 address ranges, except the gateway and DNS |
RFC 1918 defines the private address ranges most internal networks use: 10.0.0.0/8, 172.16.0.0/12 and 192.168.0.0/16.
What does Purple WiFi cost, and what do you get back?
Purple prices Guest WiFi through three plans: Connect, Capture and Engage. Purple quotes each estate against the plan you choose and the number of venues. The bigger difference shows in the cost lines you no longer carry.
| Cost line | Self-hosted captive portal and RADIUS | Purple cloud overlay |
|---|---|---|
| RADIUS servers | You buy, host, patch and back them up | Purple runs cloud RADIUS |
| Portal hosting | You run web servers and TLS certificates | Purple hosts the splash pages |
| Access points | Existing hardware | Existing hardware from the eight supported vendors |
| Availability | Your own redundancy design | 99.999% uptime (Purple's own figure) |
| Security assurance | Your own audits | Purple holds ISO 27001 and Cyber Essentials certification |
| Effort per new site | Server, portal and access point build | Access point settings applied from a group template |
What you get back
Your hardware stays. Purple layers on top of existing infrastructure, so no access points come out of the ceiling.
First-party data with consent. Each form or social sign-in creates a consented record. WiFi Analytics then reports visits, dwell time and new versus returning visitors per venue. Purple integrates with CRM and marketing platforms, so that data reaches the teams who act on it.
One platform across mixed estates. Group templates and one dashboard replace per-site, per-vendor configuration.
Proven scale. Purple was founded in 2012. It runs at 80,000+ live venues in more than 90 countries and handles 500 million users and logins a year (all Purple's own data). Purple is also B Corp certified.
Frequently asked questions
Do I need new access points to set up Purple WiFi?
No. Purple is hardware-agnostic and runs as a cloud overlay on access points you already own. Supported vendors are Cisco Meraki, HPE Aruba, Ruckus, Juniper Mist, Ubiquiti UniFi, Cambium, Extreme and Fortinet. You apply Purple's RADIUS, captive portal and walled garden settings in your existing management plane, such as Meraki Dashboard or a SmartZone controller. No on-site server is needed, because Purple hosts the portal and RADIUS in the cloud.
How much does Purple WiFi cost?
Purple prices Guest WiFi through three plans, Connect, Capture and Engage, and quotes each estate against the plan and venue count. You do not buy or maintain on-site RADIUS or portal servers, because Purple runs both in the cloud. Your remaining costs are the access points you already own, internet bandwidth and engineer time to configure each site. Ask Purple for a quote against your venue list.
Can we move from our current captive portal provider without downtime?
Yes, if you build Purple on a test SSID alongside your live one. Create your venue, splash pages and sign-in rules in Purple first. Then broadcast the test SSID with Purple's settings and run the full checklist on iOS, Android and Windows. When every check passes, move the production SSID across in your change window. Guests see a new splash page, not an outage.
Is Purple GDPR compliant?
Yes. Purple is GDPR and CCPA compliant, and holds ISO 27001 and Cyber Essentials certification. You choose the fields on your splash page, write the consent wording and link your privacy notice. Purple's conscious-choice opt-ins keep marketing consent separate from connection, so a guest can get online without agreeing to marketing. That separation supports the GDPR requirement that consent is freely given and specific.
Can guests connect without seeing a captive portal?
Yes. Purple's SecurePass add-on uses IEEE 802.1X with WPA2- or WPA3-Enterprise. Devices authenticate once, then connect automatically on later visits with no splash page. Each session gets its own encryption keys, which an open captive portal SSID does not provide. SecurePass suits corporate visitors and long-stay guests. You can run it on its own SSID alongside a captive portal for walk-in visitors.
How is Purple different from the splash page built into my access points?
Purple gives you one platform across every site and every supported vendor. Built-in splash pages are configured per vendor and often per site. A mixed Cisco Meraki and Ubiquiti UniFi estate ends up with separate pages, consent records and reports. Purple centralises splash pages, sign-in rules, consent capture and analytics in one dashboard. It runs at 80,000+ live venues in more than 90 countries (Purple's own data).
Does adding guest WiFi affect our PCI DSS scope?
Only if guest traffic can reach your cardholder data environment. PCI DSS v4.0 does not mandate segmentation, but without it every connected system falls into scope. Put the guest SSID on its own VLAN with internet-only firewall rules. Keep payment terminals on a separate segment. Then prove it: from a signed-in guest device, try to reach an internal address. The attempt must fail.
Key Definitions
Captive portal
A web page a network shows an unauthenticated device before granting internet access, usually on an open SSID. It controls admission only and adds no radio-layer encryption.
This is the splash page your guests see. You meet it in Step 3, and you plan around the fact that it does not protect data in transit.
RADIUS
Remote Authentication Dial-In User Service, defined in IETF RFC 2865. A controller sends an Access-Request to a server, which replies with Access-Accept or Access-Reject. Standard authentication runs on UDP 1812.
Purple runs RADIUS in the cloud. You enter Purple's server addresses and shared secret in Step 5, and a mismatch rejects every sign-in.
RADIUS accounting
The accounting extension to RADIUS defined in IETF RFC 2866. The controller sends start and stop records for each session, conventionally on UDP 1813.
These records feed session length and visit data into Purple. If accounting is off or UDP 1813 is blocked, your dashboard stays empty.
Walled garden
A firewall allow list of the only domains a device can reach before it authenticates. It holds the portal domains plus any social login providers and their content delivery networks.
A missing domain breaks sign-in. In the retail pilot, one absent content delivery network domain broke social login on Android.
Captive network assistant (CNA)
The operating system component that probes a known address to test for open internet, such as captive.apple.com on Apple devices and connectivitycheck.gstatic.com on Android.
Your controller intercepts this probe to open the splash page. If DNS or the firewall blocks it, the portal never appears.
IEEE 802.1X
The IEEE standard for port-based network access control. Every device must authenticate through EAP before the network passes its traffic, with RADIUS as the usual authentication back end.
Purple's SecurePass add-on uses 802.1X to give corporate visitors and long-stay guests encrypted access with no splash page.
WPA2-Enterprise and WPA3-Enterprise
Security modes built on IEEE 802.11 that use 802.1X authentication and derive unique encryption keys for each session, rather than a shared passphrase or an open network.
You choose these when guest traffic must be encrypted over the air. They run on a separate SSID alongside your captive portal.
VLAN
A virtual LAN as specified in IEEE 802.1Q, which tags frames to split one physical network into isolated logical segments.
A dedicated guest VLAN with internet-only rules is a prerequisite. It keeps guests away from payment terminals, the property management system and clinical systems.
RFC 1918 private address ranges
IETF RFC 1918 reserves 10.0.0.0/8, 172.16.0.0/12 and 192.168.0.0/16 for private internal networks.
Deny guest traffic to these ranges, except the gateway and DNS, then prove it by trying to reach an internal printer from a signed-in device.
PCI DSS segmentation
PCI DSS v4.0, published by the PCI Security Standards Council, does not mandate network segmentation. Without it, every connected system falls into assessment scope.
Segmenting the guest VLAN from payment systems narrowed the hotel scenario's assessment scope to the payment segment alone.
GDPR consent, Article 4(11)
Regulation (EU) 2016/679 Article 4(11) defines consent as freely given, specific, informed and unambiguous indication of the data subject's wishes.
Purple's conscious-choice opt-ins keep marketing consent separate from getting online, which supports this definition on every form or social sign-in.
MAC randomisation
A device privacy feature where iOS 14 and Android 10 onwards use a private hardware address per network by default.
It explains returning guests being asked to sign in again. Longer session lengths, the Purple app or SecurePass restore recognition across visits.
Worked Examples
A 200-room hotel runs Cisco Meraki access points on one flat network shared by guests, restaurant card terminals and the property management system. Marketing collects no consented guest data from WiFi. How should IT deploy Purple?
IT created a guest VLAN with internet-only rules and moved the card terminals and property management system to their own segment. The team built one venue in Purple with form and social sign-in. The online splash page links to the booking engine. IT applied Purple's RADIUS and walled garden values in Meraki Dashboard, then ran the seven-point checklist on iOS, Android and Windows. Segmentation narrowed the PCI DSS assessment scope from the whole property network to the payment segment. Two legacy guest SSIDs were retired, leaving one. Every sign-in now creates a first-party record, with marketing consent only where the guest chose to give it.
A 40-store fashion retailer runs HPE Aruba in large stores and Ubiquiti UniFi in small ones. Each store has its own vendor splash page, and consent records sit in 40 separate places. How do you roll out one configuration safely?
IT created one group in Purple with one set of splash pages and form plus social sign-in. They piloted one representative store first. The pilot exposed a missing content delivery network domain in the walled garden, which broke social login on Android. IT fixed the domain list once, and the pilot configuration became the template for the other 39 stores. The gap was fixed in one store instead of surfacing in 40. Consent records moved from 40 local systems into one platform. Store-by-store reports now compare shopper visits across both hardware brands in one dashboard.
You already run a captive portal from another provider and cannot afford guest downtime during the move to Purple. How do you switch?
Build Purple on a test SSID alongside your live one. Create your venue, splash pages and sign-in rules in Purple first. Then broadcast the test SSID with Purple's RADIUS, portal URL and walled garden settings. Run the full checklist on iOS, Android and Windows, including segmentation and accounting checks. When every check passes, move the production SSID across in your change window. Guests see a new splash page, not an outage, because the configuration was proven before it carried live traffic.
Practice Questions
Q1. You are deploying Purple in a 20,000-capacity stadium with high-density WiFi requirements. During peak event times, you anticipate over 12,000 concurrent authenticated users. What is your primary technical consideration regarding the underlying network infrastructure, and how does Purple's architecture mitigate or exacerbate this challenge?
Hint: Consider the path of both the authentication traffic and the subsequent internet traffic, and where the bottlenecks are most likely to occur.
View model answer
The primary consideration is the capacity and performance of the on-premise Wireless LAN Controller (WLC) and the internet gateway. While Purple's authentication is cloud-based, all guest traffic - including the initial captive portal redirect, the RADIUS accounting packets, and the subsequent internet traffic - must pass through the venue's own network hardware. The WLC must be able to handle the high volume of RADIUS authentication and accounting packets during peak connection events (e.g., when gates open and thousands of devices connect simultaneously). The internet gateway must have sufficient bandwidth and processing power to manage 12,000+ concurrent sessions. Purple's cloud architecture mitigates the server-side load by handling the portal and RADIUS processing in the cloud, but the on-premise hardware remains the critical bottleneck. The recommended approach is to ensure the WLC is properly sized, the internet uplink has sufficient headroom, and bandwidth-per-device limits are configured in the Access Journey to prevent any single user from consuming a disproportionate share of capacity.
Q2. Your marketing team wants to use a highly stylised, graphically-intensive video on the captive portal splash page to promote a new product launch. What is the main technical risk associated with this request, and how would you advise them to achieve their marketing objective without compromising the user experience?
Hint: Consider the user's network state and available bandwidth at the precise moment the splash page is displayed.
View model answer
The main risk is poor user experience and high abandonment rates. Before authentication, the user is on a restricted network with limited bandwidth - they are in the walled garden, and only the portal's whitelisted domains are accessible. A large video file will load slowly or fail to load entirely, leading to user frustration and a high proportion of guests abandoning the connection attempt. I would advise the marketing team to use a lightweight, optimised static image on the Offline Splash Page (the captive portal) to ensure a fast loading time and a high authentication completion rate. The video would be far more effective on the Online Splash Page, which is displayed after the user has successfully authenticated and has full, high-speed internet access. This approach achieves the marketing objective without compromising the critical first-impression user experience.
Q3. A public-sector client wants to provide free WiFi in a city library. They are concerned about their legal obligations regarding illegal content and the safeguarding of vulnerable users, including children. Which Purple feature would you highlight to address this concern, and what additional steps would you recommend to ensure the client has a defensible compliance position?
Hint: Think about both the technical controls available and the policy and legal framework that must surround them.
View model answer
I would highlight Purple's Shield content filtering feature, which allows the organisation to block access to specific categories of websites - including adult content, gambling, extremist material, and malware sites - at the network level. This provides a meaningful technical control. However, I would strongly advise the client that technical filtering alone is not sufficient for a defensible compliance position. Additional steps should include: publishing a clear Acceptable Use Policy (AUP) that users must accept before connecting; configuring the Access Journey to require explicit acceptance of the AUP; retaining session logs for a legally appropriate period in accordance with data retention policies; and conducting a Data Protection Impact Assessment (DPIA) under GDPR Article 35, given the likelihood of processing data relating to children. The client should also be advised that no content filtering system is 100% effective, and that the AUP acceptance creates a clear record of the user's agreement to the terms of use.
Frequently asked questions
Do I need new access points to set up Purple WiFi?
No. Purple is hardware-agnostic and runs as a cloud overlay on access points you already own. Supported vendors are Cisco Meraki, HPE Aruba, Ruckus, Juniper Mist, Ubiquiti UniFi, Cambium, Extreme and Fortinet. You apply Purple's RADIUS, captive portal and walled garden settings in your existing management plane, such as Meraki Dashboard or a SmartZone controller. No on-site server is needed, because Purple hosts the portal and RADIUS in the cloud.
How much does Purple WiFi cost?
Purple prices Guest WiFi through three plans, Connect, Capture and Engage, and quotes each estate against the plan and venue count. You do not buy or maintain on-site RADIUS or portal servers, because Purple runs both in the cloud. Your remaining costs are the access points you already own, internet bandwidth and engineer time to configure each site. Ask Purple for a quote against your venue list.
Can we move from our current captive portal provider without downtime?
Yes, if you build Purple on a test SSID alongside your live one. Create your venue, splash pages and sign-in rules in Purple first. Then broadcast the test SSID with Purple's settings and run the full checklist on iOS, Android and Windows. When every check passes, move the production SSID across in your change window. Guests see a new splash page, not an outage.
Is Purple GDPR compliant?
Yes. Purple is GDPR and CCPA compliant, and holds ISO 27001 and Cyber Essentials certification. You choose the fields on your splash page, write the consent wording and link your privacy notice. Purple's conscious-choice opt-ins keep marketing consent separate from connection, so a guest can get online without agreeing to marketing. That separation supports the GDPR requirement that consent is freely given and specific.
Can guests connect without seeing a captive portal?
Yes. Purple's SecurePass add-on uses IEEE 802.1X with WPA2- or WPA3-Enterprise. Devices authenticate once, then connect automatically on later visits with no splash page. Each session gets its own encryption keys, which an open captive portal SSID does not provide. SecurePass suits corporate visitors and long-stay guests. You can run it on its own SSID alongside a captive portal for walk-in visitors.
How is Purple different from the splash page built into my access points?
Purple gives you one platform across every site and every supported vendor. Built-in splash pages are configured per vendor and often per site. A mixed Cisco Meraki and Ubiquiti UniFi estate ends up with separate pages, consent records and reports. Purple centralises splash pages, sign-in rules, consent capture and analytics in one dashboard. It runs at 80,000+ live venues in more than 90 countries (Purple's own data).
Does adding guest WiFi affect our PCI DSS scope?
Only if guest traffic can reach your cardholder data environment. PCI DSS v4.0 does not mandate segmentation, but without it every connected system falls into scope. Put the guest SSID on its own VLAN with internet-only firewall rules. Keep payment terminals on a separate segment. Then prove it: from a signed-in guest device, try to reach an internal address. The attempt must fail.
Sources
- IETF RFC 2865: Remote Authentication Dial In User Service (RADIUS)
- IETF RFC 2866: RADIUS Accounting
- IETF RFC 1918: Address Allocation for Private Internets
- IEEE 802.1X: Port-Based Network Access Control
- Regulation (EU) 2016/679, General Data Protection Regulation
- PCI Security Standards Council document library (PCI DSS v4.0)
Continue reading in this series
Event venue WiFi providers: per-event captive portals, exhibitor access and attendee reporting
You will be able to choose between temporary contractors, vendor splash pages, organiser-supplied networks and a cloud overlay for your event venue. You will also be able to specify per-event captive portals, expiring exhibitor keys and sponsor-ready attendance reports. Finally, you can settle who controls attendee data under UK GDPR before the first portal goes live.
Ruckus SmartZone and RUCKUS One guest WiFi vs external captive portal platforms
Decide whether native Ruckus SmartZone or RUCKUS One guest access covers your estate, or whether an external captive portal such as Purple is worth its subscription. You can map your sites, vendors and data ownership to a clear recommendation. You will also understand the WISPr, Northbound Interface and RADIUS integration, and the cost of each option.
Aruba Central guest WiFi vs dedicated captive portal platforms: CRM, Passpoint and reporting compared
Use this comparison to choose between Aruba Central's native Cloud Guest, ClearPass Guest and a dedicated cloud platform such as Purple for your HPE Aruba estate. You can match each option to who owns guest WiFi, where guest data must land, how you record GDPR consent, whether returning guests need Passpoint and what each option costs over three years.
Got questions about your specific setup?
Our team works with venue operators, IT managers, and network engineers across 80,000 venues. Book a 20-minute call and we will show you how others like you solved it.