Skip to main content

Cisco Spaces alternatives for mixed-vendor estates: Aruba, Ruckus, Mist and Meraki compared

You will be able to decide whether to standardise on Cisco, run each vendor's own tool or add a hardware-neutral layer across a mixed estate. You will also be able to plan a staged, eight-step move off Cisco Spaces. That move covers the captive portal, Passpoint, CRM connectors and Staff WiFi, without replacing working access points.

By Tom HackettPublished
📖 13 min read2,848 words3 worked examples12 key definitions

Cisco Spaces alternatives for mixed-vendor estates: Aruba, Ruckus, Mist and Meraki compared

For a mixed-vendor estate, the practical Cisco Spaces alternative is a hardware-neutral layer that sits above every access point. Cisco Spaces is built for Cisco wireless, so acquired HPE Aruba, Ruckus, Juniper Mist or Ubiquiti UniFi venues fall outside its reach. Purple runs one captive portal, one cloud RADIUS service and one analytics model across all of them.

Which Cisco Spaces alternative suits a mixed-vendor estate?

Cisco Spaces is Cisco's cloud platform for captive portals, location analytics and OpenRoaming. It connects to Cisco Meraki networks and Cisco Catalyst wireless controllers. That works while every venue runs Cisco. It stops working when an acquisition, franchise deal or regional refresh brings in another vendor.

When you compare Cisco Spaces alternatives at that point, three realistic options remain:

  • Standardise on Cisco. Replace the acquired access points so Cisco Spaces can see them.
  • Run each vendor's own tool. Keep Cisco Spaces for Cisco venues and add HPE Aruba Networking Central, Ruckus Analytics or the Juniper Mist cloud for the rest.
  • Add a hardware-neutral layer. Run one captive portal, one cloud RADIUS service and one analytics model across every vendor.

For mixed estate guest WiFi, only the third option gives you one view of each visitor without a hardware programme. Purple is that layer. It is hardware-agnostic and runs as a cloud overlay on Cisco Meraki, HPE Aruba, Ruckus, Juniper Mist, Ubiquiti UniFi, Cambium, Extreme and Fortinet. Purple runs in 80,000+ live venues across more than 90 countries and handles 500 million users and logins a year (Purple data).

What happens to Cisco Spaces coverage when an acquisition adds HPE Aruba, Ruckus or UniFi venues?

Coverage stops at the edge of the Cisco estate. The acquired venues keep their networks, but they sit outside your captive portal, your analytics and your CRM feed. A captive portal is the web page a visitor sees, and accepts, before getting online.

Four gaps open on day one

  1. Several login experiences. Acquired venues keep whatever portal they had. Your brand, terms and consent wording now differ by venue.
  2. Partial analytics. Visit, dwell and repeat-visit reports cover Cisco venues only. Any estate-wide figure becomes an estimate.
  3. Split identity. A guest who logs in at a Cisco venue and an HPE Aruba venue appears as two people. Nothing joins the records.
  4. Duplicated integrations. Every CRM or marketing connector must be rebuilt for each tool, then maintained in parallel.

There is a compliance cost too. Under GDPR Article 7(1), you must be able to demonstrate that each person consented. Consent held in two or three systems, under different wording, makes that harder to prove.

Why replacing access points rarely survives the business case

Standardising means capital spend, site surveys and change windows at every acquired venue. It also retires hardware that still has useful life left. If the acquired estate already runs WiFi 6 or WiFi 6E, you would replace working kit only to change software. Why your next WiFi upgrade doesn't need new hardware sets out the alternative. When a refresh is genuinely due, WiFi 7 (802.11be) Explained: What Changes for Enterprise WiFi covers what changes.

Where do Cisco Spaces, vendor tools and a hardware-neutral layer genuinely differ?

The differences show up in coverage, identity and the number of systems your team maintains. The table compares the three options for a four-vendor estate: Cisco Meraki, HPE Aruba, Ruckus and Ubiquiti UniFi.

