A device token
For the person issuing vouchers.
Optional · self-hosted · open-source proxy
Guest access.
With limits you choose.
When reception needs to issue vouchers, give its devices a token for that job. Keep the controller API key on a server you control.
Your rules
Allowed sites, operations and limits.
The controller key
Used by the proxy on your server.
Useful when access
is a shared responsibility.
A direct controller connection is still available. The proxy is an option for teams that want to restrict what a particular device can do.
Choose the scope.
Allow reading sites and vouchers, creating vouchers or revoking them. Limit a token to the sites it should reach.
Set practical limits.
Configure voucher quantities, validity and request rates. Each device can have its own token.
Keep a record.
The proxy writes an audit log and pins the upstream controller certificate.
Run it yourself.
The public proxy repository contains the code, Docker configuration and setup instructions. You operate the service on your own infrastructure.
Configuration details: official proxy README ↗
Connect WiFi Vouchers
Same app. A different connection.
- Prepare the proxy.
Follow the repository’s setup instructions, configure the controller and create a token for this device.
- Choose proxy mode in the app.
Set up a profile and controller, then choose the proxy connection option. Enter the proxy’s address and the device token.
- Check the connection.
Connect and select a permitted site. The available actions follow the permissions granted to your token.