Platform Overview

​

Platform Structure

Wiacom has two administration sides: The inventory hierarchy is: Access Points → Zones → Location → Customer account. Each location belongs to exactly one business name (required for data protection compliance). Wiacom separates infrastructure administration from venue-level operations. The MSP/Admin side controls customer setup, inventory, vendor integration, compliance configuration, and platform provisioning. The Client Account side gives venue operators control over their own portal experience, user onboarding, campaigns, reports, and operational troubleshooting. This separation allows partners to manage infrastructure centrally while customers manage their own guest-facing WiFi experience. Wiacom also includes a dedicated User Portal (WUP) for registered WiFi users. This portal allows end users to access and manage their personal data, privacy preferences, consent status, and related GDPR requests through a self-service interface. While the MSP/Admin and Client account areas are used by operators, partners, and venue teams, the User Portal is designed for the registered user. It provides transparency and control over personal data, supports GDPR compliance, and reduces manual workload for legal and support teams.

​

Access Features

Access features define how a validated user is granted WiFi connectivity. Each access feature maps to specific WiFi technology supported by one or more vendors.

​

Onboarding Channels

Onboarding channels are how users register, are identified, and trigger an access flow. A user can be onboarded through one channel and then access via any configured access feature.

​

Sign-up and Identity Methods

Regardless of the onboarding channel, Wiacom supports multiple identity verification and registration methods:

• Email sign-up with confirmation
• Phone registration with PIN / OTP verification
• Social login through Identity Providers (IdPs), including but not limited to Google, Apple, Facebook, LinkedIn, X / Twitter, Microsoft, and other supported providers
• Enterprise OAuth / SSO integrations, including Microsoft Entra ID / Azure AD, Office 365, and other compatible identity platforms
• Voucher-based registration, Internet Access Plans
• API-created identities
• Pre-registered identities, created by an administrator or imported in bulk
• Custom business integrations

​

Post-Validation Access Flow

After a user is successfully validated through any onboarding channel, Wiacom applies the access workflow configured for that location:

• Captive portal RADIUS authorisation (per-user auto-generated credentials)
• RADIUS Access-Accept
• Unique PSK (iPSK / MPSK) provisioning
• Passpoint profile delivery
• Personal SSID provisioning (Horizon)
• Expiry, quota, bandwidth, and session policy enforcement

For public venues and guest access, users also receive a link to a self-service privacy page where they can manage personal data, consent records, and exercise their data protection rights.

​

Equipment Onboarding

WiFi equipment is integrated with Wiacom in two modes:

​

Legacy Mode (Manual)

For any vendor — no API integration required.

1. Single device: Go to Inventory → Routers → Add New Router, select vendor, fill details, assign a location.
2. Bulk import: Go to Inventory → Routers → Unallocated Routers → Import from Excel. Download the template, fill it in, select vendor and location, upload.

Manually configure the device with the RADIUS server and portal URL provided by Wiacom for your region.

​

API Mode (Controller Integration)

For vendors with API support. Wiacom connects to the vendor cloud, discovers networks and SSIDs, assigns roles, and pushes configuration automatically.

1. Go to Inventory → Controllers → Add Controller.
2. Select vendor, enter API credentials.
3. Map networks to Wiacom locations.
4. Assign SSID roles (Portal / WiFi Pass / Key Access).

​

Deployment Options

Wiacom supports three deployment models to accommodate different commercial, branding, and infrastructure requirements.

​

Cloud-Hosted (Standard)

The default model. Wiacom operates the platform on its own cloud infrastructure. Customers access the platform through a dedicated subdomain under the Wiacom root domains.

​

White-Label

The platform can be deployed under a partner or customer brand. In white-label mode:

• The platform is served from a customer-owned or partner-owned domain (e.g. wifi.yourbrand.com), configured via DNS CNAME to the Wiacom infrastructure
• All portal pages, registration flows, dashboards, and email communications can be fully rebranded — logo, colour scheme, domain, sender identity
• No Wiacom branding is visible to end users or venue operators unless specifically agreed
• SSL/TLS certificates are provisioned for the custom domain as part of the setup

White-label deployments are typically used by MSPs, resellers, and enterprise operators who deliver the service under their own brand.

​

Customer-Hosted (On-Premise / Private Cloud)

The Wiacom platform can be deployed on customer-owned or customer-managed infrastructure. This option is available for operators with specific data residency, network isolation, or compliance requirements that preclude use of shared cloud infrastructure. Customer-hosted deployments require server infrastructure meeting Wiacom’s minimum specifications, and the deployment and ongoing maintenance are scoped and agreed with the Wiacom team.

​

Platform Services

​

Data & Security

• All data processed and stored in compliance with GDPR
• Guest PII is never transmitted to WiFi vendors — only anonymised credentials reach controllers
• All platform communication uses HTTPS / TLS 1.2+
• Credentials encrypted in transit and at rest