> ## Documentation Index
> Fetch the complete documentation index at: /docs/llms.txt
> Use this file to discover all available pages before exploring further.

# External Vaults: Connect Password Managers

> Connect Buckle to Bitwarden and other password managers. Pull credentials from vaults you already use. Agents never see the secrets.

## Overview

Vaults let the Buckle gateway fetch credentials directly from your password manager at request time, without storing them on the server.

![The Vaults tab under Settings > Apps in the Buckle dashboard](https://mintcdn.com/onecli-17d3f772/hJP3XqgFsBDnXHKy/images/connections-vaults.png?fit=max\&auto=format\&n=hJP3XqgFsBDnXHKy\&q=85\&s=bb3b2c3c06209643fad2501f4fbd2cc7)

## How vaults work

When an agent makes an HTTPS request and no server-stored secret matches the target host, the gateway checks if the user has a paired vault. If so, it asks the vault for a credential by domain, injects it into the request, and caches it briefly in memory.

```
Agent ──► Gateway ──► Secret Store (check DB secrets)
                │
                │  no match
                ▼
          Password Manager (fetch credential)
                │
                ▼
          Gateway ──► External Service (inject + forward)
```

Credentials never hit disk or the database. They're cached in gateway memory for 60 seconds, then discarded.

## Vaults vs server-stored secrets

| | Server-stored secrets | Vault credentials |
| - | - | - |
| **Storage** | Encrypted in database | Stay in your password manager |
| **Priority** | Checked first | Fallback when no DB secret matches |
| **Setup** | Add via dashboard | One-time pairing with the vault app |
| **Rotation** | Manual update in dashboard | Automatic (always reads latest from vault) |

Use server-stored secrets for stable, shared credentials. Use vaults for personal credentials, frequently rotated keys, or when you don't want secrets leaving your password manager.

## Supported providers

> [card] [Bitwarden](/docs/vaults/bitwarden.md)
>
> Connect your Bitwarden vault via the Agent Access SDK. Credentials are fetched through an encrypted Noise protocol channel.

> [card] [1Password](/docs/vaults/1password.md)
>
> Connect your 1Password vault via Service Accounts. Map hostnames to op\:// references and resolve secrets at runtime.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.