Axis Cisco Spaces (standardise on Cisco) Each vendor's own tool Purple (hardware-neutral)
Access points covered Cisco Meraki and Cisco Catalyst wireless One vendor per tool Cisco Meraki, HPE Aruba, Ruckus, Juniper Mist, Ubiquiti UniFi, Cambium, Extreme, Fortinet
Hardware change for acquired venues Replace every non-Cisco access point None None
Captive portals to maintain One Four One
Visitor identity across venues Joined only after full replacement Not joined across tools One profile per visitor
CRM connectors to build One Four One
Staff 802.1X authentication Cisco ISE, a separate product Each vendor's own access control product Purple cloud RADIUS with Microsoft Entra ID, Okta or Google Workspace
OpenRoaming and Passpoint On Cisco hardware Configured separately per vendor Run from one platform on Passpoint-capable access points
Processor agreements under GDPR Article 28 One Four One

How does a hardware-neutral layer normalise visitor identity across mixed AP vendors?

Every enterprise vendor on that list speaks RADIUS (Remote Authentication Dial-In User Service). RADIUS is the protocol access points use to ask a server who may connect, and to report each session. RFC 2865 defines authentication and RFC 2866 defines accounting. Every vendor also supports handing new connections to an external captive portal.

The standards are shared. The details are not. Vendors format attributes such as Called-Station-Id differently. Each adds its own vendor-specific attributes, which RFC 2865 explicitly permits. Each passes different parameters when it redirects a device to the captive portal.

A hardware-neutral layer absorbs those differences in four steps:

  1. Ingest. Purple receives redirect, authentication and accounting data from each vendor's access points or controller.
  2. Map. It translates every vendor's format into one schema: venue, zone, access point, session and visitor.
  3. Resolve. It anchors each session to a visitor identity, not a device address.
  4. Report. Visits, dwell time and repeat visits roll up identically, whether the venue runs Meraki or Ruckus.

The anchor matters. Since iOS 14 and Android 10, phones use randomised private MAC addresses by default. Analytics keyed on MAC addresses alone overcount people and undercount return visits. Purple anchors identity on something the visitor chose to give: a login with a conscious-choice opt-in, a Passpoint credential or a personal key. That first-party data stays consistent across every vendor. It feeds WiFi Analytics and your CRM from one record, which is what makes multi-vendor WiFi location analytics comparable venue to venue.

Where does each option fit?

Match your estate to the row that describes it. Each row shows what breaks under Cisco Spaces and what fixes it.

Your estate What breaks under Cisco Spaces What to do
All Cisco Meraki, acquisitions likely Nothing yet; the next acquisition falls outside coverage Deploy Purple on Meraki now, so acquired venues join the same captive portal
Cisco core plus acquired HPE Aruba or Ruckus hotels Acquired hotels sit outside portal, analytics and CRM Run Purple across all vendors and replace no access points
Meraki stores plus franchise stores on Ubiquiti UniFi UniFi stores missing from shopper reporting Run Purple on both, with one consent wording estate-wide
Stadium with Juniper Mist in the bowl and Meraki in suites Fans log in twice and count twice Use Purple as the single identity layer
Rail operator with mixed station and onboard vendors Roaming limited to Cisco sites Run OpenRoaming from Purple across the estate
Merged hospital trusts on different vendors Patient and visitor WiFi split by legacy trust Run one Purple captive portal and policy across both estates

Sector detail sits on the Hotels, Retail, Trains and Healthcare pages. The three worked examples below show the arithmetic.

Worked example: a 60-hotel group after an acquisition

Situation. A hotel group runs 40 hotels on Cisco Meraki with Cisco Spaces. It acquires 20 more: 15 on HPE Aruba and five on Ruckus. Cisco Spaces now covers 40 of 60 hotels, or 67%. The group runs three captive portals and three sets of consent records.

What the group does. It deploys Purple as a cloud overlay on all three vendors. One captive portal design serves every hotel, with a variant per brand. It builds one CRM connector and pilots Purple alongside Cisco Spaces before retiring the old portals.

Outcome. Portal and analytics coverage moves from 67% to 100% of hotels. Captive portals fall from three to one, and CRM connectors from three to one. None of the access points in the 20 acquired hotels is replaced. A guest who stays at two brands appears as one profile.

Worked example: a 120-store retailer with UniFi franchise stores

Situation. A retailer runs 90 company-owned stores on Cisco Meraki with Cisco Spaces. Its 30 franchise stores run Ubiquiti UniFi with their own hotspot page and wording. Shopper reporting covers 90 of 120 stores, or 75%.

