Skip to main content

Purple vs. Tanaza: Plataformas de Captive Portal Comparadas

Este guia de referência técnica oferece uma comparação neutra entre Purple e Tanaza para implantações de captive portal em SMBs e no mercado intermediário. Ele avalia ambas as plataformas em termos de arquitetura técnica, compatibilidade de hardware, postura de conformidade e precificação para ajudar líderes de TI a alinhar sua estratégia de acesso à rede com resultados de negócios mensuráveis.

📖 4 min de leitura📝 1,000 palavras🔧 2 exemplos3 perguntas📚 8 termos-chave

🎧 Ouça este Guia

Ver Transcrição
Purple vs Tanaza: Captive Portal Platforms Compared — A Senior Consultant Briefing [INTRODUCTION — approximately 1 minute] Welcome. If you're listening to this, you're probably evaluating captive portal platforms for a venue deployment — a hotel, a retail chain, a stadium, or perhaps a multi-site managed services rollout — and you've narrowed it down to Purple and Tanaza. Good. Those are both credible platforms, and the fact that you're comparing them rather than just buying the first thing a reseller recommended tells me you're approaching this the right way. My name isn't important. What matters is that over the next ten minutes, I'm going to give you the same briefing I'd give a client sitting across the table from me. No marketing language, no vendor spin. Just the architecture, the pricing reality, the compliance implications, and the deployment scenarios where each platform genuinely wins. Let's get into it. [TECHNICAL DEEP-DIVE — approximately 5 minutes] First, let's establish what we're actually comparing, because these two platforms are solving slightly different problems — and that distinction matters enormously for your procurement decision. Tanaza is, at its core, a cloud-based WiFi network management platform. It's built around TanazaOS, a Linux-based operating system that you flash onto compatible access points from vendors like TP-Link, Ubiquiti, MikroTik, and Edgecore. The captive portal functionality — what Tanaza calls the Classic Hotspot or the built-in splash page — is a feature of that network management layer. It gives you click-through authentication, voucher-based login, and basic splash page customisation. It's clean, it's functional, and for an MSP managing dozens of small business networks, it does exactly what you need. Purple, by contrast, is a guest WiFi intelligence platform. The captive portal is the front door, yes — but it's the front door to an analytics engine, a first-party data platform, and a marketing automation layer. Purple doesn't require you to flash firmware onto your access points. It works via an external captive portal redirect mechanism, which means it integrates with your existing infrastructure — whether that's Cisco Meraki, Aruba, Ruckus, Juniper Mist, Ubiquiti UniFi, or any of the fifty-plus hardware vendors on its compatibility list — without touching the underlying network operating system. That architectural difference is the single most important thing to understand. Tanaza owns the AP layer. Purple sits above it. Now, let's talk about captive portal capabilities specifically, because that's where the gap becomes very clear. Tanaza's built-in splash page supports click-through and code-based login. Voucher login is available as a paid add-on from the Marketplace. Social login — Google, Facebook, Apple — is not natively available. You need a third-party integration, such as DataWiFi, to enable it. That's an additional cost and an additional dependency in your stack. Purple supports all standard authentication methods natively: social login via Google, Facebook, and Apple; email capture with address verification; SMS one-time password; and click-through. The splash page builder is drag-and-drop, fully white-labelled, and supports 25 languages out of the box. GDPR consent capture is built into the onboarding flow with a full per-user audit trail — which is critical if you're operating in the EU or the UK and you need to demonstrate lawful basis for processing under Article 6 of the GDPR. Speaking of compliance — this is an area where the platforms diverge significantly. Tanaza provides basic GDPR documentation and allows you to configure terms and conditions on the splash page. Purple goes considerably further: consent records, data retention controls, right-to-erasure workflows, and compliance with GDPR, CCPA, and LGPD are built into the platform architecture. For a hotel chain operating across EU jurisdictions, or a retail group with stores in California, that's not a nice-to-have — it's a procurement requirement. On analytics: Tanaza gives you network-level statistics — connected clients, bandwidth usage, access point load, connection status over the last seven days. That's useful for network operations. It tells you nothing about visitor behaviour. Purple's analytics layer tracks footfall patterns, dwell time by zone, repeat visit frequency, and demographic data captured during authentication. For a retail operator, that's the difference between knowing your WiFi is working and knowing that customers who connect to WiFi spend an average of 23 minutes longer in-store. For a hotel, it's the difference between a cost centre and a revenue intelligence tool. CRM integration is another clean differentiator. Tanaza has no native CRM connectors. Purple integrates natively with Salesforce, HubSpot, Mailchimp, ActiveCampaign, Microsoft Dynamics, and Eagle Eye, among others. If your marketing team is running automated campaigns based on WiFi engagement data, Purple is the only platform in this comparison that supports that workflow without custom development. Now, hardware support. Both platforms are hardware-agnostic in principle, but the mechanism differs. Tanaza requires TanazaOS to be installed on the access point — either pre-installed on Tanaza Powered Devices from OEM partners, or manually flashed by the installer. The supported vendor list includes TP-Link, Ubiquiti, MikroTik, Edgecore, LigoWave, and Comfast, among others. It's a solid list for SMB deployments, but it skews toward lower-cost hardware. Purple's compatibility list spans over fifty enterprise hardware vendors, including Cisco, Cisco Meraki, Aruba, Ruckus, Juniper Mist, Extreme Networks, Fortinet, Huawei, and Cambium Networks. No firmware modification is required. Purple integrates via the vendor's external captive portal or RADIUS redirect mechanism. If you're deploying into an existing enterprise network infrastructure — which is the reality for most mid-market and enterprise clients — Purple's approach is significantly lower risk and lower operational overhead. [IMPLEMENTATION RECOMMENDATIONS AND PITFALLS — approximately 2 minutes] Let me give you the practical deployment guidance now. If you're an MSP deploying WiFi for small businesses — cafés, independent hotels, small retail outlets — and your clients don't need marketing analytics or CRM integration, Tanaza Pro at $1.99 per access point per month is genuinely excellent value. The zero-touch provisioning workflow is clean, the multi-site dashboard is well-designed, and the platform is stable. The captive portal does what it needs to do for basic guest access. Start with the free Basic plan on three access points, validate the deployment, then scale to Pro. The pitfall to avoid with Tanaza is scope creep on the captive portal requirements. If a client comes back six months later asking for social login, footfall analytics, or CRM integration, you're looking at third-party add-ons, custom development, or a platform migration. Build that conversation into the initial scoping. For Purple, the free Connect tier is a legitimate starting point for any venue that needs a branded captive portal with compliance built in. It's not a trial — it's a permanent free tier. The upgrade path to Capture and Engage is driven by data and marketing requirements, not by access point count. That's an important distinction. Purple's pricing scales with your ambition for the platform, not just your hardware footprint. The implementation pitfall with Purple is underestimating the onboarding investment for the analytics and marketing features. The captive portal deploys quickly — typically within a day for a standard venue. But getting the CRM integration configured, the data capture fields mapped to your marketing taxonomy, and the automated campaign workflows set up requires project management. Budget for it. One more thing on compliance: if you're deploying in the EU, do not assume that a basic terms-and-conditions checkbox on a splash page satisfies your GDPR obligations. You need documented consent, a lawful basis for processing, and a mechanism for data subjects to exercise their rights. Purple's platform handles this by design. With Tanaza, you need to build that compliance layer yourself or through a third-party integration. [RAPID-FIRE Q&A — approximately 1 minute] Let me run through the questions I get most often on this comparison. "Can I run Purple on top of a Tanaza-managed network?" — Yes, in principle. Purple works via external captive portal redirect, so if Tanaza is managing the AP layer and you configure the SSID to redirect to an external portal, you can point it at Purple. It's an unusual architecture, but it's technically viable. "Does Tanaza support WPA3?" — TanazaOS supports WPA2 and WPA2 Enterprise. WPA3 support depends on the underlying hardware and firmware version. Check the specific device compatibility before specifying WPA3 in your design. "Is Purple's free Connect tier genuinely free, or is there a catch?" — It's genuinely free. No time limit, no access point count limit on the portal side. The limitation is that you don't get first-party data capture or CRM integration on the free tier. For a venue that just needs a branded, compliant guest WiFi portal, Connect is a permanent solution. "Which platform is better for a stadium deployment?" — Purple, without question. The analytics, the zone-level footfall data, the high-density AP support, and the enterprise hardware compatibility make it the right choice for large venues. [SUMMARY AND NEXT STEPS — approximately 1 minute] Let me leave you with the decision framework. Choose Tanaza if: you're an MSP managing SMB networks, your clients need cloud-based AP management with a basic captive portal, and marketing analytics are not a requirement. The pricing is transparent, the platform is mature, and the zero-touch provisioning workflow is genuinely efficient. Choose Purple if: your venue needs to capture first-party visitor data, integrate with a CRM or marketing automation platform, demonstrate GDPR compliance with an audit trail, or generate operational intelligence from WiFi analytics. The free Connect tier means there's no financial barrier to getting started, and the upgrade path is driven by business outcomes rather than hardware count. The bottom line: Tanaza is a network management platform with a captive portal feature. Purple is a guest intelligence platform with a captive portal as the entry point. If you need the former, Tanaza is excellent. If you need the latter, Purple is the clear choice. For next steps: if you're evaluating Purple, start with the free Connect tier on your primary venue. Run it for thirty days, review the network analytics, and assess whether the Capture or Engage tiers would deliver measurable ROI for your marketing team. If you're evaluating Tanaza, request a demo of the Pro plan and test the zero-touch provisioning workflow with your target hardware. Thanks for listening. Make the right call for your deployment.

