Docs

FAQ

Answers to the questions we hear most.

Is Caddi free?

Yes, for a single person. The solo product is free, no pricing to configure or read through. Teams (shared workspaces, multiple members) are coming soon; there’s no pricing to announce for that yet either.

What happens if I lose my device?

Use your recovery code: run caddi login --recovery on a new device and paste it in to restore vault access. It’s shown to you exactly once, right after your vault is first created (and again after any caddi vault rotate), so store it somewhere safe, like a password manager, the moment you see it. If you lose every approved device and don’t have the recovery code, the vault private key is unrecoverable and the secrets sealed to it don’t come back; your account itself isn’t lost, and you can reconnect your services and keep going. See security model for the full mechanics.

Can Caddi read my keys?

No. Every API key and OAuth token you connect is sealed to your vault’s public key before it ever leaves the device you typed it into (client-side, in your browser, or on your machine from the CLI), and the server stores only that ciphertext. The vault private key needed to decrypt it never exists on Caddi’s servers at all; it lives only in your approved devices’ OS keychains. See security model for exactly which primitives do this and what the honest limits are.

Do you support OAuth providers?

Not yet. Providers that only offer OAuth (Gmail, Google Drive, Google Calendar, Canva) are listed in the catalog for completeness, but connecting them is coming soon. Every provider connectable today works by pasting a token you generate on that provider’s own site, which is a deliberate current tradeoff: it costs one extra copy-paste step in exchange for Caddi’s servers never being in the token-exchange path at all.

Can I self-host Caddi?

Not today, and we want to be upfront about that rather than imply otherwise. The plan is for the CLI and vault packages to go source-open, so you can read and audit exactly how the crypto works and, eventually, run the client side yourself. That hasn’t shipped yet; this page will be updated the moment it does.

What’s the npm package?

The CLI is published as @caddi/cli. Install it globally with npm i -g @caddi/cli; see getting started for the full setup flow.