Part of the API Studio: Complete Tutorial Series, 46 short videos covering every feature.
SECRET VAULT
Overview
A built-in AES-256-GCM encrypted vault for storing secrets (API keys, passwords, tokens) and TLS certificates. No external services needed — fully offline.
Creating the Vault
Set up a new encrypted vault in a few steps:
- Open the Vault tab
- Click 'Create Vault'
- Enter a master password (used to derive the encryption key)
- Confirm the password
- Click 'Create Vault'
~/.openpost/global/vault.enc (encrypted file)⚠️ Important: If you forget your master password, vault contents cannot be recovered. This is by design — there is no backdoor.
Unlocking
Unlock your vault to access secrets and certificates:
- Open the Vault tab
- Enter your master password
- Click 'Unlock'
{{variable}} resolution while unlockedLocking
Lock the vault to clear secrets from memory:
Changing Password
Change your vault's master password (vault must be unlocked):
- Click 'Change Password'
- Enter your current password
- Enter the new password
Keep Unlocked (OS Keychain)
Optional convenience toggle to avoid entering your password every session:
| Platform | Keychain Backend |
|---|---|
| macOS | macOS Keychain |
| Windows | Windows Credential Store |
| Linux | Linux Secret Service |
Storage & Encryption
Technical details of how the vault is stored and encrypted:
| Property | Value |
|---|---|
| File | ~/.openpost/global/vault.enc |
| Algorithm | AES-256-GCM |
| Key derivation | PBKDF2 with SHA-512, random 32-byte salt, 100,000 iterations |
| File format | JSON with salt, iv, authTag, ciphertext (all Base64) |
| Decrypted payload | { secrets: Record<string,string>, certificates: CertificateEntry[] } |
~/.openpost/global/ (your home directory), not inside workspace folders. It's safe to exist alongside git repos — encrypted contents are never committed.