Ente Auth vs Clave

Ente's Authenticator app helps you generate and store 2 step verification (2FA) tokens on your mobile devices. FEATURES SECURE BACKUPS Auth provides end-to-end encrypted cloud backups so that you don't have to worry about losing your tokens. We use the same protocols Ente Photos uses to encrypt and preserve your data. MULTI DEVICE SYNC Auth will automatically sync the 2FA tokens you add to your account, across all your devices on mobile & desktop. Every new device you sign into will have access to these tokens. WEB ACCESS You can access your 2FA tokens on any device by using https://auth.ente.io. OFFLINE MODE Auth generates 2FA tokens offline, so your network connectivity will not get in the way of your workflow. IMPORT AND EXPORT You can add tokens to ente by one of the following methods: - Scanning a QR code - Manually entering (copy-pasting) a 2FA secret - Bulk importing from a file that contains a list of codes in the following format: otpauth://totp/provider.com:you@email.com?secret=YOUR_SECRET The codes maybe separated by new lines or commas. You can also export the codes you have added to ente, to an unencrypted text file, that adheres to the above format. TERMS https://ente.io/terms

Your Nostr identity is one key. Lose it or leak it and there's no reset — no password recovery, no support line. Yet the usual way to use Nostr is to paste that key into every app you try. Clave ends that. Your key is created and stored in your iPhone's Keychain, and it stays there. When an app needs something signed — a post, a reaction, a profile update — it asks Clave. You approve, Clave signs, and the app gets a signature. The key itself never leaves your phone. Think of it as a notary in your pocket: apps bring things to be stamped, you decide what gets stamped, and nobody ever borrows the stamp. WHAT YOU GET - One key, one place. Pair every Nostr app to Clave instead of spreading copies of your key around. - You're in control. Set each app to full, medium, or low trust. Sensitive actions — profile changes, contact lists, deletions — always ask first. - See everything. A running activity log shows every signature, with one-tap unpair for any app. - More than one identity? Hold several accounts and sign in with all of them in a single pairing flow. Each key stays separate. - Works in the background. Clave can sign even when it's closed — no need to keep it open. BUILT ON AN OPEN STANDARD Clave is a NIP-46 remote signer. NIP-46 is the open Nostr standard for letting apps request signatures from a separate signer instead of holding your key. Any client that supports it can pair with Clave. FOR THE CURIOUS Requests reach your phone through an end-to-end encrypted relay. A lightweight push notification — with no readable content — wakes a small part of Clave for a few seconds to decrypt the request, check the rules you set, sign with the key in your Keychain, and send back an encrypted response. The relay and proxy can see that a request arrived, never what's in it, and they can never sign on your behalf. OPEN SOURCE Clave is MIT-licensed and the entire signing path is public: github.com/DocNR/clave. It has had an internal security review; an independent third-party audit is on the roadmap. Don't want to use our proxy? Point Clave at your own in Settings and run the whole stack yourself. GOOD TO KNOW Clave holds your real Nostr key — treat it like any app you'd trust with your nsec. The win is one place that holds your key instead of the many copies you create by pasting it everywhere. New to it? Pairing a fresh key first is a fine way to try it.