What the retailer does. It runs Purple on both vendors with one consent wording. Guest traffic sits on its own VLAN, a logically separate network segment, away from payment systems. PCI DSS treats segmentation as the way to keep guest networks out of cardholder data scope.

Outcome. Shopper visit and repeat-visit reporting covers 120 of 120 stores. Consent wordings fall from two to one. Franchise stores feed the same CRM as company stores.

Worked example: a stadium with two vendors under one roof

Situation. A stadium runs Juniper Mist across the bowl and concourses, and Cisco Meraki in hospitality suites and offices. A fan who walks from concourse to suite meets a second login. Two platforms report two overlapping attendance figures.

What the stadium does. Purple runs one captive portal on both vendors. Sessions from both resolve to one fan profile. Stadium staff move from a shared password to individual 802.1X logins through Purple cloud RADIUS.

Outcome. Logins per fan per match fall from two to one. Platforms reporting attendance fall from two to one, producing a single de-duplicated fan count.

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.

What does each option cost to run?

Licence price is only the visible line. Running cost grows with every platform, connector and consent store you keep alive. Cisco licenses Spaces per access point, so standardising adds replacement hardware plus licences for the new Cisco access points. Vendor tools carry their own per-device subscriptions. Each one adds another console, contract and integration.

Cost driver (four-vendor estate) Standardise on Cisco Each vendor's own tool Purple
Access points replaced Every HPE Aruba, Ruckus and UniFi access point None None
Analytics and portal platforms licensed One Four One
Analytics consoles your team learns One Four One
CRM connectors built and maintained One Four One
Consent stores to reconcile under GDPR One, after migration Four One
Processor agreements under GDPR Article 28 One Four One

The hidden costs sit in engineering time. Each connector breaks when a vendor changes its API. Each consent store must be reconciled at audit. Each new console needs training. Purple pricing follows the plan you choose, Connect, Capture or Engage, rather than the badge on your access points.

How do you migrate captive portal, Passpoint and CRM connectors off a single-vendor stack?

Move in stages, with Cisco Spaces still serving production until each stage reconciles.

Step 1: inventory what Cisco Spaces does today

List each venue, its vendor, its SSIDs and its controller or cloud dashboard. Then list each Cisco Spaces feature in use: captive portal, location reports, OpenRoaming and connectors. That list becomes your acceptance criteria.

Decide which consent records move, and on what lawful basis. Carry the wording and timestamp with each record, because Article 7(1) requires you to demonstrate consent. Where acquired venues used weaker wording, collect fresh opt-ins rather than import them. Put an Article 28 processor agreement in place with Purple. Purple is ISO 27001 and Cyber Essentials certified, and GDPR and CCPA compliant.

Step 3: configure each vendor once

Point each vendor's external captive portal settings and RADIUS servers at Purple. Settings differ by vendor and firmware. Follow the Purple support article for each vendor rather than copying values between them.

Step 4: pilot one venue per vendor in parallel

Run Purple on a test SSID or single venue per vendor while Cisco Spaces keeps serving production. Compare login completion, opt-in rates and session data against existing reports. Move on only when the numbers reconcile.

Step 5: move Passpoint and OpenRoaming

Passpoint is a certification programme built on the Hotspot 2.0 specification. It lets a device join a network automatically using a stored profile, over WPA2-Enterprise or WPA3-Enterprise encryption. OpenRoaming is a Wireless Broadband Alliance federation that uses Passpoint, so one profile works on any participating network.

Plan for two groups of devices. Federated OpenRoaming profiles from other identity providers keep working once your venues connect through Purple. Profiles your own app or captive portal issued under Cisco Spaces reference the old provider, so reissue them during an overlap window. Is public WiFi safe? What risks and protections to know explains why encrypted, profile-based access beats open networks.

Step 6: rebuild CRM connectors once

Map Purple's visitor fields to your CRM fields, test with pilot data, then switch the feed. Because every vendor feeds one schema, you build this once for the estate. Retire the old Cisco Spaces connectors after one full reporting cycle overlaps.

Step 7: bring staff WiFi into scope

