FerrVault stores your secrets, versions them, and hands them to the things that need them: a Kubernetes cluster or a developer's shell. It is a hosted service, and every secret is encrypted before it reaches the database, under a key you choose.

The app stays short on purpose. A dialog tells you what to do next and links here for the manifests, the flags and the failure cases.

Where to start

• Vaults and environments: how secrets are organised, versioned and shared with your team.
• Tokens: the service-account tokens a machine uses to read a vault without anyone signing in.
• Kubernetes operator: sync a vault into native Kubernetes Secrets.
• CLI: read secrets from a shell, or inject them into a process.
• Keys: the encryption keys behind your vaults, and how to generate, share and rotate them.