Download and evaluation
Evaluate Bouncer Vault
There are no public downloads. Check what you need below, then email S6 Studios for access to the current private release.
Release status
Checked 19 November 2026. The current release is 0.5.7, published on 19 November 2026 as the private GitLab release v0.5.7+34, built from commit b329764d1b909dc6cc5fbd560d018933d14ab8e0. The 0.5.7 release notes list what changed.
| App or part | Platform | Status today |
|---|---|---|
| Bouncer Mobile | Android 9 or later | Private beta Installed from an APK file supplied with access. Google Play's internal test track holds an older build for S6 Studios' own testing. Your own server can't send phone notifications to the official app yet, so open the app to see waiting requests. |
| Bouncer Mobile | iPhone, iOS 15 or later | Not available Version 0.5.7 is in internal TestFlight testing at S6 Studios. |
| Bouncer Desktop | Windows 11, x86_64 | Private beta Beta MSIX signed with a test certificate, or unsigned portable ZIP. Approving requires a Windows Hello passkey and a server that accepts Windows Hello keys (off by default). From 0.5.7, the server checks a TPM attestation when a Windows Hello key is enrolled, if Windows supplies one. No real PC has passed that check yet, and keys enrolled earlier stay unchecked, so no Windows key is confirmed as hardware-backed today. Requests arrive only while Bouncer Desktop is running, including from the notification area. |
| Bouncer Desktop | macOS | In development No supported release to install yet. |
| bouncer and bouncer-mcp | Linux x86_64 and Windows x86_64 | Private beta Linux tarball, .deb or .rpm; Windows ZIP with a per-user installer. The Linux and Windows tools are unsigned. No public package repository yet. |
| Bouncer server | Linux x86_64, Docker Compose or Podman | Private beta A prebuilt container image and deployment kit are in the private release. Uses OpenBao and PostgreSQL on infrastructure your organisation controls. The container image is unsigned. |
Evaluate free with up to 25 paired devices
You can evaluate Bouncer free with up to 25 paired devices and unlimited users. A trial with more than 25 paired devices is optional; see larger teams.
- Check your setup. You need an administrator who can run Linux x86_64 containers, maintain OpenBao and PostgreSQL, configure HTTPS and keep backups. Bouncer runs on one server with no failover, so keep a way into your systems that doesn't depend on Bouncer, such as a break-glass account. The manual's page When Bouncer is unavailable explains what still works during an outage. You also need an Android phone or Windows 11 PC to approve, and a Linux or Windows machine to make requests. The setup outline lists the software requirements. The guide supplied with 0.5.7 uses Tailscale to make the server reachable privately over HTTPS. If you plan to use a different network setup, check it with S6 Studios first.
- Ask for access. Email support@bouncervault.com with your operating systems, roughly how many people and devices will use Bouncer, and whether you already run OpenBao. Don't send passwords, keys or pairing codes. Ask for the release tagged
v0.5.7+34, with its checksums and install instructions. - Get the files. S6 Studios will either give your GitLab account access to the private project that holds the release, or send you the files. Links into that project only work once that access is set up.
- Check, install and try it. Verify the files and publisher information below, and follow the instructions for that exact release. Run one request through approval, use and revoke, and read the security model and its limits.
Files to ask for
Ask for these files from release 0.5.7. They are file names, not links. Installation instructions come with the files.
- Android app:
bouncer-android-, the production APK, and0.5.7+34.apk bouncer-android-. Theupload-certificate.pem bouncer-android-file is for S6 Studios' own testing and isn't sent to evaluators.0.5.7+34-internal.apk - Windows app:
bouncer-windows-x64-0.5.7+34.msixwithbouncer-beta-signing.cerandbouncer-windows-, orinstall-instructions.md bouncer-windows-x64-0.5.7+34.zipfor the portable app. - Linux CLI and MCP:
bouncer-cli-with0.5.7+34-x86_64-linux.tar.gz install.sh, or the release's.debor.rpm. Windows tools usebouncer-cli-with0.5.7+34-x86_64-windows.zip install-windows-cli.ps1. Self-update isn't available yet. - Server:
bouncer-server-0.5.7+34-image.tar.gz,bouncer-server-0.5.7+34-compose.tar.gz,INSTALL-SERVER.mdandbouncer-server-0.5.7+34-SHA256SUMS. With the prebuilt image you don't compile the server yourself. The kit includesdeploy/compose/README.mdand its upgrade, backup and rollback instructions.
For an upgrade, use the new release's guide and keep the previous kit and a tested backup. Before starting it, compare BUILD-INFO, the image revision and the version with the release you asked for. Version 0.5.7 adds database migrations 0017 to 0019, so the only way back is to restore the backup taken before the upgrade. After a restore, wait the longest SSH credential lifetime plus five minutes from when the server was stopped, then reset each SSH host's revocation-list version, as the release notes describe. Upgrade the role kit first; the release notes give the order. The release checks upgraded a 0.5.6 test server with fake data and a sandbox OpenBao. They didn't cover every app feature or a real deployment, so ask S6 Studios to confirm the upgrade path from your current version.
Check the files and publisher
Get SHA256SUMS directly from the private release. On Linux, in the folder containing your selected files, run:
sha256sum -c SHA256SUMS --ignore-missing
Every file you downloaded must report OK. --ignore-missing skips release files you didn't download. SHA256SUMS covers every file in the release, and the server files also have their own bouncer-server-0.5.7+34-SHA256SUMS. The SHA256SUMS file published with 0.5.7 has this SHA-256:
a5fef128f5add90d4fb3ba932e5c28fdf69d79f18b9533d287298ebf661e2224
On Windows, use Get-FileHash -Algorithm SHA256 <file> and compare it with the matching line. If it doesn't match, don't install that file.
A checksum shows a file matches the list. It can't show who published it: if someone replaced both the files and the list, they would still match. The container image, Linux tarball, .deb, .rpm, Windows portable app and Windows CLI are unsigned, and releases don't yet come with a signed file list.
The Android APK is signed with S6 Studios' upload certificate, whose SHA-256 fingerprint is:
C3:
It is not Play-signed. A sideloaded APK and the Play build cannot update each other in place, and you cannot downgrade in place. Uninstalling to switch builds or install an older version removes the pairing; pair the device again afterwards.
The 0.5.7 Windows MSIX has beta identity S6Studios.Bouncer.Beta, publisher CN=S6 Studios Bouncer Beta and package version 0.5.34.0. It uses a test certificate, not a Microsoft Store distribution signature. Before you tell Windows to trust the certificate, check it with S6 Studios through a separate channel you trust, and follow the matching private installation instructions.
Phone notifications during evaluation
Phone notifications from your own server to the official apps aren't available yet: they need a sending key for S6 Studios' notification project, which we don't hand out. Open the app to see waiting requests. iOS 0.5.7 hasn't been checked on a real iPhone yet.