jo saillier Contact
Secrets Vaultsecurity

Secrets Vault

Keeps API keys behind Touch ID, and gives each project only the keys you approve.

FACTS
Role
Creator
Team
Solo
Status
In daily use, open source (MIT)
Secrets Vault

In short.

Secrets Vault keeps API keys in the Mac's Keychain, behind Touch ID. AI coding agents can list the key names without seeing any value. When a project needs a key, you approve that project and those names, and only they are written to its local .env file.

It runs as a native Mac app with a small local web interface: add, rename, replace, reveal or copy a key, each behind a fresh Touch ID check. Provisioning refuses to run unless the project's .env is ignored by Git, so a key can't be committed by accident. The source is open under the MIT licence.

STACK USED

Mac app

  • Swift
  • AppKit
  • WebKit

Security

  • macOS Keychain
  • Touch ID
  • Keychain access lists

Interface

  • Node.js
  • Local web UI
For you

How it makes your life easier.

Store each key once

Add a key once and every new project can ask for it. No more hunting through old .env files, chats or notes.

Approve with a fingerprint

Your coding agent sees which keys exist and asks for the ones it needs. One Touch ID and you are back to work.

Nothing leaks by accident

Keys land only in a .env that Git ignores, and values stay masked on screen, so a push or screen share gives nothing away.

All projects.

Contact

Get in touch.

Have a question or a project in mind? Send me a message.