While you re-point RADIUS, move staff off shared passwords. IEEE 802.1X is the standard for port-based access control, where each person authenticates with their own credentials. Purple cloud RADIUS authenticates staff against Microsoft Entra ID, Okta or Google Workspace. Joiners, movers and leavers then follow your directory, as What is user provisioning? a plain-english guide for 2026 explains. For devices that cannot run 802.1X, iPSK (identity pre-shared key) gives each one a personal key. WPA-PSK Explained: What It Is, How It Works, and Its Security Risks covers why a shared key is the risk.

Step 8: cut over and retire

Switch production SSIDs venue by venue and keep rollback settings for each. Decommission Cisco Spaces when the last Meraki venue has moved.

How should you decide for your estate?

Weighing Cisco Spaces vs a hardware-neutral captive portal and analytics layer comes down to five questions:

  1. How many access point vendors will you run in 24 months? More than one means single-vendor analytics will leave gaps.
  2. Where must identity join? Across brands, sites or zones within one venue.
  3. How many integrations do you own? Each vendor tool multiplies them.
  4. Can you prove consent at every venue today? Split consent stores weaken that proof.
  5. Are staff or residents still on shared passwords? A RADIUS migration is the moment to fix it.

If two or more answers point beyond one vendor, a hardware-neutral layer is the lower-risk path. Purple was founded in 2012 and runs at 99.999% uptime (Purple data). It is ISO 27001, Cyber Essentials and B Corp certified. Purple runs Guest WiFi for brands including McDonald's, Harrods and Premier Inn.

Frequently asked questions

Does Cisco Spaces work with HPE Aruba, Ruckus or Ubiquiti UniFi access points?

No. Cisco Spaces is built for Cisco wireless: Cisco Meraki networks and Cisco Catalyst controllers. Venues on HPE Aruba, Ruckus, Juniper Mist or Ubiquiti UniFi fall outside its captive portal, location analytics and connectors. To bring them in, you either replace their access points with Cisco hardware or add a hardware-neutral layer. Purple runs on all of those vendors, plus Cambium, Extreme and Fortinet, without new hardware.

Can Purple run on the Cisco Meraki access points we already own?

Yes. Purple runs as a cloud overlay on Cisco Meraki, using Meraki's external captive portal and RADIUS support. You keep your access points and your Meraki dashboard. Purple then applies the same captive portal, cloud RADIUS and analytics to any HPE Aruba, Ruckus, Juniper Mist or Ubiquiti UniFi venues you add later. Acquired venues join the same visitor profiles and reports instead of starting a second platform.

Do we need to replace any hardware to move off Cisco Spaces?

No. Purple is hardware-agnostic, so it works with the access points each venue already has. You re-point captive portal and RADIUS settings on each vendor's controller or cloud dashboard. Hardware replacement only becomes relevant when equipment reaches end of life. Even then, your choice of access point vendor no longer decides which analytics and captive portal platform you can use.

You carry consent across only where you can prove it. GDPR Article 7(1) requires you to demonstrate consent, so each migrated record needs its wording and timestamp. Where acquired venues used weaker or different wording, collect fresh conscious-choice opt-ins through the new captive portal. Purple acts as your processor under an Article 28 agreement and holds ISO 27001 and Cyber Essentials certification.

Will OpenRoaming and Passpoint visitors lose access during the switch?

No, provided you stage it. Federated OpenRoaming profiles issued by other identity providers keep working once your venues connect through Purple. Profiles your own app or captive portal issued under Cisco Spaces reference the old provider, so reissue them during an overlap window. Run both providers in parallel until reissued profiles cover your active visitors, then retire the old configuration.

Can we run Cisco Spaces and Purple side by side during migration?

Yes. You can point individual SSIDs or venues at different captive portals and RADIUS servers. That lets you pilot Purple on one venue per vendor while Cisco Spaces keeps serving production on the Meraki estate. Compare login completion, opt-in rates and session data between the two. Then cut over venue by venue, keeping rollback settings for each until the numbers reconcile.

How does Purple pricing work for a mixed-vendor estate?

Purple prices by plan, not by access point vendor. You choose Connect, Capture or Engage for your venues, and add SecurePass, Verify or Shield where you need extra security. Because one platform runs on every supported vendor, an acquisition adds venues to your existing estate. It does not add a new platform, captive portal or CRM connector to license and maintain.