header_image.png

Resumo Executivo

Para gerentes de TI e arquitetos de rede que avaliam plataformas de captive portal, a escolha entre Purple e Tanaza representa uma decisão arquitetônica fundamental. Tanaza opera principalmente como uma plataforma de gerenciamento de rede baseada em nuvem com recursos de captive portal integrados, projetada para MSPs que gerenciam implantações SMB de múltiplos fornecedores via firmware personalizado. Purple, por outro lado, funciona como uma camada de inteligência de convidado de nível empresarial que se posiciona acima da infraestrutura de rede existente via redirecionamentos externos de captive portal, transformando o Guest WiFi padrão em um motor de captura e análise de dados.

Este guia detalha as diferenças técnicas, modelos de implantação e custo total de propriedade para ambas as plataformas. Seja você atualizando um único hotel de 200 quartos ou implantando em uma rede de Varejo de 50 unidades, entender onde cada plataforma se destaca evitará refatorações arquitetônicas dispendiosas no futuro.

Análise Técnica Detalhada

Abordagens Arquitetônicas

O diferencial mais significativo entre as duas plataformas é como elas interagem com o hardware de rede subjacente.

Tanaza depende do TanazaOS, um sistema operacional baseado em Linux que deve ser gravado em pontos de acesso compatíveis (ou adquirido pré-instalado em Dispositivos Tanaza Powered). Isso confere à Tanaza controle profundo sobre o ponto de acesso, permitindo provisionamento zero-touch, monitoramento de carga em tempo real e otimização de canal diretamente de seu painel na nuvem. No entanto, essa abordagem exige a substituição do firmware OEM, o que pode anular garantias e limita as escolhas de hardware a modelos suportados de fornecedores como TP-Link, Ubiquiti e MikroTik.

