Somewhere to put the things that don't belong in a repo.

Deploy scripts, .env files, API keys, the runbook nobody wrote down. Encrypted before storage, shared with exactly who you choose.

Encrypted per item: AES-256-GCM with a separate key for every secret, wrapped by a master key that never touches the database.
Four ways to share: The whole org, one team, one person, or nobody. Private means private — org owners can't read your items either.
Nothing is overwritten: Every save keeps the previous version. Read any of them back, or delete an item outright when a secret is burned.
Every access recorded: Who viewed what, when, and from where — visible to admins, without exposing the names of anyone's private items.

How the encryption works

The short version. Full detail on the security page.

1
Every item gets its own key

The moment you save something, it's encrypted with AES-256-GCM under a random, single-use data key — one key per item, never one key for everything.
2
That key is wrapped, not stored raw

The data key is itself encrypted by a master key that lives only in our hosting provider's runtime config, never in the database. A leaked backup or database breach yields ciphertext and nothing else.
3
Sharing scope decides who can unlock it

Private, one person, one team, or the whole org — set per item. A missing or invalid scope fails closed, not open.
4
Quick share links go further

Those are genuinely end-to-end encrypted: the key is generated in your browser and travels in the URL fragment, after the #, which browsers never send to a server. We can't decrypt those even if we wanted to.

No account needed.