secretsmgr handbook
Editor sign-in

Keeping secrets, explained

Every team has passwords, API keys, and database credentials that a few people and a few machines need, and that nobody else should ever see. This handbook explains why that is hard and how secretsmgr makes it manageable. It assumes you know nothing about cryptography.

Two things make this secrets manager unusual:

  • Your secrets are encrypted before they leave your computer. Encrypted by you, on your machine, with a key the server never sees. Everything else follows from this one decision.
  • You can run it with no server at all. The storage is an ordinary git repository full of encrypted files. A server is optional, adds useful things, and can be switched on or off later without re-encrypting anything. The one this site runs beside lives at secrets.mikeruf.com.

Where to start

If you are…Read
New to all of thisEverything, in order, starting with What this is. It builds up.
A developer who just needs a passwordDay to day, then come back to the concepts when something confuses you.
Setting this up for a teamHow it works and Setting it up, then Limitations before you promise anyone anything.
A security reviewerThe powerless-server bet, the custody tiers, and all of Limitations. The design document (PRD) in the repository has the full threat model.

47 pages · search finds everything · the assistant answers with links.