Static IP reservation now covers Internal Accounts too.
A few weeks ago we shipped Static IP / reserved addressing for Subscriber accounts, our answer to a traditional ISP's PPPoE-style fixed line. This week we extended it to Internal Accounts as well, the named logins businesses provision themselves for residents, staff, and students.
Why this matters: a landlord's building has security cameras. A school has staff devices and shared printers. A clinic has a booking terminal. All of them need to be reachable at the exact same address every time, not whatever DHCP feels like handing out that day. Now any internal account can have a device permanently assigned a fixed IP, pushed straight to the router as a real DHCP reservation, no manual router configuration required.
SSO logins get this automatically too, since an SSO login already is a real internal account under the hood on our platform, not a separate record bolted on the side.
We were deliberate about where this stops. It's not offered on vouchers, data plans, or ad-unlocks, those are short-lived, often anonymous grants, and a permanent IP reservation tied to one would just become orphaned router configuration once that guest moves on. It's also not offered to roaming guests, since an IP reservation only ever exists on one specific router's own network, and roaming's whole point is moving between different venues that don't share address space. Static addressing only makes sense where there's a real, ongoing relationship behind it.
Before shipping, we ran this against a live test environment: tenant isolation, input validation, and injection resistance, all verified end to end against real infrastructure, not just reviewed on paper.
Small, deliberate features like this are what turn guest WiFi into real network infrastructure.