Purple adota uma arquitetura de overlay. Ele se integra com mais de 50 fornecedores de hardware empresarial — incluindo Cisco Meraki, Aruba, Ruckus e Juniper Mist — via redirecionamentos padrão de captive portal externo e autenticação RADIUS. Nenhuma modificação de firmware é necessária. Isso torna Purple significativamente de menor risco para implantações de médio porte e empresariais onde a infraestrutura de alto desempenho existente já está em vigor. Para mais informações sobre como isso se integra com o design de rede mais amplo, consulte nosso Arquitetura da Internet das Coisas: Um Guia Completo .

Recursos do Captive Portal

A página de splash integrada da Tanaza oferece acesso de convidado funcional e direto. Ela suporta acordos de clique e logins baseados em código nativamente. No entanto, ela carece de recursos nativos de login social (Google, Facebook, Apple) e requer integrações de terceiros como DataWiFi para conseguir isso.

O captive portal da Purple é construído para aquisição de dados e conformidade de marketing. Ele suporta nativamente uma ampla gama de métodos de autenticação, incluindo logins sociais, SMS OTP e captura de e-mail com verificação em tempo real. O construtor de arrastar e soltar suporta 25 idiomas e permite uma profunda personalização da marca.

comparison_chart.png

Conformidade e Segurança

