HashiCorp Vault alternative
A secrets manager with no cluster to run.
Clavitor keeps your API keys, SSH keys, tokens and passwords in one encrypted vault, hands each person, script and AI agent only the secrets it is scoped to, and records every read. We run it for you, in 26 regions.
Where it replaces Vault
What you would use Vault for, and how Clavitor does it.
- Secrets your code needs at runtime. One CLI call fetches a value, fills a config template, or starts your app with the real values in its environment. Your
.envfile holds pointers likeclavitor://Stripe/key, not the keys. - Keys an agent must use but should not read. The built-in HTTPS proxy puts the credential into the request on its way out. The agent only ever sees the reference.
- SSH keys.
clavitor-cli get "Deploy Key" --field private_key | ssh-add -loads a key without writing it to disk. - One identity per agent or script. Each client has its own token, its own list of entries it may read, and its own read limit.
- A record of every read. The audit log shows who read what, and when.
# A script gets its secret at runtime. Nothing is stored in the repo. $ clavitor-cli run --env-file .env -- ./server
How it differs
How they compare, row by row.
| Clavitor | HashiCorp Vault | |
|---|---|---|
| The server that stores your credentials can't decrypt them | ✓ ¹ | — |
| Per-field encryption tiers: your agent reads the API key, not the card in the same entry | ✓ | — |
| Unlocked by a hardware key (WebAuthn PRF) | ✓ | — |
| Ships its own credential-injecting HTTPS proxy | ✓ | — |
| Hosted, with no cluster for you to operate | ✓ | ✓ |
| Run on your own hardware | Enterprise ² | ✓ |
| Open source | — | ~ ³ |
✓ yes · ~ partly · — no. Checked against each vendor's own documentation on 3 Nov 2026; the sources are on the comparison page.
- Credential and identity fields. Titles and other vault-level fields are encrypted at rest with a key the server uses.
- Enterprise only: on the customer's own dedicated hardware, with our installer, on request.
- Business Source License 1.1 since August 2023.
Where Vault or a cloud KMS fits better
What Clavitor does not do.
Clavitor is a vault for the secrets you have. It is not a cloud key-management service: it does not run encrypt and decrypt calls for your application, and it does not hold your keys in a hardware security module you call from code. Automatic secret rotation is planned, and today it is something you do yourself. Vault, a cloud KMS or an HSM is the right tool when your application must send data to be encrypted or signed with a key that never leaves the service.
If your problem is the long list of credentials your people, scripts and AI agents use, and who is allowed to read each one, that is what Clavitor is for.
Try it with your own secrets.
Start with 10 entries free. Full encryption, all tiers, no credit card required.