At home on your devices.
Native Mac, iPhone, and iPad interfaces. Fill passwords and verification codes, and sign in with cloud or device-local passkeys through Apple’s AutoFill system.
Set up AutoFill ↗Independent by design. Apple at heart.
A native password manager with a developer’s soul. Keep passwords and passkeys in iCloud, or create local keys that stay in your device’s Secure Enclave. Put secrets to work with sp, the Mac CLI for scripts, SSH, and Git signing.
macOS 15+ · iOS & iPadOS 18+ · All rights reserved
# References in your project. Secrets in your vault.
$ sp run --env-file app.env -- npm run dev
# Same vault. Native app. Your iCloud.One vault. Both sides of your day.
The password you need in Safari. The token your script needs in Terminal. 2ndPass brings them into one native application, without a separate password-manager service.
Native Mac, iPhone, and iPad interfaces. Fill passwords and verification codes, and sign in with cloud or device-local passkeys through Apple’s AutoFill system.
Set up AutoFill ↗The separately installed Mac CLI, sp, reads secrets, fills configuration templates, runs tools with credentials, and serves SSH and Git signing keys.
Meet the CLI ↗Encrypted vaults travel through CloudKit. There’s no 2ndPass account or separate sync server to operate.
Understand the boundary ↗Restore transferable contents from a portable archive with its separate key. General password-manager document import remains planned.
Plan your move ↗Store passwords, API tokens, passkeys, SSH/Git keys, notes, cards, and attachments in cloud vaults. Choose device-local Secure Enclave identities when keys must stay on one device.
Compare vault capabilities ↗Create local passkeys, SSH keys, Git signing keys, and certificate identities inside your device’s Secure Enclave. Their private keys never leave that device. Register an independent credential on another device: local keys cannot be synced, exported, or recovered.
Choose where your keys live ↗Built to replace a real workflow
2ndPass began with a developer who wanted to leave 1Password but still needed the everyday utility of op. Use read, run, and inject to supply secrets to scripts and development tools. Use the SSH agent to authenticate to servers and sign Git commits with selected cloud or device-local keys.
APP_ENV=development
PGUSER=sp://${APP_ENV}/db/user
PGPASSWORD=sp://${APP_ENV}/db/password$ sp run --env-file app.env -- npm run devProtection with a clear explanation
Each enrolled device has its own Secure Enclave keys. Your secrets are encrypted before they reach iCloud, and signed updates help detect unauthorized changes.
The Mac app is sandboxed; the separately installed CLI supports developer workflows outside App Sandbox. Hardware protects device keys; passwords and cloud credential keys enter authorized process memory during use. Keep a portable archive and its separate key for independent restoration. Account recovery is unavailable. Local Secure Enclave identities cannot be recovered.
Read the security model ↗Authenticate to use hardware-bound private keys.
Per-item keys for separately encrypted fields.
Store and sync ciphertext to enrolled devices.
Your Apple Account is also part of device enrollment and must be protected.
A second pass at passwords
“I needed a replacement for op. So I built one.”The starting point for 2ndPass.
A values-driven decision became a practical tool. Read why the project exists, what it aims to do, and what it doesn’t promise.
Read the origin story ↗