Key Definitions

Captive portal

The web page a visitor sees and accepts before getting online. Access points redirect new connections to an external portal, passing vendor-specific parameters in the redirect.

Under Cisco Spaces, acquired non-Cisco venues keep their own portals, so brand, terms and consent wording differ by venue. A hardware-neutral layer runs one portal across every vendor.

RADIUS

Remote Authentication Dial-In User Service, the protocol access points use to ask a server who may connect. IETF RFC 2865 specifies authentication and authorisation.

Every enterprise vendor in a mixed estate speaks RADIUS, which is why one cloud RADIUS service can authenticate visitors and staff on Cisco Meraki, HPE Aruba, Ruckus and the rest.

RADIUS accounting

The RADIUS extension, specified in IETF RFC 2866, through which access points report the start, progress and end of each session to a server.

Accounting data is one of the inputs a hardware-neutral layer ingests and maps into one schema, so dwell and repeat-visit reports roll up identically across vendors.

Vendor-specific attributes

RADIUS attributes that each vendor defines for its own use, explicitly permitted by RFC 2865 alongside the standard attributes.

Vendors also format standard attributes such as Called-Station-Id differently. These differences are what a hardware-neutral layer must normalise before analytics become comparable venue to venue.

MAC address randomisation

The default behaviour since iOS 14 and Android 10, where phones present a randomised private MAC address rather than the hardware address.

Analytics keyed on MAC addresses alone overcount people and undercount return visits. Purple anchors identity on a login, Passpoint credential or personal key instead.

IEEE 802.1X

The IEEE standard for port-based network access control, where each person authenticates with their own credentials through a RADIUS server before the network grants access.

Re-pointing RADIUS during a migration is the moment to move staff off shared passwords, using Purple cloud RADIUS against Microsoft Entra ID, Okta or Google Workspace.

iPSK

Identity pre-shared key: each device receives its own personal key rather than one shared passphrase for the whole network.

iPSK covers devices that cannot run 802.1X, removing the risk a single shared key creates when staff or residents leave.

Passpoint

A certification programme built on the Hotspot 2.0 specification. It lets a device join a network automatically using a stored profile, over WPA2-Enterprise or WPA3-Enterprise encryption.

Profiles your own app or captive portal issued under Cisco Spaces reference the old provider, so plan to reissue them during an overlap window.

OpenRoaming

A Wireless Broadband Alliance federation that uses Passpoint, so one profile works on any participating network.

Federated OpenRoaming profiles from other identity providers keep working once your venues connect through Purple, which lets a rail operator extend seamless roaming beyond Cisco sites.

GDPR Article 7(1)

The provision of the EU General Data Protection Regulation requiring a controller to be able to demonstrate that each person consented to the processing of their personal data.

Consent held in several systems under different wording is harder to prove. Each migrated record needs its wording and timestamp, or a fresh opt-in.

GDPR Article 28

The GDPR provision requiring a written agreement between a controller and any processor that handles personal data on its behalf.

Running each vendor's own tool means four processor agreements in a four-vendor estate. A hardware-neutral layer means one, with Purple as your processor.

VLAN

A virtual LAN, defined by IEEE 802.1Q, that creates a logically separate network segment on shared infrastructure.

Placing guest traffic on its own VLAN, away from payment systems, follows PCI DSS guidance on keeping guest networks out of cardholder data scope.

Worked Examples

A hotel group runs 40 hotels on Cisco Meraki with Cisco Spaces, then acquires 20 more: 15 on HPE Aruba and five on Ruckus. Cisco Spaces now covers 67% of hotels, with three captive portals and three sets of consent records. How does the group close the gap?

The group deploys Purple as a cloud overlay on all three vendors. One captive portal design serves every hotel, with a variant per brand. It builds one CRM connector and pilots Purple alongside Cisco Spaces before retiring the old portals. Portal and analytics coverage moves from 67% to 100% of hotels. Captive portals fall from three to one, and CRM connectors from three to one. None of the access points in the 20 acquired hotels is replaced. A guest who stays at two brands now appears as one profile, because identity resolves to the visitor rather than the hardware.

