Secrets, passwords, team access
Vaultix
The encrypted workspace between your team and everything it ships.
Keep runtime secrets and shared credentials together. Your keys are created on your device; Vaultix only stores encrypted data.
payments-api
12 encrypted secrets · 4 members
DATABASE_URL
••••••••••••••••••••
STRIPE_SECRET_KEY
••••••••••••••••••••
RESEND_API_KEY
••••••••••••••••••••
Encryption
XChaCha20-Poly1305
Key exchange
Public-key cryptography
Plaintext storage
Never
CLI
macOS · Linux · Windows
One encrypted workspace
Built around how a team actually works.
Vaultix is not another dashboard that asks you to move work into it. It sits between your team, the terminal, and the browser.
Secrets that follow the project
Organize environment variables by vault and stage. Inject them at runtime without leaving a plaintext .env file behind.
Passwords that stay with the team
Store credentials, one-time codes, and notes in the same encrypted workspace. Share access without sharing the master password.
Access you can explain
Owners, moderators, and members get explicit permissions. Remove a teammate once and their encrypted access is revoked.
Security model
The server can store it. It cannot read it.
Encryption and decryption happen on your device. Every vault gets its own key, then that key is sealed separately for each authorized member.
Keys begin locally
Your identity keys are generated in the client and protected by your credentials.
Data leaves encrypted
Secrets are encrypted before they cross the network or reach persistent storage.
Access is individually sealed
Sharing grants a recipient an encrypted key, never a copy of the plaintext secret.
Secrets arrive with the command.
Authenticate once, choose a vault, and run any process with its secrets injected into memory.
$curl -fsSL https://vaultix.dev/install.sh | sh
Resolving latest release...
Installing vaultix to your PATH...
Vaultix CLI installed
$vaultix run -- npm run dev