Ao implantar redes de convidados em Saúde ou setores públicos, a conformidade é inegociável. Tanaza permite que os administradores configurem termos e condições, mas o ônus de demonstrar a conformidade com o GDPR recai em grande parte sobre o operador.

Purple incorpora a conformidade no fluxo de onboarding. Ele mantém um registro de auditoria completo do consentimento do usuário, gerencia automaticamente as políticas de retenção de dados e fornece fluxos de trabalho integrados para solicitações de direito ao esquecimento. Esta arquitetura é projetada para atender aos requisitos rigorosos do GDPR, CCPA e LGPD de forma nativa. Para estratégias de conformidade regionais específicas, consulte nosso LGPD do Brasil e Guest WiFi: Um Guia de Conformidade .

Guia de Implementação

Implantando Tanaza

  1. Seleção de Hardware: Verifique se seus pontos de acesso estão na lista de suporte da Tanaza ou adquira Dispositivos Tanaza Powered.
  2. Gravação de Firmware: Se estiver usando hardware existente, siga as instruções específicas de gravação para instalar o TanazaOS. Esta etapa requer proficiência técnica e acesso físico aos APs ou a um ambiente de staging.
  3. Provisionamento em Nuvem: Adicione os endereços MAC ao painel de nuvem da Tanaza.
  4. Configuração de Rede: Configure SSIDs, marcação de VLAN e limites de largura de banda centralmente.
  5. Configuração do Portal: Habilite a página de splash integrada e configure os termos básicos de clique para aceitar.

Implantando Purple

  1. Integração de Infraestrutura: Configure seu WLC ou controlador de nuvem existente (por exemplo, Meraki Dashboard, Aruba Central) para apontar para as URLs de captive portal externo e servidores RADIUS da Purple.
  2. Design do Portal: Use o construtor de portal da Purple para projetar a página de splash, configurar APIs de login social e definir os requisitos de captura de dados.
  3. Configuração de Conformidade: Defina os limites de retenção de dados e configure os links da política de privacidade dentro do painel da Purple.
  4. Mapeamento de CRM: Conecte Purple ao seu CRM (por exemplo, Salesforce, HubSpot) e mapeie os campos de dados demográficos capturados para seus registros de contato.

Ouça o briefing do nosso consultor sênior para uma análise mais aprofundada dessas estratégias de implantação:

