Bouncer Vaultby S6 Studios

Bouncer Vault by S6 Studios

Time-limited grants to retrieve secrets

When a person, a script or an AI agent needs a password, an API key or SSH access, it asks your Bouncer server. Where approval is required, the people responsible see the request in Bouncer, check who is asking and why, and approve it for a set time, called a grant, or deny it. When a grant ends, Bouncer stops issuing credentials for it.

Your organisation runs the server, and S6 Studios can't see your requests or secrets.

Bouncer Mobile on Android: deploy-agent asks to read Production Postgres (orders-db) for 15 minutes to apply a schema migration, with Deny and Approve 15 min buttons
Bouncer Mobile on an Android emulator, with fake example data.

Manage access for AI agents

Give each agent its own identity in Bouncer. Your team decides which credentials an agent can request and when a person needs to approve access.

Once access is granted, an agent can carry on without waiting for anyone. People still make the decisions that require approval.

Store the credentials your tools already use in OpenBao, and Bouncer puts an approval step in front of them. You don't have to replace your identity system or wait for every tool to support agent identities.

What Bouncer Vault does

Bouncer adds an approval step in front of credentials stored in OpenBao, the open-source fork of HashiCorp Vault managed by the Linux Foundation. A person reads each request and signs a decision on their own device, and the grant sets how long access lasts.

Read before deciding

Each request names the resource, the requester, the reason and the length of access. Each detail is labelled Verified, Observed or Reported by requester, so an approver can tell what Bouncer checked.

Grants that end

The approver chooses how long access lasts, within the resource's limit. When a grant ends, Bouncer stops issuing credentials for it and asks OpenBao to revoke those already issued.

Signed on the device

Each approval is signed with a key made on the approver's phone or PC. A requester's key can't sign an approval. The security model explains what the server checks on each platform.

AI agents and MCP

The bouncer-mcp server lets an AI agent ask for access and wait for a person's answer. bouncer exec runs a command with the secret, without handing the value to the agent.

A record of decisions

The approval log records requests, decisions, revocations, app views and saves, and device changes. Export it as JSON Lines for your log store.

Runs on your infrastructure

Your organisation runs the Bouncer server next to its own OpenBao. Notifications carry only random IDs; the app fetches the details from your server.

From request to revoke

Every request follows the same steps, whoever sends it.

  1. AskA requester asks for one resource, with a reason and a length of time.
  2. NotifyApprovers see the request in Bouncer Mobile or Bouncer Desktop.
  3. DecideAn approver checks the details and approves for a chosen time, or denies.
  4. UseThe requester gets a scoped credential, such as a short-lived OpenBao read token.
  5. EndWhen the grant ends or is revoked, Bouncer stops issuing credentials for it.

Bouncer Desktop

The same inbox on Windows. Each detail says whether Bouncer checked it or the requester reported it, and approving signs with Windows Hello.

Bouncer Desktop inbox with three waiting requests. A deploy-agent request for 15 minutes of Postgres access is open beside it, with a note to approve it on the paired phone, Sam Pixel.
Bouncer Desktop on Windows 11, with fake example data. This PC has no Windows Hello key, so it shows the request and points approval to the paired phone.

Getting started

An administrator sets up the server once. Everyone else installs an app and connects it to that server.

  1. Run the server

    Your administrator runs the Bouncer server on Linux with Docker Compose or Podman, next to OpenBao and PostgreSQL.

  2. Install the app

    People who approve install Bouncer Mobile on their phone or Bouncer Desktop on Windows.

  3. Connect it

    Scan the QR code your administrator shows, or paste the pairing string, to connect the app to your server.

  4. Make a first request

    Ask for a test secret from the command line, approve it in the app, then revoke the grant.

Pricing

Free for up to 25 paired devices, with unlimited users and AI agents. Pricing details.