Keys is a vault for the credentials you collect while shipping software. API keys, SSH keys, OAuth tokens, certificates, connection strings. The ones that end up in .env files, scratch notes, and screenshots because no password manager was really built for them.
Keys isn't a reinvention. It just wants to be the password vault you'd actually trust with the keys to production.
We don't keep a copy. We can't restore your vault if you lose your passphrase, and there's no version of "ask nicely" that gets us in. That's on purpose.
Your passphrase is the only thing that can decrypt your vault. Any "recovery service" we offered would have to break that, so we don't offer one. What we do is generate a one-time recovery code at setup. Print it, put it somewhere you'd find again in a year. That's the safety net.
1Password is great for households. Passwords, two-factor codes, family sharing, the works. iCloud Keychain is great for the websites you log into in Safari. Keys is for the rest. The credentials that show up when you actually build things: API keys, SSH keys, OAuth tokens, server creds, the .env files that quietly grow over time. It speaks that vocabulary natively.
As little as possible, by design. Keys ships as a standard App Store app, sandboxed, with no analytics or telemetry baked in and no Abokado Labs server in the picture. Your data lives on your devices and in your iCloud, encrypted with a key only you have. The privacy policy walks through every data flow.
You can export an encrypted backup any time. The format is documented, and the secrets stay readable as long as you have the passphrase, whether or not Keys is still in the App Store.
No, and no plans for one. Keys is built on iCloud sync, the Secure Enclave, and the macOS / iOS sandbox. Bringing the same guarantees to Android would mean rebuilding the trust model from scratch on different primitives. That's a different product, and we'd rather build this one well.