Melhores Práticas

  • Defina o Resultado de Negócio Primeiro: Se o objetivo é puramente o gerenciamento operacional de rede para uma pequena implantação, priorize o provisionamento zero-touch da Tanaza. Se o objetivo é inteligência de marketing e Análise de WiFi , Purple é a arquitetura necessária.
  • Avalie o Custo Total de Propriedade (TCO): O nível Pro da Tanaza cobra uma taxa mensal fixa por AP. Purple ofoferece um nível gratuito robusto (Connect) para acesso básico de marca e conformidade, com níveis pagos (Capture e Engage) que escalam com base nas necessidades de análises avançadas e integração de CRM. Considere o custo de complementos de terceiros se tentar construir recursos de marketing sobre o Tanaza.
  • Decisões de Hardware à Prova de Futuro: Confiar em firmware personalizado limita a flexibilidade futura do hardware. Arquiteturas de sobreposição preservam sua capacidade de migrar fornecedores de hardware subjacentes sem reconstruir a experiência do Captive Portal.

pricing_comparison.png

Solução de Problemas e Mitigação de Riscos

Risco: Expansão do Escopo nos Requisitos de Marketing Muitas equipes de TI implementam um Captive Portal básico apenas para o departamento de marketing solicitar integração de CRM e análise de fluxo de visitantes seis meses depois. Mitigação: Se os requisitos de marketing forem antecipados, implemente uma arquitetura de sobreposição como a Purple desde o primeiro dia para evitar uma migração de plataforma dispendiosa posteriormente.

Risco: Bricking do Firmware durante a Instalação Gravar firmware personalizado em APs acarreta um risco pequeno, mas não nulo, de inutilizar o dispositivo. Mitigação: Se estiver implementando Tanaza, utilize um ambiente de teste para gravar e testar os APs antes de enviá-los para o local de implantação, ou adquira Dispositivos Tanaza Powered pré-gravados.

ROI e Impacto nos Negócios

O retorno sobre o investimento para plataformas de Captive Portal é medido de forma diferente dependendo da arquitetura escolhida.

Para implementações Tanaza, o ROI é tipicamente medido em eficiência operacional. A capacidade de gerenciar APs de múltiplos fornecedores a partir de um único painel reduz as visitas técnicas e simplifica a solução de problemas para MSPs.

Para implementações Purple, o ROI é medido em aquisição de dados e inteligência operacional. Ao capturar dados primários verificados e rastrear tempos de permanência física, os locais podem automatizar campanhas de marketing que impulsionam visitas repetidas. Em ambientes de Hospitalidade e varejo, isso transforma a rede WiFi de uma despesa de TI em um gerador de receita mensurável.

Termos-Chave e Definições

External Captive Portal

A mechanism where the network controller redirects unauthenticated users to a splash page hosted on an external server, rather than serving the page locally from the access point.

This is the architecture Purple uses to remain hardware-agnostic and scalable across enterprise deployments.

Zero-Touch Provisioning

The ability to configure a network device remotely so that it automatically downloads its configuration from the cloud the moment it is connected to the internet.

Crucial for MSPs deploying Tanaza to multiple remote sites without sending specialized IT staff.

First-Party Data

Information a company collects directly from its customers, such as email addresses and demographics gathered during WiFi authentication.

The primary value driver for marketing teams utilizing Purple's Capture and Engage tiers.

Firmware Flashing

The process of overwriting the original manufacturer's operating system on a hardware device with a custom operating system.

Required when deploying Tanaza on third-party hardware to enable cloud management.

RADIUS

Remote Authentication Dial-In User Service; a networking protocol that provides centralized Authentication, Authorization, and Accounting (AAA) management.

Used by both platforms to securely authenticate users and enforce bandwidth or time limits.

Dwell Time

The measurable duration a visitor spends within a specific physical location or zone, tracked via their device's WiFi probe requests.

A key operational metric provided by Purple's analytics engine, used heavily in retail and hospitality.

Audit Trail

A secure, immutable record of user actions, specifically relating to when and how a user consented to data processing terms.

Essential for demonstrating compliance with GDPR and other privacy regulations during an audit.

Overlay Architecture

