Your secrets. Your machine. Your control.
Securely manage development credentials across projects, environments, terminals and AI coding agents, all from one private macOS vault.
One-time payment. No subscription, no account, no cloud vault.
$ aback-vault secrets list --project acme-api --env development
Project: acme-api
Environment: development
DATABASE_URL Configured
OPENAI_API_KEY Configured
SESSION_SECRET Configured
$ aback-vault run --project acme-api --env development -- bun run devWhy Aback Vault
One vault instead of a dozen .env files
Credentials end up copied between dashboards, terminals, chat windows and AI agents, with a plaintext .env file in every project folder. Aback Vault keeps them encrypted in one place on your Mac and hands them to the program that needs them, when you say so.
- 1
Create a project
Link it to a folder so the CLI knows which project you are in.
- 2
Organise environments
Development, staging and production to start, plus any you add.
- 3
Add or import secrets
Type them in, or import an existing .env file after a preview.
- 4
Connect your AI agent
Set up Claude Code, Codex or Cursor from the app.
- 5
Run your workflow
aback-vault run starts your program with the right variables.
Projects and environments
Every project's secrets, organised the way you work
Projects linked to folders
Associate a project with its directory. Commands run inside that folder pick the project on their own, and you can always name another.
Environments per project
Each project starts with development, staging and production. Add custom environments whenever you need them.
Compare environments
See which variables exist in both, which are missing from one, and which differ, without revealing any value.
.env import and export
Imports show a preview of new, replaced and unchanged names first. Exports warn that the file holds plaintext and are readable only by you.
Search, reveal and copy
Search names, descriptions and tags without decrypting values. Copied values are cleared from the clipboard after a delay you choose, unless you copied something else since.
Encrypted backups
Create an encrypted backup file and restore it on this or another Mac with your master password or recovery key.
Command line
Run any program with the right variables
aback-vault run starts your program with an environment's variables in its process environment. No intermediate .env file is written and no value is passed as a command-line argument.
$ aback-vault validate --project acme-api --env staging --from .env.example
Project: acme-api
Environment: staging
DATABASE_URL Configured
OPENAI_API_KEY Configured
SESSION_SECRET Missing
1 required variable(s) are missing.Safe by default. Listing commands show names and whether each is configured. A value is printed only when you ask for one by name.
Approvals stay in the app. While the app is open, the CLI asks it for access. Running with a development environment is approved once per unlocked session; production is approved every time.
Honest limits. A program that receives variables can read them, and so can programs it starts. Use the narrowest environment that works.
AI coding agents
A local MCP server, with you in charge of every run
Aback Vault includes a Model Context Protocol server that your AI client starts on your Mac over standard input and output. There is no hosted server and no Aback account. Agents see names and metadata; values reach only the commands you approve.
Tools the agent can call
list_projectsProject names and descriptions.
list_environmentsThe environments of a project.
list_secret_metadataVariable names and descriptions, never values.
validate_environmentWhich required variables are configured, empty or missing.
get_access_policyWhat needs your approval before it runs.
run_with_environmentRuns a command with an environment's variables, after you approve it in the app.
{
"mcpServers": {
"aback-vault": {
"command": "/Applications/Aback Vault.app/Contents/MacOS/aback-vault",
"args": ["mcp"]
}
}
}When an agent asks to run a command, the app shows the exact command, folder and environment and waits for you. A command can be approved once, or for the rest of the unlocked session if it uses a non-production environment. Locking the vault forgets every session approval.
Claude Code
Connection tested- For all your projects
- Added with claude mcp add-json at user scope
- For one project
- .mcp.json in the project folder
The app shows the change before it writes it, keeps every other server in the file, and saves a backup copy first.
OpenAI Codex
- For all your projects
- ~/.codex/config.toml
- For one project
- .codex/config.toml in a trusted project
The app shows the change before it writes it, keeps every other server in the file, and saves a backup copy first.
Cursor
- For all your projects
- ~/.cursor/mcp.json
- For one project
- .cursor/mcp.json in the project folder
The app shows the change before it writes it, keeps every other server in the file, and saves a backup copy first.
Security and privacy
Encrypted on your Mac, and only on your Mac
Your vault is a local database. Secret values, encryption keys and vault contents are never sent to Aback, to Cloudflare or to Dodo Payments.
Authenticated encryption
Every secret value, and separately its name and description, is sealed with XChaCha20-Poly1305 under a random vault key. Search reads names and descriptions only and never decrypts a value.
A memory-hard master password
The vault key is wrapped with a key derived from your master password with Argon2id. The password itself is never stored.
Recovery key
An optional 256-bit recovery key can unlock the vault and reset the master password if you forget it.
Touch ID
Unlock with Touch ID. The unlock key is protected by your Mac's Secure Enclave and stops working if your fingerprints change. Your master password always works as well.
Automatic locking
The vault locks after the inactivity period you set, when your Mac sleeps or its screen locks, and when you quit.
Offline by design
Unlocking, the CLI and the MCP server work without a network connection. A licence problem never locks you out of your own data.
What does leave your Mac: buying a licence goes through Dodo Payments, and activating it sends your licence key, a random device identifier and the app version to our licence server on Cloudflare. Aback Vault has not been independently audited yet, and no software can protect secrets on a Mac that is already compromised.
Lifetime pricing
Pay once. The price rises every ten licences.
The first ten licences cost $5 and the next ten $9. After that, each group of ten costs $5 more than the one before. The price you see is the price you pay, and it is set by our server from completed sales.
Aback Vault Lifetime
$5
USD. One-time payment. Lifetime licence.
- Left at $5
- 10
- Next price
- $9
- The desktop app, the CLI and the local MCP server
- Setup for Claude Code, OpenAI Codex and Cursor
- Use on up to 2 of your Macs
- No subscription and no account
Purchases are not open yet.
What counts as a sale. Only a payment that Dodo Payments confirms to our server. Abandoned and failed checkouts do not count.
Holding your price. Starting checkout holds a licence at the current price for 30 minutes while you pay.
Refunds. A refunded licence stops being active, and prices are not lowered again. See the refund policy.
Paying. Prices are in US dollars. Depending on where you are, the checkout can offer to charge you in your own currency, converted by Dodo Payments, which can add a conversion fee; you can pay in US dollars instead. Pay with any method the checkout offers you.
Taxes. Sales tax or VAT, where it applies, is added at checkout by Dodo Payments, the merchant of record.
FAQ
Questions developers ask
Keep every project's secrets in one private vault
A lifetime licence for the app, the CLI and the local MCP server.