Install
brew install ente-cli
vs Google Authenticator
vs Microsoft Authenticator
vs Authy
vs 1Password
vs Bitwarden
vs Proton Pass
vs 2FASTry itExperimental
See what an agent can do with Ente Auth before you ever sign up. Pick a story: recorded sessions replay real probe-harness transcripts; sandboxed self-drive sessions are designed and gated (docs/TRY-IT.md).
$brew info --json=v2 ente-cli | grep descrecorded session — replayed, not liveVerified integrations
No integration evidence found in our corpus for this product yet — that means none was found, never that it doesn’t integrate.
By theme — the product's score on each story themeBy theme
Agenticness — how well agents can access and operate the productAgenticnessevidence →
How well agents can access and operate the product
Automation depth — how much of the product can run unattendedAutomation depthevidence →
How much of the product can run unattended
Openness — open source, data portability, and self-hosting storiesOpennessevidence →
Open source, data portability, and self-hosting stories
Passkey support — passkeys in the vault — storage, sign-in, cross-ecosystem syncPasskey supportevidence →
Passkeys in the vault — storage, sign-in, cross-ecosystem sync
Portability — your secrets stay yours — open export, bulk import, device migrationPortabilityevidence →
Your secrets stay yours — open export, bulk import, device migration
Privacy posture — data-handling and privacy storiesPrivacy postureevidence →
Data-handling and privacy stories
Security posture — how it protects itself — app lock, E2EE design, audits, breach alertingSecurity postureevidence →
How it protects itself — app lock, E2EE design, audits, breach alerting
Self hosting — running it yourself — self-hosted servers, open-source clientsSelf hostingevidence →
Running it yourself — self-hosted servers, open-source clients
Surfaces — where it meets your workflow — IDE, CLI, web, PR comments, CI checksSurfacesevidence →
Where it meets your workflow — IDE, CLI, web, PR comments, CI checks
Sync backup — not losing your accounts — encrypted backup, multi-device sync, recoverySync backupevidence →
Not losing your accounts — encrypted backup, multi-device sync, recovery
Team admin — shared and managed use — shared vaults, org policies, programmatic provisioningTeam adminevidence →
Shared and managed use — shared vaults, org policies, programmatic provisioning
Totp core — the TOTP fundamentals — QR enrollment, organization, offline codes, non-standard tokensTotp coreevidence →
The TOTP fundamentals — QR enrollment, organization, offline codes, non-standard tokens
Story verdicts — every judged story with its evidenceStory verdicts
Follow the green: where the map greys out is where Ente Auth stops today. ✓ full · ~ partial · ! disputed · — none · n/a not applicable.
Agenticness — how well agents can access and operate the productAgenticness
How well agents can access and operate the product
API surface
Drive the product through a documented public API
~3/10
unlocks → Official SDKs · Scoped API keys · MCP server · Machine-readable spec · Versioning policy · API/UI parity · Full data export
Subscribe to events via webhooks
n/an/a
Build against official SDKs
—–
Issue scoped/least-privilege API credentials for an agent
—–
Connect an agent via an official MCP server
—–
Download a machine-readable API spec (OpenAPI or equivalent)
—0/10
Rely on versioned APIs with a documented deprecation policy
—0/10
Test against a sandbox environment without touching production data
n/an/a
Explore an interactive API reference with runnable examples
—0/10
Docs for agents
Point an agent at llms.txt or agent-oriented docs
✓7/10
Agentic features
Delegate tasks to a built-in AI assistant inside the product
n/an/a
Operate the product with natural-language commands
—–
Plug MCP servers into this product so it can use their tools
n/an/a
Get AI-generated insights and suggestions from my data inside the product
n/an/a
Set up automations that run autonomously in the background
—–
Automation depth — how much of the product can run unattendedAutomation depth
How much of the product can run unattended
Openness — open source, data portability, and self-hosting storiesOpenness
Open source, data portability, and self-hosting stories
Passkey support — passkeys in the vault — storage, sign-in, cross-ecosystem syncPasskey support
Passkeys in the vault — storage, sign-in, cross-ecosystem sync
Portability — your secrets stay yours — open export, bulk import, device migrationPortability
Your secrets stay yours — open export, bulk import, device migration
Privacy posture — data-handling and privacy storiesPrivacy posture
Data-handling and privacy stories
Security posture — how it protects itself — app lock, E2EE design, audits, breach alertingSecurity posture
How it protects itself — app lock, E2EE design, audits, breach alerting
The app itself locks behind biometrics or a PIN, so a borrowed phone doesn't expose my codes
✓8/10
The vendor publishes independent security audits of the app and its sync protocol
—–
The app warns me when a service I use is breached or a stored credential is weak, reused, or exposed
—–
Push-based sign-in includes phishing defenses — number matching, location context, and admin-enforced MFA policies
—–
Self hosting — running it yourself — self-hosted servers, open-source clientsSelf hosting
Running it yourself — self-hosted servers, open-source clients
Surfaces — where it meets your workflow — IDE, CLI, web, PR comments, CI checksSurfaces
Where it meets your workflow — IDE, CLI, web, PR comments, CI checks
Sync backup — not losing your accounts — encrypted backup, multi-device sync, recoverySync backup
Not losing your accounts — encrypted backup, multi-device sync, recovery
Backups are end-to-end encrypted with a key the vendor never holds, and the encryption design is documented
~6/10
My tokens are available on my phone, tablet, and computer at the same time, kept in sync automatically
✓8/10
Losing my phone doesn't lose my accounts — a documented recovery path restores my tokens on a new device
✓8/10
Team admin — shared and managed use — shared vaults, org policies, programmatic provisioningTeam admin
Shared and managed use — shared vaults, org policies, programmatic provisioning
An agent can create and update vault entries — seeding new TOTP secrets, storing credentials — through documented programmatic surfaces
—0/10
Enforce org-wide policies — require app lock, restrict export, mandate strong master credentials — across every member's app
—0/10
My team can share TOTP-protected logins through shared vaults or collections with per-member access control
~4/10
Totp core — the TOTP fundamentals — QR enrollment, organization, offline codes, non-standard tokensTotp core
The TOTP fundamentals — QR enrollment, organization, offline codes, non-standard tokens
Scan a QR code and immediately start generating TOTP codes for a new account
✓8/10
Codes generate fully offline — no network, no vendor account required just to see my TOTP codes
✓8/10
Keep dozens of tokens organized — search, folders or groups, and service icons — so the right code is always two taps away
~6/10
Non-standard tokens work too — Steam Guard, HOTP counters, custom periods and digit lengths
~4/10
Sorted by importance (agentic first) (high → low) · 55/55 stories · click a row’s chevron for the rationale and evidence
Drive the product through a documented public API G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | partial | 3/10 | Tprobed | |
Connect an agent via an official MCP server G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | none | untested | none yet | |
Delegate tasks to a built-in AI assistant inside the product G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | n/a | untested | none yet | |
Plug MCP servers into this product so it can use their tools G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | n/a | untested | none yet | |
Point an agent at llms.txt or agent-oriented docs G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 7/10 | Tprobed | |
Use an official CLI G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 6/10 | Tprobed | |
Run the product headlessly / in CI for automation G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 3/10 | Tprobed | |
Download a machine-readable API spec (OpenAPI or equivalent) G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Explore an interactive API reference with runnable examples G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Rely on versioned APIs with a documented deprecation policy G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Build against official SDKs G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | untested | none yet | |
Get AI-generated insights and suggestions from my data inside the product G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | n/a | untested | none yet | |
Issue scoped/least-privilege API credentials for an agent G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | untested | none yet | |
Operate the product with natural-language commands G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | untested | none yet | |
Set up automations that run autonomously in the background G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | untested | none yet | |
Subscribe to events via webhooks G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | n/a | untested | none yet | |
Test against a sandbox environment without touching production data G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 1 | n/a | untested | none yet | |
Losing my phone doesn't lose my accounts — a documented recovery path restores my tokens on a new device Recovery | everyday user | Sync backup — not losing your accounts — encrypted backup, multi-device sync, recoverySync backup | 3 | full | 8/10 | Tprobed | |
Scan a QR code and immediately start generating TOTP codes for a new account Enrollment | everyday user | Totp core — the TOTP fundamentals — QR enrollment, organization, offline codes, non-standard tokensTotp core | 3 | full | 8/10 | Cclaimed | |
Self-host the core product G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 3 | full | 8/10 | Tprobed | |
Backups are end-to-end encrypted with a key the vendor never holds, and the encryption design is documented Backup | security engineer | Sync backup — not losing your accounts — encrypted backup, multi-device sync, recoverySync backup | 3 | partial | 6/10 | Tprobed | |
Export all of my data in open formats and leave G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 3 | disputed | 5/10 | Dcontradicted | |
Prevent my data from being used to train AI models G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 3 | partial | 5/10 | Tprobed | |
Export all my TOTP secrets in an open, readable format and leave for another app whenever I choose — no lock-in Export | power user | Portability — your secrets stay yours — open export, bulk import, device migrationPortability | 3 | disputed | 4/10 | Dcontradicted | |
Define rules that trigger actions automatically on events G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 3 | n/a | untested | none yet | |
The app stores passkeys and signs me into websites and apps with them, not just TOTP codes Storage | everyday user | Passkey support — passkeys in the vault — storage, sign-in, cross-ecosystem syncPasskey support | 3 | none | untested | none yet | |
Import tokens in bulk from other authenticator apps instead of re-enrolling every account by hand Import | power user | Portability — your secrets stay yours — open export, bulk import, device migrationPortability | 2 | full | 9/10 | Xcommunity | |
Codes generate fully offline — no network, no vendor account required just to see my TOTP codes Offline | power user | Totp core — the TOTP fundamentals — QR enrollment, organization, offline codes, non-standard tokensTotp core | 2 | full | 8/10 | Cclaimed | |
My tokens are available on my phone, tablet, and computer at the same time, kept in sync automatically Multi device | everyday user | Sync backup — not losing your accounts — encrypted backup, multi-device sync, recoverySync backup | 2 | full | 8/10 | Xcommunity | |
The app itself locks behind biometrics or a PIN, so a borrowed phone doesn't expose my codes App lock | everyday user | Security posture — how it protects itself — app lock, E2EE design, audits, breach alertingSecurity posture | 2 | full | 8/10 | Cclaimed | |
A first-class desktop app gives me codes and vault access on my computer, not just on mobile Desktop | power user | Surfaces — where it meets your workflow — IDE, CLI, web, PR comments, CI checksSurfaces | 2 | full | 7/10 | Xcommunity | |
Control data retention and deletion G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | partial | 7/10 | Tprobed | |
Moving to a new phone transfers all my tokens in one guided step Migration | everyday user | Portability — your secrets stay yours — open export, bulk import, device migrationPortability | 2 | full | 7/10 | Tprobed | |
Read the product's source under an open license G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 2 | full | 7/10 | Tprobed | |
The client apps are open source, so the code handling my seeds can be inspected and community-reviewed Source | security engineer | Self hosting — running it yourself — self-hosted servers, open-source clientsSelf hosting | 2 | full | 7/10 | Tprobed | |
Keep dozens of tokens organized — search, folders or groups, and service icons — so the right code is always two taps away Organization | power user | Totp core — the TOTP fundamentals — QR enrollment, organization, offline codes, non-standard tokensTotp core | 2 | partial | 6/10 | Cclaimed | |
Self-host the sync server on my own infrastructure and keep every secret inside my perimeter Server | it admin | Self hosting — running it yourself — self-hosted servers, open-source clientsSelf hosting | 2 | partial | 6/10 | Tprobed | |
Choose where my data is stored (region/residency) G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | partial | 5/10 | Tprobed | |
My team can share TOTP-protected logins through shared vaults or collections with per-member access control Sharing | it admin | Team admin — shared and managed use — shared vaults, org policies, programmatic provisioningTeam admin | 2 | partial | 4/10 | Cclaimed | |
Non-standard tokens work too — Steam Guard, HOTP counters, custom periods and digit lengths Variants | power user | Totp core — the TOTP fundamentals — QR enrollment, organization, offline codes, non-standard tokensTotp core | 2 | partial | 4/10 | Cclaimed | |
Perform bulk operations across many items at once G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 2 | partial | 4/10 | Tprobed | |
An agent can create and update vault entries — seeding new TOTP secrets, storing credentials — through documented programmatic surfaces Automation | ai-native user | Team admin — shared and managed use — shared vaults, org policies, programmatic provisioningTeam admin | 2 | none | 0/10 | ||
An agent can fetch a current TOTP code programmatically — via CLI or API — to complete a 2FA login inside an automated workflow Automation | ai-native user | Surfaces — where it meets your workflow — IDE, CLI, web, PR comments, CI checksSurfaces | 2 | none | 0/10 | ||
Do everything through the API that I can do in the UI G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 2 | none | 0/10 | ||
My passkeys sync across ecosystems — iOS, Android, Windows, Linux, browsers — instead of being locked to one platform vendor Sync | power user | Passkey support — passkeys in the vault — storage, sign-in, cross-ecosystem syncPasskey support | 2 | none | 0/10 | ||
A browser extension autofills my TOTP codes and passkeys during login instead of making me retype them Browser | everyday user | Surfaces — where it meets your workflow — IDE, CLI, web, PR comments, CI checksSurfaces | 2 | none | untested | none yet | |
Opt out of telemetry and usage tracking G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | none | untested | none yet | |
Push-based sign-in includes phishing defenses — number matching, location context, and admin-enforced MFA policies Push | it admin | Security posture — how it protects itself — app lock, E2EE design, audits, breach alertingSecurity posture | 2 | none | untested | none yet | |
Schedule recurring jobs or workflows G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 2 | n/a | untested | none yet | |
The app warns me when a service I use is breached or a stored credential is weak, reused, or exposed Monitoring | power user | Security posture — how it protects itself — app lock, E2EE design, audits, breach alertingSecurity posture | 2 | none | untested | none yet | |
The vendor publishes independent security audits of the app and its sync protocol Audits | security engineer | Security posture — how it protects itself — app lock, E2EE design, audits, breach alertingSecurity posture | 2 | none | untested | none yet | |
Enforce org-wide policies — require app lock, restrict export, mandate strong master credentials — across every member's app Policy | it admin | Team admin — shared and managed use — shared vaults, org policies, programmatic provisioningTeam admin | 1 | none | 0/10 | ||
Expose the vault through a local programmatic endpoint an agent can query for codes and secrets without screen-scraping the app Automation | ai-native user | Surfaces — where it meets your workflow — IDE, CLI, web, PR comments, CI checksSurfaces | 1 | none | 0/10 | ||
Read my codes from my smartwatch without pulling out my phone Watch | everyday user | Surfaces — where it meets your workflow — IDE, CLI, web, PR comments, CI checksSurfaces | 1 | none | untested | none yet | |
Version, review, and roll back my automations G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 1 | n/a | untested | none yet |
Opportunities — the stories that would move this product's scores, from its own judged verdictsOpportunitiestop 8 of 33 stories with headroom
What would move Ente Auth’s scores — derived from its own judged verdicts, biggest headroom first. Each line quotes what the judge found missing; shipping it (or evidencing it publicly) is the fix.
Agenticness — how well agents can access and operate the productConnect an agent via an official MCP server
nonemoves agent-readyimpact 45
The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na".
Agenticness — how well agents can access and operate the productDrive the product through a documented public API
partialq3/10moves agent-readyimpact 31.5
Missing: a documented public API/SDK covering core operations (add/edit/delete codes, sharing, sync), API authentication docs, and independent developer corroboration of API usage.
Passkey support — passkeys in the vault — storage, sign-in, cross-ecosystem syncThe app stores passkeys and signs me into websites and apps with them, not just TOTP codes
nonemoves PA Scoreimpact 30
The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na".
Agenticness — how well agents can access and operate the productSet up automations that run autonomously in the background
nonemoves Built-in AIimpact 30
The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na".
Agenticness — how well agents can access and operate the productOperate the product with natural-language commands
nonemoves Built-in AIimpact 30
The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na".
Agenticness — how well agents can access and operate the productIssue scoped/least-privilege API credentials for an agent
nonemoves agent-readyimpact 30
The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na".
Agenticness — how well agents can access and operate the productBuild against official SDKs
nonemoves agent-readyimpact 30
The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na".
Agenticness — how well agents can access and operate the productExplore an interactive API reference with runnable examples
nonemoves API qualityimpact 30
No evidence of an interactive API reference or runnable examples; OpenAPI/swagger probes returned 404s and no developer API docs are mentioned anywhere in the pack.
Showing the top 8 of 33 — every none/partial verdict in the story verdicts table is headroom.
Think a verdict is wrong? Every verdicts-table row has a Flag link — see the methodology.
Coverage map — which docs area, API section, or community source covers which judged storiesCoverage map6 surfaces · 26 covered stories
Where the cited evidence behind each covered verdict came from — the same citations the verdicts table shows, no extra judging.
Help docs24 stories
- Point an agent at llms.txt or agent-oriented docs
- Run the product headlessly / in CI for automation
- Use an official CLI
- Drive the product through a documented public API
- Perform bulk operations across many items at once
- Export all of my data in open formats and leave
- Read the product's source under an open license
- Self-host the core product
- Export all my TOTP secrets in an open, readable format and leave for another app whenever I choose — no lock-in
- Import tokens in bulk from other authenticator apps instead of re-enrolling every account by hand
- Moving to a new phone transfers all my tokens in one guided step
- Choose where my data is stored (region/residency)
- Prevent my data from being used to train AI models
- Control data retention and deletion
- The app itself locks behind biometrics or a PIN, so a borrowed phone doesn't expose my codes
- Self-host the sync server on my own infrastructure and keep every secret inside my perimeter
- A first-class desktop app gives me codes and vault access on my computer, not just on mobile
- Backups are end-to-end encrypted with a key the vendor never holds, and the encryption design is documented
- Losing my phone doesn't lose my accounts — a documented recovery path restores my tokens on a new device
- My team can share TOTP-protected logins through shared vaults or collections with per-member access control
- Scan a QR code and immediately start generating TOTP codes for a new account
- Codes generate fully offline — no network, no vendor account required just to see my TOTP codes
- Keep dozens of tokens organized — search, folders or groups, and service icons — so the right code is always two taps away
- Non-standard tokens work too — Steam Guard, HOTP counters, custom periods and digit lengths
Auth docs11 stories
- Perform bulk operations across many items at once
- Import tokens in bulk from other authenticator apps instead of re-enrolling every account by hand
- Moving to a new phone transfers all my tokens in one guided step
- Prevent my data from being used to train AI models
- A first-class desktop app gives me codes and vault access on my computer, not just on mobile
- Backups are end-to-end encrypted with a key the vendor never holds, and the encryption design is documented
- My tokens are available on my phone, tablet, and computer at the same time, kept in sync automatically
- Losing my phone doesn't lose my accounts — a documented recovery path restores my tokens on a new device
- My team can share TOTP-protected logins through shared vaults or collections with per-member access control
- Codes generate fully offline — no network, no vendor account required just to see my TOTP codes
- Keep dozens of tokens organized — search, folders or groups, and service icons — so the right code is always two taps away
Hacker News9 stories
- Export all of my data in open formats and leave
- Read the product's source under an open license
- Export all my TOTP secrets in an open, readable format and leave for another app whenever I choose — no lock-in
- Import tokens in bulk from other authenticator apps instead of re-enrolling every account by hand
- Moving to a new phone transfers all my tokens in one guided step
- The client apps are open source, so the code handling my seeds can be inspected and community-reviewed
- A first-class desktop app gives me codes and vault access on my computer, not just on mobile
- My tokens are available on my phone, tablet, and computer at the same time, kept in sync automatically
- Losing my phone doesn't lose my accounts — a documented recovery path restores my tokens on a new device
llms.txt7 stories
- Point an agent at llms.txt or agent-oriented docs
- Read the product's source under an open license
- Self-host the core product
- Choose where my data is stored (region/residency)
- Self-host the sync server on my own infrastructure and keep every secret inside my perimeter
- The client apps are open source, so the code handling my seeds can be inspected and community-reviewed
- Backups are end-to-end encrypted with a key the vendor never holds, and the encryption design is documented
Blog docs5 stories
- Control data retention and deletion
- The app itself locks behind biometrics or a PIN, so a borrowed phone doesn't expose my codes
- A first-class desktop app gives me codes and vault access on my computer, not just on mobile
- My team can share TOTP-protected logins through shared vaults or collections with per-member access control
- Keep dozens of tokens organized — search, folders or groups, and service icons — so the right code is always two taps away
Probe proofs — replayable recordings from the probe harnessProbe proofs
Replayable recordings from our probe harness — see the Prove-It protocol to submit one.
$brew info --json=v2 ente-cli | grep descreproduced$ brew info --json=v2 ente-cli | grep desc "desc": "Utility for exporting data from Ente and decrypt the export from Ente Auth"
$curl -s https://ente.com/llms.txt | head -4reproduced$ curl -s https://ente.com/llms.txt | head -4 # Ente > Ente builds private, end-to-end encrypted apps for photos, two-factor authentication codes, and files. Ente's apps and server are open source, and user data is encrypted before it leaves the user's device.
Business model
Ente Auth is free and fully open source (AGPL, client and server) with documented export and self-hosting; Ente monetizes its Photos product, not Auth.
pricing ↗Score trend
How this product’s scores have moved as evidence and verdicts are re-derived — a point per change, not per day.
Try Experimental
Run it in the microterminal →Recorded agent sessions — and a live MCP handshake where the vendor ships one.
Flag
⚑ Flag a verdictThink a verdict is wrong? Opens a prefilled GitHub issue — or use the ⚑ next to any verdict above.
For agents