Loading
Flagship case study · CSP
How MyWiFi built WorkPass — Plume's commercial WiFi platform.
When Plume Design — a CSP platform serving ISPs and cable operators worldwide — needed to take its adaptive-WiFi platform into the commercial SMB market, they didn't build the guest-experience layer from scratch. They partnered with MyWiFi to ship a multi-region, GDPR-compliant, 400+ endpoint API platform under Plume's brand.
400+
REST API endpoints
4
AWS regions, multi-continent
Global
CloudFront edge distribution
Weeks
Not quarters — scope to deploy
The Challenge
Plume's customers are service providers. Their SMB opportunity wasn't.
Plume is a Communications Service Provider platform — their customers are ISPs, cable operators, and telcos, not end-users. Service providers around the world were already shipping Plume pods into homes. The company had built one of the most sophisticated cloud-managed WiFi platforms in the industry.
The opportunity in front of them was commercial. SMBs — coffee shops, salons, dental offices, coworking spaces — wanted the same adaptive WiFi, but with something residential never required: a guest-facing portal, data capture, and an automated marketing layer. Building that in-house would have meant a new product team, data team, and compliance team. The timeline didn't have room for "build."
Why MyWiFi
Four things shortened the Plume evaluation significantly.
White-label from day one
Every surface — portal, admin UI, emails, API responses — ships under the Plume brand with no MyWiFi co-branding anywhere in the stack.
API-first architecture
Not a portal product with an API bolted on. Every customer-facing feature is a REST endpoint first, UI second — Plume's engineering team consumes it natively.
Multi-tenant by design
Plume's service-provider customers need isolated tenants with their own branding, data, and analytics. MyWiFi's core architecture already did this.
Multi-region data residency
Plume sells globally. A Canadian service provider can't have guest data in us-east-1; an EU one can't have it outside the EU. Our regional model mapped cleanly.
What we built
A production platform Plume operates as WorkPass today.
01
REST API Platform — 400+ Endpoints
Authentication, tenant management, venue provisioning, portal configuration, captive-portal session lifecycle, guest records, segmentation, campaign triggers, webhook emission, analytics queries, and administrative operations — every function in WorkPass is an API call first. Plume's product and platform teams consume the same API surface third-party integrators do. No internal/external feature asymmetry; no drift between docs and what works.
02
Multi-Region AWS Hosting
Multiple AWS regions matching Plume's service-provider footprint: Canada, the US, the EU, and Asia-Pacific. Each is a full deployment — API, database, portal edge, marketing worker pool — not a read replica. A tenant provisioned in the EU never has data leave the EU.
03
GDPR-Compliant Data Handling
Built to GDPR from the first commit: lawful-basis capture on every guest record, explicit opt-in for marketing, subject-access and erasure endpoints on the public API, regional audit logging, and DPAs that flow through to Plume's service-provider customers. Same primitives reused for PIPEDA (Canada) and CCPA (US).
04
CloudFront Edge + Direct AWS Integration
CloudFront fronts the portal and API edges for global low-latency delivery. The AWS account structure was designed so Plume holds direct IAM-level control — no opaque MyWiFi-managed layer between Plume and their data. Plume operates the environment as a first-class AWS tenant.
05
Captive Portal Engine
A Plume-branded captive portal running on every supported AP vendor — splash-page configuration, login methods (social, SMS, email, one-click), session authorization, bandwidth and time policies, and real-time session state — all driven by the same API surface that powers the admin UI.
06
Data Capture + Automated Marketing
Every guest session produces a data record: contact, demographics, visit frequency, dwell time, repeat-visit recognition. On top of that data layer sits the marketing engine — welcome sequences, first-visit offers, lapse-recovery triggers, and return-visit campaigns — firing automatically on guest behavior.
The Results
Scoped-product to live-platform in weeks. Infrastructure Plume still runs today.
Commercial WiFi, productized
Plume's SMB channel got a complete guest-experience layer without Plume staffing it in-house.
4-region global coverage
Guest data residency in Canada, the US, the EU, and Asia-Pacific, with CloudFront edges in front of each.
Full data sovereignty
Plume operates the AWS environment directly — no managed-service black box between them and customer data.
GDPR / PIPEDA / CCPA-ready
Subject-access, erasure, and consent primitives baked in — not bolted on.
API parity
Zero feature gap between internal Plume tooling and the external developer surface — because they're the same surface.
Service-provider-ready
Every Plume service-provider customer gets an isolated, brandable tenant out of the box.
Specific guest-volume, revenue, and adoption figures belong to Plume and are not disclosed here.
Same platform · Different brand
Plume runs WorkPass on it. Thousands of resellers ship their clients' portals on it.
Every portal below is a live deployment on the exact same MyWiFi infrastructure that powers Plume WorkPass. Different brand surface, same captive-portal engine, same multi-region API, same white-label controls.
Real customer portals
What your clients ship — not generic mockups.
Every screen below is a live deployment running on the MyWiFi platform. Your reseller clients build these in our drag-drop portal builder; you keep your name on the bottom.
● Live · United States
9:41MyWiFi · Subway
Powered by Subway · MyWiFi-white-labeled
The Product
WorkPass in production. The social-page captive portal.
Plume's WorkPass — guest WiFi captive portal powered by MyWiFi Networks
Why this matters for you
The platform we built for Plume is the same platform you get.
For CSPs
WorkPass is the commercial evidence.
Plume is a CSP. Their entire go-to-market is built around service providers — ISPs, cable operators, and telcos that resell managed WiFi as a product line. WorkPass is the commercial evidence that MyWiFi can operate at that tier: multi-region, multi-tenant, GDPR-compliant, API-first, white-labeled. If you need to add guest WiFi marketing to your service catalog without staffing a new product team — this is exactly the class of platform we built for Plume.
See CSP solutionsAlso applies to ISPs, SaaS, MSPs
Same platform. Different resellers.
- ISPs — productize this for your business-subscriber base: captive portal, data capture, and marketing automation billed on your existing invoice.
- SaaS platforms serving physical venues can embed the same API surface to add on-premise behavior data to their customer records.
- MSPs can resell it turnkey — quote, provision, brand, hand over a dashboard — with a recurring revenue story that closes without technical explanation.
Build your own WorkPass.
The platform behind Plume WorkPass isn't a custom one-off. It's the same MyWiFi platform that powers every reseller on our stack — with the same white-label, multi-region, API-first foundation.