Independent by design. Apple at heart.

Your secrets.
Your devices.
Your choice.

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

2ndPass: a titanium vault door on an indigo app icon
your next workflow
# References in your project. Secrets in your vault.
$ sp run --env-file app.env -- npm run dev

# Same vault. Native app. Your iCloud.
Native apps & AutoFillSecure Enclave device keysYour iCloud for syncSource inspection & security review

One vault. Both sides of your day.

From signing in
to shipping code.

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.

01 / EVERYDAY ACCESS

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 ↗
02 / DEVELOPER WORKFLOWS

Secrets, ready to run.

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 ↗
03 / YOUR INFRASTRUCTURE

Bring your own iCloud.

Encrypted vaults travel through CloudKit. There’s no 2ndPass account or separate sync server to operate.

Understand the boundary ↗
04 / A PRACTICAL MOVE

Bring your passwords with you.

Restore transferable contents from a portable archive with its separate key. General password-manager document import remains planned.

Plan your move ↗
05 / MORE THAN LOGINS

A place for the other secrets.

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 ↗
06 / DEVICE-LOCAL KEYS

Private keys that stay put.

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

Meet sp.
Your vault in Terminal.

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.

Explore CLI workflows ↗
app.env
APP_ENV=development
PGUSER=sp://${APP_ENV}/db/user
PGPASSWORD=sp://${APP_ENV}/db/password
Terminal
$ sp run --env-file app.env -- npm run dev
Resolve first. Launch only when every lookup succeeds.

Protection with a clear explanation

Synced through the cloud.
Rooted in your hardware.

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 ↗
1

Your device

Authenticate to use hardware-bound private keys.

2

Encrypted vault

Per-item keys for separately encrypted fields.

3

Your iCloud

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

Built out of
a decision to leave.

“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 ↗