A guest checks in.
Choose the right property, use your usual validity preset and hand over a guest code. Keep each property’s controllers together in a profile.
One voucher app · five platforms
UniFi tucks voucher creation away inside network administration. When a guest needs WiFi, finding those controls becomes an unnecessary detour. WiFi Vouchers puts creating, sharing and revoking codes right in front of you — in one app across all five platforms.
Free · Your controller · No additional app account
Version 2.2.0: see the release preview →
Find us onProduct Hunt
Opening network administration, finding the voucher controls, then creating a code: a small request becomes a series of interruptions. Connect your controller once in WiFi Vouchers. Next time, open the app, choose the validity and create the code.
Choose the right property, use your usual validity preset and hand over a guest code. Keep each property’s controllers together in a profile.
Make a short-lived voucher without navigating the network administration screens. Share the code as a message or a printable card.
Open the same app on whichever device is at hand and create access for visitors. Switch between controllers in the sidebar and check the vouchers you have already issued.
iPhone, Android, Mac, Windows or Linux: the same voucher workflow adapts to the space available. Use a profile for each place or customer and keep its controllers together. Your UniFi controller continues to manage guest access.

Name a profile, connect its first controller and keep the API key in secure device storage. Add further controllers to the same profile.
Keep the validity periods and voucher presets you actually use. Change them on dedicated editing screens.
Voucher codes are entered in your hotspot portal. A WiFi password QR joins an SSID directly. The app supports both, with different cards for each.
Share a profile by QR or link with a trusted colleague. It contains controller API keys, so treat it like a credential.
The guides show the app you will use, with a screenshot beside each step. Start with your first profile, or go straight to handing a guest a code.
Part of the app since version 1.7: create a voucher through your paired iPhone from Apple Watch, or open a saved preset from a Home Screen widget.
Choose 1 hour, 4 hours or 1 day. Create through the paired iPhone and read the result on your wrist.
Two presets in the small widget, four in the medium one. Tap a preset to open the app and create the voucher.
Illustrative mockups based on the Apple Watch and iOS widget views · demonstration data.
Direct connections go to your controller. The optional cloud service stores encrypted profile copies and voucher observations; it does not sit between the app and UniFi.
For a team that only needs voucher operations, you can run the optional unifi-voucher-proxy yourself. The app uses a proxy token while the controller API key stays on your server.
Optional cloud sync
Keep a profile, its presets and the voucher history in step across your devices. Everything is encrypted before it is uploaded, and the keys never leave your devices. Sync stays off until you turn it on.
Your profile, presets and voucher codes are encrypted on your device. The service stores copies it cannot read, and it never connects to your controller.
Settings and presets you change as the owner follow on every linked device. Each voucher is recorded once in the shared history, however many devices see it.
Delete your cloud data from the app at any time; operator backups expire on their own schedule. The protocol is public, so you can host a compatible service yourself.

