Cloakspire

Pricing

Pay once. Not a subscription.

Start free with a single project. Unlock everything else whenever you're ready - no recurring charge, ever.

Free

Everything you need to stop keeping secrets in .env files.

$0forever
Download free
  • 1 project, unlimited environments & variables
  • Full Personal Vault (logins, cards, notes, SSH keys)
  • .env import/export & clipboard import
  • Command palette & keyboard shortcuts
  • Manual backup & restore
Most popular

Pro

Unlimited projects and every developer workflow, unlocked once.

$39one-time · not a subscription
Get Pro
  • Unlimited projects
  • Snapshots with diff & restore
  • Servers & VPS + live SSH terminal
  • Service Credentials vault
  • Project Scanner + .env.example generation
  • Vercel & GitHub Actions sync
  • CLI companion
  • Automatic rotating backups

Pro is a one-time unlock - pay once and it's yours forever on this major version. A future major version may offer an optional paid upgrade, the same way Sublime Text and Tower do it. Never a recurring charge for what you already own.

How it compares

Why not just use Bitwarden or Doppler?

Every one of them is excellent at part of this job. Cloakspire is the only one built to do all of it, fully offline.

CapabilityCloakspireBitwarden1PasswordDopplerInfisical
Fully offline, no account required
partial
One-time purchase available
Dev-native project / environment vault
partial
General password manager (logins, cards, notes)
Live SSH terminal built in
CLI: inject secrets, never write .env
partial
partial
Snapshots with diff and restore
partial
partial
Detects your stack (Docker, CI, Prisma) and suggests typo fixes
Vercel / GitHub Actions sync
Zero infrastructure to run or trust
partial

Based on each product's publicly documented model as of this writing. Feature sets and pricing change - please verify against each vendor's current site.

What about teams?

Work offline locally, sync through CI - no team cloud required

Cloakspire is offline-first by design: there's no central server to trust, breach, or pay for per seat. For a small team, that's not a gap - it's the pitch.

Today, sharing a project between teammates means passing the vault file directly, or using the Pro Vercel / GitHub Actions sync as the hand-off point - push from your machine, teammates (and CI) pull from there. Native multi-user sync isn't built yet, and we'd rather say that plainly than pretend otherwise.

# Everyone on the team works offline, locally
> evx run acme-app/production -- npm run start
 
# Ship the environment through CI, not through Slack DMs
> evx export acme-app/production --template > .env.example
  synced to GitHub Actions secrets on push

FAQ

Questions, answered plainly