Featured · Engineering
Designing an API that scales to a million captive portals
Seven web API design assumptions captive portals break: cloud RADIUS, walled gardens without CDNs, one-shot bootstraps and roaming without a controller.
The Halo Journal
Field notes on internet for real life.
Product updates, deployment stories, and hard-won lessons from running guest WiFi across four continents.
All posts
Live Event WiFi Deployment: The Field Guide
How to plan and deploy WiFi for a live event: capacity math, AP counts, RF settings, segmentation, roaming and day-of ops. With a printable checklist.
The HaloWiFi team
Opening our API, or: how we learned to stop worrying and love other people's code
The two fears that almost kept our API closed, why both were wrong, and how opening it made the platform safer and bigger than we would have built alone.
The HaloWiFi team
Extending guest WiFi with a third-party extender
Stretch the guest network behind the captive portal with a TP-Link, Netgear or OpenWrt extender — and the three mistakes that break the portal.
The HaloWiFi team
From around the site
The API: everything the router does, over REST
Everything the router does, exposed over REST: locations, networking, guest login and mobile money, with a sandbox venue included.
One push, fifty properties: how a fleet config rollout works
Portal, firmware and campaigns updated across a whole portfolio in one push. What that looks like from the dashboard.
Runs where WiFi is hard: the deployment field log
Load-shedding in the Western Cape, coaches at 80 km/h, rentals with nobody technical on site — live on four continents.
Seven things we believe
Built in the field not a lab, data that belongs to you, support from the people who built the product. The manifesto behind the router.