Loading page
Loading page
Security · 1Password Secrets Automation alternative
A small secrets vault for teams. Values are decrypted only on your server, reveals need a passkey, and every read is logged.
kuukura is a self-hosted vault for team secrets. It is one small server with one database and a few concepts: tags, grants and people. You store API keys and passwords in it, and people and machines see only the secrets they are granted.
Secrets are encrypted with a new key for each version, and that key is wrapped by a master key that never lives in the database. The server decrypts values only when an allowed request comes in. Sensitive actions, like revealing a value, open a confirmation page that needs your passkey or authenticator app.
The README targets one organization with five to fifty people that signs in with Google and uses CI and local development. It suits teams that want order in their secrets without the work of a heavy vault.
The whole point of kuukura is that you run it and you hold the keys. No outside service can read your secrets, and the audit log records every decision in a chain you can check.
Be honest about the limits. The project has a single maintainer. It needs a Google OAuth client to work. It has no dynamic secrets or SAML yet. Losing the master key means losing access to your secrets, so store it safely and back up the database. For production, pin a release tag instead of the latest image.
Containers: ghcr.io/victorlunam/kuukura:2026.10.13
Step 1
Choose the Starter plan. It costs $20 a month and runs up to 3 apps.
Step 2
Open App templates in the dashboard, choose kuukura, and click Deploy. We set up the containers, secrets and domain.
Step 3
Wait a few minutes for the first deploy, then open your new URL and finish the kuukura setup screen.