What the service actually holds
Before anything leaves your device, the app locks your profile and voucher history with keys that only your devices hold. What arrives on our servers is a sealed box. We store it and hand it back to your devices, but we cannot open it. All we can read is the label it needs to be stored and delivered.
The label on the box. Enough to store and deliver it, nothing about your network.
The contents of the box. Readable on your devices only.
The other side of that promise. We hold no key, so we cannot reset one. Lose every device and your recovery password, and nobody can restore your data — including us.
Start with the network you already have
You need a reachable UniFi controller with a compatible Integration API. For vouchers, configure a guest hotspot with voucher authentication first.
iPhone, Android and Mac are distributed through the app stores. Windows and Linux downloads are hosted on Fairu. These are downloads of the app; the optional proxy is a separate server service.
Before you connect your first controller.
Voucher creation is tucked away in UniFi’s network administration. WiFi Vouchers gives that everyday task its own clear starting point: choose a preset, create a voucher and share it. It is one app for iPhone, Android, Mac, Windows and Linux; your controller still manages the vouchers.
Yes. WiFi Vouchers is free for business use, for example at a hotel, café or campsite. You don’t need a separate license.
No. Your controller still creates and enforces vouchers. Guests connect to the hotspot and enter their voucher in its portal. The app makes issuing and managing those codes easier.
The connection flow uses a controller API key, or a token for your self-hosted proxy. It does not ask for the controller administrator’s username and password.
It cannot search Apple’s system WiFi keychain. Copy a WiFi password from your password manager and use “Paste password”. It stays in the form until you save it.
The guide follows the current screens, from creating a profile to handing a code to a guest. Screenshots use example networks and credentials.
Use the Apple App Store for iPhone and Mac, and Google Play for Android. The Windows and Linux pages provide installation instructions and verified downloads hosted on Fairu once available.
No. These downloads are the WiFi Vouchers app, with its voucher interface and profile management. The optional unifi-voucher-proxy is a separate server service that limits controller access. The app can connect directly to your controller without a proxy.
No. Direct controller and self-hosted proxy connections continue to work without our cloud. Cloud linking and automatic sync are optional. The new cloud workflow requires matching current app/service source builds; older store releases or deployed APIs may not include it.
The app defaults to https://cloud.getvouchers.app. The new normal setup has no manual token field: an enabled service accepts an encrypted profile and confirms its UUID. Administrators can allow or close registration per service installation and set a profile limit. Another compatible HTTPS service can be selected before linking. A closed or older service needs an administrator update, not a guessed UniFi API key.
It is the public identifier of one encrypted cloud profile. The app creates a random UUID and the service confirms it at registration. The UUID alone cannot read or decrypt your profile. Authorization capabilities and encryption keys are generated and managed by the app.
For another device you own, enable Password recovery and retain the profile UUID plus a separate strong password. Choose Restore owner access on the other device. For a recipient with a simplified interface, choose Manage devices → Add device and create a sharing code instead. iOS/Android can scan the relevant QR locally; every platform supports manual entry.
A sharing code gives recipient access to the saved configuration and shared voucher journal. UUID plus recovery password restores owner cloud permissions, including configuration changes, sharing, revocation and deleting cloud data. Both roles create and revoke vouchers normally, straight from the device to the controller; recipients get a simplified view without controller addresses, keys, profile management or the WiFi tab. The cloud service itself never connects to your controller and cannot create or revoke vouchers. A recovery QR contains only UUID and service address; enter the password separately.
Yes, in the cloud workflow. The app encrypts configuration, connection credentials and voucher-log contents before upload with XChaCha20-Poly1305. The API and PostgreSQL store ciphertext without the decryption keys or recovery password. Voucher codes inside journal entries are encrypted too. The separately operated proxy workflow deliberately lets its operator read its configuration and optional journal; it is not E2E encrypted.
Public UUIDs, authorization hashes, data sizes, ordering and receipt times remain visible. For sharing codes the service sees how many a profile has, when each was created, when it ends, whether it is for one device and whether it was redeemed; their names and the codes themselves are encrypted. Network operators can see traffic metadata such as IP addresses. They cannot read the encrypted profile or voucher contents. E2E encryption does not prevent deletion, delay or omission by a malicious service, and is not a complete audit of controller activity.
Enable automatic cloud sync separately on each device; it starts off. While the app is open it checks about every three seconds. Owner devices upload profile and controller changes, validity presets, quick-create voucher presets and shared WiFi passphrases when they change, and every other device, owner or recipient, applies them automatically; settings need no separate save. The voucher history receives encrypted live updates normally within about one second plus network latency. The journal need not be open. Saved connection changes are used when you reconnect. Language stays a per-device preference (recipients follow the profile’s language), WiFi networks hidden on a device stay hidden there, and device security, tray mode, the active controller selection and connection recency remain local.
Local edits and already queued encrypted voucher entries are retained. The app retries after reconnecting and shows pending/offline status. Suspended mobile apps catch up when resumed; this is not background push delivery. Concurrent edits on two owner devices require an owner decision about which configuration to keep. The app never silently overwrites a newer revision.
You decide for each code. Under Settings → Cloud sync → Manage devices → Add device you name the code, choose whether it is valid for one device (the default) or several, and choose when access ends: a code can have no expiry or end after 1, 7, 30 or 365 days. A one-device code is bound to the first device that redeems it. When access ends, the service stops accepting that device and the code can no longer be redeemed. You can revoke each code separately; the others keep working. Treat a code as a credential until then. Revocation or expiry stops future cloud access, but cannot erase copied data or revoke external controller credentials; rotate the controller or proxy key to fully remove a device. Codes created by earlier app versions keep working and can be revoked in the same list. Older one-use invitations retain their original ten-minute expiry.
No. UUID/password recovery uses Argon2id locally to unwrap encrypted owner keys. The service receives neither the password nor plaintext keys. The service releases the encrypted recovery packet only to a device that proves it knows the password, using a capability derived from it, and allows 10 failed attempts per profile in 15 minutes. Someone who knows only your UUID can therefore make only rate-limited online guesses; guessing offline would require a copy of the service database. A strong password still matters: use the password generator and a password manager. Someone who knows the UUID can temporarily pause recovery, not sync, by sending wrong guesses. Changing or removing recovery does not invalidate keys or packets already copied.
Turning sync off stops automatic cloud reads and new log uploads on that device. It does not delete remote records; no new observations are collected for later automatic upload while off. Deleting a local profile also does not delete the cloud copy or backups. To delete the cloud copy, the owner chooses Delete cloud data in cloud settings; backups follow the operator’s retention policy.
As the owner, open Settings → Cloud sync and choose Delete cloud data. This removes the encrypted profile, voucher history, sharing codes and password recovery from the service. Linked devices lose cloud access, and the profile stays on your device as an ordinary local profile. Recipients see Remove from this device instead, which only removes the shared profile from that device. Backups held by the service operator expire on the operator’s schedule.
No. Every device derives the same ID for the same voucher and action, and the service stores each ID once, so each voucher is recorded once however many devices see it. Vouchers created or revoked on any device appear in the shared history. A voucher that a device merely sees is recorded as observed at most once, and not at all if its creation or revocation is already there. Older histories with repeated observations are shown de-duplicated.
Cloud settings show a saved version, the profile UUID and a success or error message after an action. Automatic sync has separate syncing, up-to-date, pending/offline and conflict states. A failed request is not a successful save. If registration is closed, capacity is reached or the service is incompatible, the app explains that condition without asking for a guessed token. See the setup guide.
Yes. The public protocol reference documents the endpoints, JSON formats, UUID registration, HKDF/AAD, encrypted journals, sharing and password recovery. Download its public interoperability vectors to check your implementation. HTTPS and scoped controller/proxy credentials remain necessary.
No. There is no sign-up, email address or login. The app creates a random profile UUID and its own keys on your device; the service only confirms the UUID. Access comes from those keys, a sharing code from the owner, or the owner's UUID plus recovery password.
No. The service only stores encrypted copies of the profile and the voucher history. Creating and revoking vouchers always goes straight from your device to your controller or your own proxy, so the service never needs to reach your network.
You keep working. Vouchers are created and revoked directly on your controller, and the profile stays saved on your device. Changes and voucher events are queued as ciphertext on the device and uploaded once the service answers again.
As the owner, open Settings → Cloud sync → Manage devices. Every device has its own named sharing code with its status and end date. Choose Revoke on that entry; the other devices keep working. A revoked device keeps the connection details it already received, so renew the controller or proxy key if it must lose access completely.
Yes, so one profile cannot fill the service. A profile can have up to 64 sharing codes and 10,000 voucher history entries or 10 MB of encrypted history. Each installation also limits how many profiles it accepts. When a limit is reached the app reports it and keeps the data on your device.
After 10 failed attempts for a profile within 15 minutes, the service refuses further recovery attempts for that profile until the window has passed. The service only releases the encrypted recovery packet to someone who proves knowledge of the password, and it never sees the password itself.