A retailer runs 90 company-owned stores on Cisco Meraki with Cisco Spaces. Its 30 franchise stores run Ubiquiti UniFi with their own hotspot page and wording, so shopper reporting covers only 75% of stores. What does the retailer do?

The retailer runs Purple on both vendors with one consent wording across the estate. Guest traffic sits on its own VLAN, away from payment systems, because PCI DSS treats segmentation as the way to keep guest networks out of cardholder data scope. Shopper visit and repeat-visit reporting now covers 120 of 120 stores. Consent wordings fall from two to one, which makes consent easier to demonstrate under GDPR Article 7(1). Franchise stores feed the same CRM as company stores, so the retailer maintains one connector rather than two.

A stadium runs Juniper Mist across the bowl and concourses and Cisco Meraki in hospitality suites and offices. Fans meet a second login when they walk into a suite, and two platforms report overlapping attendance. How does the stadium fix it?

Purple runs one captive portal on both vendors, so sessions from Juniper Mist and Cisco Meraki resolve to one fan profile. Stadium staff move from a shared password to individual 802.1X logins through Purple cloud RADIUS, which removes the shared-credential risk at the same time. Logins per fan per match fall from two to one. Platforms reporting attendance fall from two to one, producing a single de-duplicated fan count. The stadium keeps both sets of access points, because the identity layer sits above the hardware rather than inside one vendor's stack.

Frequently asked questions

Does Cisco Spaces work with HPE Aruba, Ruckus or Ubiquiti UniFi access points?

No. Cisco Spaces is built for Cisco wireless: Cisco Meraki networks and Cisco Catalyst controllers. Venues on HPE Aruba, Ruckus, Juniper Mist or Ubiquiti UniFi fall outside its captive portal, location analytics and connectors. To bring them in, you either replace their access points with Cisco hardware or add a hardware-neutral layer. Purple runs on all of those vendors, plus Cambium, Extreme and Fortinet, without new hardware.

Can Purple run on the Cisco Meraki access points we already own?

Yes. Purple runs as a cloud overlay on Cisco Meraki, using Meraki's external captive portal and RADIUS support. You keep your access points and your Meraki dashboard. Purple then applies the same captive portal, cloud RADIUS and analytics to any HPE Aruba, Ruckus, Juniper Mist or Ubiquiti UniFi venues you add later. Acquired venues join the same visitor profiles and reports instead of starting a second platform.

Do we need to replace any hardware to move off Cisco Spaces?

No. Purple is hardware-agnostic, so it works with the access points each venue already has. You re-point captive portal and RADIUS settings on each vendor's controller or cloud dashboard. Hardware replacement only becomes relevant when equipment reaches end of life. Even then, your choice of access point vendor no longer decides which analytics and captive portal platform you can use.

How is guest consent handled when we migrate from Cisco Spaces?

You carry consent across only where you can prove it. GDPR Article 7(1) requires you to demonstrate consent, so each migrated record needs its wording and timestamp. Where acquired venues used weaker or different wording, collect fresh conscious-choice opt-ins through the new captive portal. Purple acts as your processor under an Article 28 agreement and holds ISO 27001 and Cyber Essentials certification.

Will OpenRoaming and Passpoint visitors lose access during the switch?

No, provided you stage it. Federated OpenRoaming profiles issued by other identity providers keep working once your venues connect through Purple. Profiles your own app or captive portal issued under Cisco Spaces reference the old provider, so reissue them during an overlap window. Run both providers in parallel until reissued profiles cover your active visitors, then retire the old configuration.

Can we run Cisco Spaces and Purple side by side during migration?

Yes. You can point individual SSIDs or venues at different captive portals and RADIUS servers. That lets you pilot Purple on one venue per vendor while Cisco Spaces keeps serving production on the Meraki estate. Compare login completion, opt-in rates and session data between the two. Then cut over venue by venue, keeping rollback settings for each until the numbers reconcile.

How does Purple pricing work for a mixed-vendor estate?

Purple prices by plan, not by access point vendor. You choose Connect, Capture or Engage for your venues, and add SecurePass, Verify or Shield where you need extra security. Because one platform runs on every supported vendor, an acquisition adds venues to your existing estate. It does not add a new platform, captive portal or CRM connector to license and maintain.

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.