A software or service layer that operates independently of the underlying physical network infrastructure.

Allows platforms like Purple to provide unified analytics across disparate hardware environments.

Estudos de Caso

A 350-room hotel chain needs to deploy a captive portal across 12 properties. They currently use a mix of older Ruckus ZoneDirectors and new Cisco Meraki MR access points. They require GDPR-compliant guest access and want to integrate guest emails with their central HubSpot CRM.

The IT team should deploy Purple using the overlay architecture. They will configure the Ruckus ZoneDirectors and Meraki dashboards to redirect guest traffic to Purple's external captive portal. In the Purple dashboard, they will build a unified splash page, enable the HubSpot native integration, and configure the GDPR consent workflows.

Notas de Implementação: This approach works because Purple is hardware-agnostic and does not require firmware flashing, allowing it to seamlessly bridge the mixed Ruckus/Meraki environment. Tanaza would require flashing custom firmware, which is not supported on all enterprise controllers and would disrupt the existing management paradigms. Furthermore, Purple's native HubSpot integration satisfies the marketing requirement without custom development.

A regional Managed Service Provider (MSP) is deploying WiFi for 40 small independent coffee shops. The shops need basic click-through WiFi access. The MSP wants to minimize hardware costs and manage all 40 sites from a single dashboard.

The MSP should deploy Tanaza. They can purchase cost-effective access points (e.g., TP-Link or Ubiquiti), flash them with TanazaOS in a staging lab, and ship them to the coffee shops for zero-touch provisioning. They will use Tanaza's multi-site dashboard to monitor AP health and configure a basic click-through splash page for each location.

Notas de Implementação: Tanaza is the optimal choice here because the primary requirement is centralized network management of low-cost hardware, not marketing analytics. The MSP benefits from Tanaza's multi-tenant architecture and zero-touch provisioning, while the coffee shops get reliable, basic guest access.

Análise de Cenário

Q1. A stadium IT director wants to monetize their high-density WiFi network by displaying sponsor advertisements on the splash page and capturing fan emails for the ticketing CRM. They have a newly installed Cisco Catalyst network. Which platform should they choose?

💡 Dica:Consider the requirement for CRM integration and the existing enterprise hardware.

Mostrar Abordagem Recomendada

They should choose Purple. Purple integrates natively with Cisco Catalyst WLCs without requiring firmware changes, which is critical for a high-density stadium deployment. Furthermore, Purple's native CRM integrations and advanced splash page builder support the marketing and monetization requirements, whereas Tanaza would require third-party add-ons and firmware flashing that is incompatible with enterprise Cisco controllers.

Q2. A franchise owner of 15 fast-food restaurants needs to replace aging consumer-grade routers. They have a very tight budget, no dedicated IT staff, and just want to offer customers 30 minutes of free WiFi without capturing data. What is the recommended approach?

💡 Dica:Focus on the need for low-cost hardware and simplified multi-site management without marketing needs.

Mostrar Abordagem Recomendada

They should choose Tanaza. The franchise can purchase low-cost hardware like TP-Link or Ubiquiti, utilize Tanaza's zero-touch provisioning for easy deployment without on-site IT staff, and use the built-in splash page to enforce the 30-minute limit. The Tanaza Pro tier provides cost-effective centralized management for this exact scenario.

Q3. An enterprise retail chain operating in the EU is migrating to Juniper Mist access points. They need to ensure their guest WiFi captures explicit, auditable consent for marketing communications to comply with GDPR. How should they architecture this?

💡 Dica:Evaluate how both platforms handle compliance and their compatibility with Juniper Mist.

Mostrar Abordagem Recomendada

They must deploy Purple as an overlay on the Juniper Mist infrastructure. Purple natively supports Juniper Mist via external captive portal integration. More importantly, Purple's architecture is designed to capture and store auditable GDPR consent records per user, providing the necessary legal protection for the retail chain's marketing activities.