Start from the job your team needs done
Crunu is one product with one rule: values are encrypted on your devices, and the server keeps only ciphertext. Different teams lean on different parts of it. Pick the page closest to yours.
Five teams, five jobs
Each page starts from one team's job, shows which parts of Crunu cover it, and says plainly what Crunu doesn't do for that team.
5 team pages
Startups
Founders and first engineers of product teams of 5 to 50 people who share .env files today.
Agencies and contractors
Agencies and contracting teams that hold several clients' cloud, payment and database keys.
Platform teams
DevOps and platform engineers who deliver secrets to Linux servers and CI pipelines.
Security leads
CTOs and security leads who answer for where secrets live and who could read them.
Solo developers
Individual developers with cloud credentials, dotfiles and side projects across several machines.
The same vault underneath
Whichever page you start from, the rules below are the same for every team.
Encryption on your devices
Values are encrypted in the browser and in the
crunuagent. The server has no key that decrypts them.A key per environment
Access to development never opens production, because the production key is sealed only to the people and machines granted it.
Signed changes
Who can read an environment, and every saved version, is signed, so the server can't add itself as a reader or swap data.
History and an audit log
The last 100 versions of each environment, and an organization log you can verify and export.
Every feature, free during early access
There's no payment step. See pricing for the limits.
Not in Crunu todayNo single sign-on or SCIM, no Windows agent, no mobile apps, no Kubernetes operator or Terraform provider, no built-in sync into cloud secret stores, and no end date on a person's access. What Crunu doesn't do
Set up the first project for your team
Create your organization at app.crunu.com. Free during early access.