I mean I get their explanation, sorta: <a href="https://1password.community/discussion/129160/it-s-time-to-say-goodbye-to-standalone-licenses/p1" rel="nofollow">https://1password.community/discussion/129160/it-s-time-to-s...</a><p>However, I like my data local because: <a href="https://blog.1password.com/update-on-our-recent-service-disruption/" rel="nofollow">https://blog.1password.com/update-on-our-recent-service-disr...</a><p>This was a "small" disruption but with a local file I have more confidence I can avoid disruptions. /wave 1password and hello bitwarden (though I'll be looking at enpass as mentioned in the first comment)
When this first hit the news I started planning my migration. I settled on Enpass <a href="https://www.enpass.io/" rel="nofollow">https://www.enpass.io/</a> . The main client is closed source but the password file is an encrypted SQLite database and is readable by open source tools (written in Go <a href="https://github.com/hazcod/enpass-cli" rel="nofollow">https://github.com/hazcod/enpass-cli</a>).<p>The UI isn't <i>quite</i> as polished as 1Password but it's pretty good, and more consistent/discoverable IMHO.
Why not just use the iCloud one built into iOS/macOS. I know it’s not a single pass key for all your passwords, buts it’s already baked in and works well.