Manual for Bouncer 0.5.7. Chapters state version and distribution limits. Source cdd3b59, site build 20 November 2026. Your server or app may run an earlier version.
Known limits
These are the limits of the current source that matter most when deciding what to put behind Bouncer. Where a limit differs in 0.5.6, the page says so. The platforms page has the status of each app.
Server and images
- No high availability. One server, one PostgreSQL database. An outage stops new access through Bouncer. Already issued tokens and SSH certificates keep their own expiry. In 0.5.6, an OpenBao outage prevents SSH hosts fetching a new revoke until OpenBao recovers. From 0.5.7, they can fetch during that outage once Bouncer has retained its CA public key; PostgreSQL must still be available (issue #281). A copied value or established session may outlast the grant (When Bouncer is unavailable).
- Images aren't signed, and there's no published container registry. The private 0.5.5 and 0.5.7 releases include an image download; building from a chosen source commit is another option. 0.5.6 has no GitLab release (Get Bouncer).
Identity
- People are entries in the config file. There's no single sign-on, directory or group sync. Code for an identity-provider verifier exists in the source but isn't connected to anything.
- Pairing is a one-time code, not a sign-in. Whoever uses the code pairs as that person.
- Requester keys are bearer keys in a file. There are no per-host certificates or hardware-bound requester keys yet.
Approvals
- One approval per request. There's no two-person rule.
- Standing grants ("Always") exist in the source, but the Bouncer project hasn't decided their policy yet. Turn them off with
durations.always: false. "Always approved" personal credentials have two open problems; keepceilings.always_approved: false(Approvals and access duration). - Re-confirming a standing grant is an admin action, not a fresh approval from a device.
- Standard Android keys only need the phone unlocked. Biometric keys are opt-in.
- Approving from a notification is Android only.
- Windows gets no push notifications: requests arrive only while the app or its tray icon is running. Device keys and user verification describes the release and verification limits for Windows Hello keys.
Secrets
- A value already read can't be recalled. Rotate it.
- Credential kinds: stored secrets, API keys and SSH host access. There are no database-credential or one-time-password kinds that issue fresh credentials per use.
- A copied value stays on the clipboard if the app can't clear it. Bouncer clears a copy after 30 seconds. On Android that only happens while the app is running. On Windows, from 0.5.1, it also happens when Bouncer quits or the session ends, but not after a crash or a forced close. Before 0.5.1, a Windows copy went to the ordinary clipboard, where Windows clipboard history and cloud sync can keep it; from 0.5.1 Windows keeps it out of both.
Operations
- Two lists to keep in step: the config file's resources and the role kit's
resourcesfile. - A new resource or an OpenBao change needs a restart.
- The approval log lives on the server. Nothing ships it elsewhere unless you set it up (Audit).
- A database restore brings back revoked access until you reconcile it (Backup and restore).
- The kit's example front end is
tailscale serve. Neither it nor any other reverse proxy was tested end to end for these pages (TLS and networking). - Push needs a Firebase key for the same project as the app builds. The official builds use the Bouncer project's own Firebase project, so a server of your own can push to them only with that project's key (Push notifications).
Clients
- The Windows CLI isn't code-signed. It's new in 0.5.1; check the zip against
SHA256SUMS. exec --fileandself-updateare Linux only.exec --stdinworks on Linux and Windows.- There's no public package repository for the Linux
.deband.rpmyet, and release builds can't self-update yet.
Verification scope
The verification notes beside each procedure say what was checked. The operator tests use fake data in isolated environments and a software stand-in for devices.
- The preparation checklist is checked against the source only. A test with fake data followed the download installation, but nobody has yet followed the current checklist from start to finish on a fresh deployment (Overview and prerequisites).
- Sizing needs measurement. The preparation checklist gives planning estimates, not a workload capacity guarantee. Measure database, OpenBao, audit and backup growth in your evaluation (Overview and prerequisites).
- HTTPS needs a check for your deployment. The manual describes network and certificate requirements. It does not supply a complete, tested setup for every reverse proxy or private CA. Check certificate name and trust, client reachability and forwarded addresses before pairing (TLS and networking).
- App and hardware checks are separate. The operator tests use a software stand-in for an approving device. Lifecycle tests exercise operator steps and the server API; they do not verify the app's screens or physical keys (Credential expiry, replacement and history).
- Moving from another secret store needs a plan for each system that uses a secret. These pages don't give a general procedure for importing secrets from another store, switching each system over, or switching back. List every system that uses or issues each secret, test each one with a fake credential, and have a way to switch back that doesn't depend on Bouncer before you plan the move. Storing a credential type in Bouncer doesn't make Bouncer able to issue it, and isn't a tested connector.
- Audit retention is operator-managed. The kit does not automatically ship logs off the server or set your log-store retention. Check delivery and recovery separately. The audit chapter's historical event table is not a complete catalogue of later lifecycle or assurance events (Audit).
- Rollback coverage is bounded. A test with fake data followed the download route from 0.5.5 to the unpublished 0.5.6 build and back. That test used the kit's
upgrade.shfor the upgrade. The tests did not run a full source-build rollback,ship.sh, or a server version without credential versions against data that had already been reconciled (Upgrade and roll back). - A database restore is only part of recovery. The tests don't cover recovering OpenBao's own storage (Raft), keeping backups off the machine, recovering from a separate workstation, fully reconciling what the restored database allows, or measuring recovery time and data loss. Bouncer doesn't reconcile a restore for you. Keep outside access closed until the restore checks that apply to you are complete.
The API and CLI reference pages are checked against the API definition and the tools' current --help output. Automatic checks confirm that the manual's example files are valid, but not that they suit your server's policy, OpenBao permissions or network. The environment variables page covers the main tools; variables for individual kit scripts are listed with those procedures.