vs Google Authenticator
vs Authy
vs 1Password
vs Bitwarden
vs Proton Pass
vs Ente Auth
vs 2FASVerified 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 Microsoft Authenticator 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
—0/10
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
—–
Test against a sandbox environment without touching production data
n/an/a
Explore an interactive API reference with runnable examples
n/an/a
Docs for agents
Point an agent at llms.txt or agent-oriented docs
—0/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
Openness
Self-host the core product
—–
Export all of my data in open formats and leave
~3/10
unlocks → 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
Do everything through the API that I can do in the UI
—0/10
Read the product's source under an open license
—0/10
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
—0/10
The app warns me when a service I use is breached or a stored credential is weak, reused, or exposed
—0/10
Push-based sign-in includes phishing defenses — number matching, location context, and admin-enforced MFA policies
~5/10
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
—0/10
My tokens are available on my phone, tablet, and computer at the same time, kept in sync automatically
!4/10
Losing my phone doesn't lose my accounts — a documented recovery path restores my tokens on a new device
!5/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
—0/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
!5/10
Codes generate fully offline — no network, no vendor account required just to see my TOTP codes
!4/10
Keep dozens of tokens organized — search, folders or groups, and service icons — so the right code is always two taps away
—0/10
Non-standard tokens work too — Steam Guard, HOTP counters, custom periods and digit lengths
—0/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 | none | 0/10 | ||
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 | |
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 | ||
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 | 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 | |
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 | n/a | 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 | |
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 | untested | none yet | |
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 | 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 | |
Use an official CLI G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 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 | disputed | 5/10 | Dcontradicted | |
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 | disputed | 5/10 | Dcontradicted | |
Export all of my data in open formats and leave G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 3 | partial | 3/10 | Xcommunity | |
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 | none | 0/10 | ||
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 | none | 0/10 | ||
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 | 0/10 | ||
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 | |
Prevent my data from being used to train AI models G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 3 | none | untested | none yet | |
Self-host the core product G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 3 | none | untested | none yet | |
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 | |
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 | disputed | 5/10 | Dcontradicted | |
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 | partial | 5/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 | disputed | 4/10 | Dcontradicted | |
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 | disputed | 4/10 | Dcontradicted | |
Opt out of telemetry and usage tracking G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | disputed | 4/10 | Dcontradicted | |
Control data retention and deletion G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | partial | 3/10 | Xcommunity | |
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 | 0/10 | ||
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 | ||
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 | none | 0/10 | ||
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 | 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 | ||
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 | none | 0/10 | ||
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 | none | 0/10 | ||
Read the product's source under an open license G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 2 | none | 0/10 | ||
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 | 0/10 | ||
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 | 0/10 | ||
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 | none | untested | none yet | |
Choose where my data is stored (region/residency) G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | none | untested | none yet | |
Perform bulk operations across many items at once G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 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 | |
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 | none | untested | none yet | |
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 | none | untested | none yet | |
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 | partial | 4/10 | Cclaimed | |
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 | ||
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 39 stories with headroom
What would move Microsoft Authenticator’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
nonemoves agent-readyimpact 45
Microsoft Authenticator is a consumer mobile app with no evidence of a documented public API for programmatic/AI-driven control; probes for llms.txt, docs-md, and OpenAPI specs all returned 404s.
Sync backup — not losing your accounts — encrypted backup, multi-device sync, recoveryBackups are end-to-end encrypted with a key the vendor never holds, and the encryption design is documented
nonemoves PA Scoreimpact 30
Docs confirm a Cloud Backup feature exists (microsoft-authenticator-docs-9, -13) but provide no description of end-to-end encryption or a vendor-inaccessible key, and no encryption design documentation is cited anywhere.
Portability — your secrets stay yours — open export, bulk import, device migrationExport all my TOTP secrets in an open, readable format and leave for another app whenever I choose — no lock-in
nonemoves PA Scoreimpact 30
Docs describe cloud backup/restore and password export/import, but none of this covers exporting TOTP secrets in an open format for use in another app; community evidence explicitly states Microsoft issues non-standard QR codes that other TOTP clients reject, indicating deliberate lock-in rather than portability.
Openness — open source, data portability, and self-hosting storiesSelf-host the core product
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".
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
Missing: any documentation of passkey creation, storage, or sign-in via Authenticator, and any independent confirmation of passkey support.
Privacy posture — data-handling and privacy storiesPrevent my data from being used to train AI models
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 productPoint an agent at llms.txt or agent-oriented docs
nonemoves agent-readyimpact 30
Probes show no llms.txt, no markdown docs, and no OpenAPI spec available for Microsoft Authenticator's documentation site; there is no evidence of agent-oriented documentation format.
Showing the top 8 of 39 — 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 map2 surfaces · 11 covered stories
Where the cited evidence behind each covered verdict came from — the same citations the verdicts table shows, no extra judging.
En us docs11 stories
- Export all of my data in open formats and leave
- Moving to a new phone transfers all my tokens in one guided step
- Control data retention and deletion
- Opt out of telemetry and usage tracking
- The app itself locks behind biometrics or a PIN, so a borrowed phone doesn't expose my codes
- Push-based sign-in includes phishing defenses — number matching, location context, and admin-enforced MFA policies
- Read my codes from my smartwatch without pulling out my phone
- 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
- 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
Hacker News9 stories
- Export all of my data in open formats and leave
- Moving to a new phone transfers all my tokens in one guided step
- Control data retention and deletion
- Opt out of telemetry and usage tracking
- Push-based sign-in includes phishing defenses — number matching, location context, and admin-enforced MFA policies
- 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
- 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
Business model
Free mobile app; no paid tiers. Enterprise value accrues to Microsoft Entra ID subscriptions, not the app itself.
pricing ↗Score trend
How this product’s scores have moved as evidence and verdicts are re-derived — a point per change, not per day.
Flag
⚑ Flag a verdictThink a verdict is wrong? Opens a prefilled GitHub issue — or use the ⚑ next to any verdict above.
For agents