Bitwarden vs Ente Auth

Agent access

1. ai-native userPoint an agent at llms.txt or agent-oriented docs

   weight 2 · round to Bitwarden
   Bitwarden✓fullprobed9/10

   Bitwarden serves a live llms.txt at bitwarden.com/llms.txt (HTTP 200) with structured content, and help pages ship real per-page markdown mirrors (e.g., cli.md) confirming genuine agent-oriented documentation rather than a stub. This is directly confirmed by runtime probes, not just claims. Missing for 10: no independent third-party corroboration of an agent actually consuming these docs end-to-end in a workflow.

   • [probe] “PROBE llms.txt: HTTP 200 at https://bitwarden.com/llms.txt # Bitwarden > The most trusted open source password manager for passwords, passk…”
   • [probe] “PROBE runtime (recorded 2026-09-15): bitwarden.com serves a live llms.txt ('# Bitwarden — The most trusted open source password manager...')…”

   proof ↗⚑ flag

   Ente Auth✓fullprobed7/10

   Ente serves a live llms.txt at ente.com/llms.txt confirmed by two independent probes, giving an agent a fair entry point; however, docs-as-markdown and OpenAPI endpoints 404, so agent-oriented documentation beyond the single llms.txt file is thin. missing for 10: markdown-served docs pages, OpenAPI/agent-consumable API spec, broader agent-oriented doc structure beyond one root file.

   • [probe] “PROBE llms.txt: HTTP 200 at https://ente.com/llms.txt # Ente > Ente builds private, end-to-end encrypted apps for photos, two-factor authen…”
   • [probe] “PROBE runtime (recorded 2026-09-15): ente.com serves a live llms.txt — '# Ente — Ente builds private, end-to-end encrypted apps for photos, …”
   • [probe] “PROBE docs-md: HTTP 404 at https://ente.com/help/auth/.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://ente.com/openapi.json, https://ente.com/swagger.json, https://ente.com/api/openapi.json, htt…”

   proof ↗⚑ flag

2. ai-native userRun the product headlessly / in CI for automation

   weight 2 · round to Bitwarden
   Bitwarden✓fullprobed8/10

   Bitwarden ships an official CLI with API-key authentication explicitly documented as suitable for automated workflows/CI, plus a Public API for org automation and a headless 'bw serve' mode confirmed at runtime. missing for 10: no CI-specific tutorial/example pipeline (e.g., GitHub Actions) in evidence, and one community report notes CLI 'bw list' unexpectedly dumping plaintext secrets, a minor safety caveat for automation use.

   • [claimed-docs] “The Bitwarden command-line interface (CLI) is a powerful, fully-featured tool for accessing and managing your vault.”
   • [claimed-docs] “Using the personal API key for CLI authentication is suitable for automated workflows, for providing access to an external appli”
   • [claimed-docs] “The Bitwarden Public API provides organizations a suite of tools for managing members, collections, groups, event logs, and policies.”
   • [probe] “PROBE runtime (recorded 2026-09-15): the official bw CLI installs keylessly from npm (@bitwarden/cli, registry latest 2026.8.0) and prints i…”
   • [community] “I had a really bad experience with the bitwarden cli. I ran 'bw list', assuming it would list names, but it listed everything including pass…”

   proof ↗⚑ flag

   Ente Auth~partialprobed3/10

   Ente provides an official CLI (ente-cli) that can run headlessly to export/backup Auth codes, which is scriptable and could be used in automation/CI contexts, but evidence only documents it for exporting/decrypting backups, not for generic headless operation, generating TOTP codes on demand, or CI-integrated workflows. Missing for 10: documentation of CLI usage for retrieving/generating codes programmatically, CI-specific examples, and any first-party statement about automation/agentic use beyond backup.

   • [claimed-docs] “You can use [Ente's CLI](https://github.com/ente/ente/tree/main/cli#readme) to automatically backup your Auth codes.”
   • [probe] “PROBE runtime (recorded 2026-09-15): Ente's official CLI is packaged in Homebrew as ente-cli 0.3.0, described by the formula itself as 'Util…”

   proof ↗⚑ flag

3. ai-native userConnect an agent via an official MCP server

   weight 3 · round to Bitwarden
   Bitwarden✓fullprobed9/10

   Bitwarden ships a first-party, GPL-3.0 MCP server (bitwarden/mcp-server) published to npm, and a runtime probe confirms it completes a full stdio handshake, showing it works as documented rather than just being an announcement. Missing for 10: independent third-party review of the MCP server's tool set/security beyond the vendor probe.

   • [probe] “official MCP server documented at https://github.com/bitwarden/mcp-server”
   • [probe] “PROBE runtime (recorded 2026-09-15): Bitwarden's OFFICIAL MCP server completed a FULL keyless stdio initialize handshake — `npx -y @bitwarde…”

   proof ↗⚑ flag

   Ente Auth—none0/10

   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". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

4. ai-native userUse an official CLI

   weight 2 · round to Bitwarden
   Bitwarden✓fullprobed9/10

   Bitwarden ships a documented, fully-featured official CLI (bw) with vault management, API key auth for automated workflows, and a runtime-verified 'bw serve' mode exposing a local REST API well-suited to agentic/AI use. missing for 10: independent third-party benchmarking of agent integration quality beyond one community anecdote about plaintext output behavior.

   • [claimed-docs] “The Bitwarden command-line interface (CLI) is a powerful, fully-featured tool for accessing and managing your vault.”
   • [claimed-docs] “Using the personal API key for CLI authentication is suitable for automated workflows, for providing access to an external appli”
   • [probe] “official CLI documented at https://bitwarden.com/help/cli/”
   • [probe] “PROBE runtime (recorded 2026-09-15): the official bw CLI installs keylessly from npm (@bitwarden/cli, registry latest 2026.8.0) and prints i…”
   • [community] “I had a really bad experience with the bitwarden cli. I ran 'bw list', assuming it would list names, but it listed everything including pass…”

   proof ↗⚑ flag

   Ente Auth~partialprobed6/10

   Ente ships an official CLI (github.com/ente/ente/tree/main/cli) confirmed to be packaged via Homebrew as 'ente-cli', documented as scriptable tooling to 'automatically backup your Auth codes' and decrypt exports — this is a real, official, automatable interface. However it is scoped narrowly to backup/export/decrypt operations rather than full account/code management or general agentic control. Missing for 10: broader CLI command coverage (add/edit/delete codes, sharing, sync), first-party docs detailing CLI usage beyond export, and independent hands-on reports of using it in automated/agentic workflows.

   • [claimed-docs] “You can use [Ente's CLI](https://github.com/ente/ente/tree/main/cli#readme) to automatically backup your Auth codes.”
   • [probe] “PROBE runtime (recorded 2026-09-15): Ente's official CLI is packaged in Homebrew as ente-cli 0.3.0, described by the formula itself as 'Util…”

   proof ↗⚑ flag

5. ai-native userDrive the product through a documented public API

   weight 3 · round to Bitwarden
   Bitwarden✓fullprobed8/10

   Bitwarden documents a Public API for organization management (bitwarden-docs-8), a personal API key for automated/programmatic access (bitwarden-docs-9), and a full-featured CLI (bitwarden-docs-7, bitwarden-probe-4) with a documented `bw serve` REST mode enabling agent-driven vault access (bitwarden-probe-rt-1); this constitutes a documented public API surface an AI-native user could drive. missing for 10: a public OpenAPI/swagger spec resolves 404 on probed endpoints (bitwarden-probe-2), and one community report flags a CLI safety/UX issue (bitwarden-comm-13) showing rough edges in automation ergonomics.

   • [claimed-docs] “The Bitwarden command-line interface (CLI) is a powerful, fully-featured tool for accessing and managing your vault.”
   • [claimed-docs] “The Bitwarden Public API provides organizations a suite of tools for managing members, collections, groups, event logs, and policies.”
   • [claimed-docs] “Using the personal API key for CLI authentication is suitable for automated workflows, for providing access to an external appli”
   • [probe] “PROBE runtime (recorded 2026-09-15): the official bw CLI installs keylessly from npm (@bitwarden/cli, registry latest 2026.8.0) and prints i…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://bitwarden.com/openapi.json, https://bitwarden.com/swagger.json, https://bitwarden.com/api/op…”
   • [community] “I had a really bad experience with the bitwarden cli. I ran 'bw list', assuming it would list names, but it listed everything including pass…”

   proof ↗⚑ flag

   Ente Auth~partialprobed3/10

   Ente provides a CLI (ente-cli) for exporting/backing up Auth codes and a documented deep-link scheme (enteauth://search), but there is no documented public REST/GraphQL API or SDK for driving the product programmatically — OpenAPI probes returned 404s. missing for 10: a documented public API/SDK covering core operations (add/edit/delete codes, sharing, sync), API authentication docs, and independent developer corroboration of API usage.

   • [probe] “PROBE runtime (recorded 2026-09-15): Ente's official CLI is packaged in Homebrew as ente-cli 0.3.0, described by the formula itself as 'Util…”
   • [claimed-docs] “You can use [Ente's CLI](https://github.com/ente/ente/tree/main/cli#readme) to automatically backup your Auth codes.”
   • [claimed-docs] “Added support for search deep links via enteauth://search.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://ente.com/openapi.json, https://ente.com/swagger.json, https://ente.com/api/openapi.json, htt…”

   proof ↗⚑ flag

6. ai-native userIssue scoped/least-privilege API credentials for an agent

   weight 2 · round to Bitwarden
   Bitwarden~partialprobed4/10

   Bitwarden documents a personal API key for CLI/automated workflows and a Public API/CLI (including `bw serve` and an official MCP server) that an agent could use, but there's no evidence of fine-grained, least-privilege scoping (e.g., read-only, per-item, or per-collection API keys) — the personal API key and CLI access appear to grant broad vault access rather than scoped permissions, and a hands-on report shows `bw list` dumping full plaintext secrets rather than a restricted subset. missing for 10: documented scoped/restricted API key types, per-agent permission grants, or evidence that MCP/CLI access can be limited to specific vault items rather than the whole vault.

   • [claimed-docs] “Using the personal API key for CLI authentication is suitable for automated workflows, for providing access to an external appli”
   • [claimed-docs] “The Bitwarden Public API provides organizations a suite of tools for managing members, collections, groups, event logs, and policies.”
   • [probe] “PROBE runtime (recorded 2026-09-15): the official bw CLI installs keylessly from npm (@bitwarden/cli, registry latest 2026.8.0) and prints i…”
   • [probe] “PROBE runtime (recorded 2026-09-15): Bitwarden's OFFICIAL MCP server completed a FULL keyless stdio initialize handshake — `npx -y @bitwarde…”
   • [community] “I had a really bad experience with the bitwarden cli. I ran 'bw list', assuming it would list names, but it listed everything including pass…”

   proof ↗⚑ flag

   Ente Auth—none0/10

   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". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

7. ai-native userBuild against official SDKs

   weight 2 · round to Bitwarden
   Bitwarden~partialprobed4/10

   Evidence shows Bitwarden exposes a Public API, CLI, personal API keys for automation, and an official MCP server (all of which an AI-native builder could integrate against), but there is no evidence of a dedicated, language-specific 'official SDK' (e.g., a bitwarden/sdk repo) and the OpenAPI/swagger spec probes all returned 404, suggesting no machine-readable API contract is published. missing for 10: explicit official SDK repositories/language bindings, published OpenAPI spec, independent developer corroboration of SDK usage.

   • [claimed-docs] “The Bitwarden command-line interface (CLI) is a powerful, fully-featured tool for accessing and managing your vault.”
   • [claimed-docs] “The Bitwarden Public API provides organizations a suite of tools for managing members, collections, groups, event logs, and policies.”
   • [claimed-docs] “Using the personal API key for CLI authentication is suitable for automated workflows, for providing access to an external appli”
   • [probe] “PROBE openapi: all candidate paths 404 (https://bitwarden.com/openapi.json, https://bitwarden.com/swagger.json, https://bitwarden.com/api/op…”
   • [probe] “official MCP server documented at https://github.com/bitwarden/mcp-server”
   • [probe] “PROBE runtime (recorded 2026-09-15): Bitwarden's OFFICIAL MCP server completed a FULL keyless stdio initialize handshake — `npx -y @bitwarde…”

   proof ↗⚑ flag

   Ente Auth—none0/10

   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". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

Agentic features

1. ai-native userSet up automations that run autonomously in the background

   weight 2 · round drawn
   Bitwarden—none0/10

   Bitwarden offers CLI/API/MCP server access that agents could use, but there is no evidence of a mechanism for setting up autonomous, scheduled, or background-running automations (e.g., triggers, workflows, cron-like jobs) — it only provides interfaces for on-demand vault access. missing for 10: any documented scheduling/trigger/workflow automation feature, evidence of background/autonomous execution, or vendor claims of persistent automation setup.

   • [claimed-docs] “The Bitwarden command-line interface (CLI) is a powerful, fully-featured tool for accessing and managing your vault.”
   • [claimed-docs] “Using the personal API key for CLI authentication is suitable for automated workflows, for providing access to an external appli”
   • [probe] “PROBE runtime (recorded 2026-09-15): the official bw CLI installs keylessly from npm (@bitwarden/cli, registry latest 2026.8.0) and prints i…”
   • [probe] “PROBE runtime (recorded 2026-09-15): Bitwarden's OFFICIAL MCP server completed a FULL keyless stdio initialize handshake — `npx -y @bitwarde…”

   proof ↗⚑ flag

   Ente Auth—none0/10

   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". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

2. ai-native userOperate the product with natural-language commands

   weight 2 · round to Bitwarden
   Bitwarden✓fullprobed8/10

   Bitwarden ships an official MCP server (bitwarden/mcp-server) that completed a live stdio handshake, letting AI agents/assistants issue natural-language commands to manage the vault, backed by a full-featured CLI and llms.txt for AI-friendly docs. Missing for 10: no independent hands-on demonstration of a natural-language command actually retrieving/creating vault items via the MCP server, and community feedback flags CLI output risks (e.g., plaintext dumps) that complicate safe agentic use.

   • [probe] “official MCP server documented at https://github.com/bitwarden/mcp-server”
   • [probe] “PROBE runtime (recorded 2026-09-15): Bitwarden's OFFICIAL MCP server completed a FULL keyless stdio initialize handshake — `npx -y @bitwarde…”
   • [claimed-docs] “The Bitwarden command-line interface (CLI) is a powerful, fully-featured tool for accessing and managing your vault.”
   • [probe] “PROBE runtime (recorded 2026-09-15): the official bw CLI installs keylessly from npm (@bitwarden/cli, registry latest 2026.8.0) and prints i…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://bitwarden.com/llms.txt # Bitwarden > The most trusted open source password manager for passwords, passk…”
   • [community] “I had a really bad experience with the bitwarden cli. I ran 'bw list', assuming it would list names, but it listed everything including pass…”

   proof ↗⚑ flag

   Ente Auth—none0/10

   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". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

Api quality

1. ai-native userExplore an interactive API reference with runnable examples

   weight 2 · round drawn
   Bitwarden—none0/10

   Bitwarden documents a Public API for org management (bitwarden-docs-8) but there is no evidence of an interactive API reference with runnable examples (e.g., Swagger/OpenAPI explorer); a direct probe for openapi.json/swagger.json endpoints returned 404 on all candidate paths (bitwarden-probe-2), indicating no such interactive reference is exposed.

   • [claimed-docs] “The Bitwarden Public API provides organizations a suite of tools for managing members, collections, groups, event logs, and policies.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://bitwarden.com/openapi.json, https://bitwarden.com/swagger.json, https://bitwarden.com/api/op…”

   proof ↗⚑ flag

   Ente Auth—none0/10

   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.

   • [probe] “PROBE openapi: all candidate paths 404 (https://ente.com/openapi.json, https://ente.com/swagger.json, https://ente.com/api/openapi.json, htt…”
   • [probe] “PROBE docs-md: HTTP 404 at https://ente.com/help/auth/.md”

   proof ↗⚑ flag

2. ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)

   weight 2 · round drawn
   Bitwarden—none0/10

   Bitwarden documents a Public API and CLI, but a probe for common OpenAPI/Swagger spec URLs (openapi.json, swagger.json, .well-known/openapi.json) all returned 404, and no evidence pack item shows a downloadable machine-readable API spec. Missing for 10: any documented OpenAPI/Swagger file, spec download link, or API reference generator output.

   • [claimed-docs] “The Bitwarden Public API provides organizations a suite of tools for managing members, collections, groups, event logs, and policies.”
   • [claimed-docs] “Using the personal API key for CLI authentication is suitable for automated workflows, for providing access to an external appli”
   • [probe] “PROBE openapi: all candidate paths 404 (https://bitwarden.com/openapi.json, https://bitwarden.com/swagger.json, https://bitwarden.com/api/op…”

   proof ↗⚑ flag

   Ente Auth—none0/10

   Probe results explicitly show all candidate OpenAPI/Swagger paths return 404, and there is no documented machine-readable API spec anywhere in the evidence pack; missing for 10: any published OpenAPI/Swagger file, API reference docs, or equivalent machine-readable spec.

   • [probe] “PROBE openapi: all candidate paths 404 (https://ente.com/openapi.json, https://ente.com/swagger.json, https://ente.com/api/openapi.json, htt…”

   proof ↗⚑ flag

3. ai-native userRely on versioned APIs with a documented deprecation policy

   weight 2 · round drawn
   Bitwarden—none0/10

   Bitwarden documents a Public API and CLI/personal API key access, but there is no evidence of API versioning scheme or a documented deprecation policy; probes for an OpenAPI spec (bitwarden-probe-2) all returned 404s, and no docs mention version headers, breaking-change policy, or sunset timelines.

   • [claimed-docs] “The Bitwarden Public API provides organizations a suite of tools for managing members, collections, groups, event logs, and policies.”
   • [claimed-docs] “Using the personal API key for CLI authentication is suitable for automated workflows, for providing access to an external appli”
   • [probe] “PROBE openapi: all candidate paths 404 (https://bitwarden.com/openapi.json, https://bitwarden.com/swagger.json, https://bitwarden.com/api/op…”

   proof ↗⚑ flag

   Ente Auth—none0/10

   Ente Auth is a 2FA authenticator app; there is no evidence of a public API, API versioning scheme, or documented deprecation policy — OpenAPI probes 404 and no API docs exist in the evidence pack.

   • [probe] “PROBE openapi: all candidate paths 404 (https://ente.com/openapi.json, https://ente.com/swagger.json, https://ente.com/api/openapi.json, htt…”
   • [probe] “PROBE docs-md: HTTP 404 at https://ente.com/help/auth/.md”

   proof ↗⚑ flag

1. ai-native userPerform bulk operations across many items at once

   weight 2 · round to Bitwarden
   Bitwarden~partialcommunity6/10

   The CLI (bw list/create/edit/delete) and Public API expose scriptable, item-level access that can be chained for bulk operations, and import/export functions handle whole-vault bulk transfers of many items at once; community evidence (bw list dumping the entire vault) confirms bulk read actually works. However, there is no first-party documentation of a dedicated bulk-edit/bulk-tag/bulk-delete command or batch endpoint — bulk operations require the user to script them themselves rather than a built-in bulk API. Missing for 10: documented native bulk-update/bulk-delete commands, batch API endpoints for many items, and independent hands-on confirmation of large-scale automated edits succeeding.

   • [claimed-docs] “The Bitwarden command-line interface (CLI) is a powerful, fully-featured tool for accessing and managing your vault.”
   • [claimed-docs] “The Bitwarden Public API provides organizations a suite of tools for managing members, collections, groups, event logs, and policies.”
   • [claimed-docs] “Using the personal API key for CLI authentication is suitable for automated workflows, for providing access to an external appli”
   • [claimed-docs] “Export your vault data, including logins and notes, to back up important information or transfer to a new Bitwarden vault.”
   • [claimed-docs] “Import logins and data from different password managers, other Bitwarden vaults, or encrypted exports to instantly transfer your information…”
   • [community] “I had a really bad experience with the bitwarden cli. I ran 'bw list', assuming it would list names, but it listed everything including pass…”

   proof ↗⚑ flag

   Ente Auth~partialprobed4/10

   Ente Auth documents bulk import from other 2FA apps and a CLI tool for scripted export/backup of all codes, which supports some automation-depth for a bulk operation, but there is no evidence of programmatic bulk editing, deleting, or tagging across many stored codes at once (only single-item edit/delete via long-press is documented). missing for 10: bulk edit/delete/tag API or CLI beyond import/export, evidence of scripted multi-item management, independent hands-on confirmation of bulk workflows.

   • [claimed-docs] “Bulk import from other 2FA apps”
   • [claimed-docs] “Ente Auth natively supports imports from many 2FA providers.”
   • [claimed-docs] “You can use [Ente's CLI](https://github.com/ente/ente/tree/main/cli#readme) to automatically backup your Auth codes.”
   • [probe] “PROBE runtime (recorded 2026-09-15): Ente's official CLI is packaged in Homebrew as ente-cli 0.3.0, described by the formula itself as 'Util…”
   • [claimed-docs] “You can delete or edit a code by long pressing (or right clicking on desktop) on that item.”

   proof ↗⚑ flag

1. ai-native userDo everything through the API that I can do in the UI

   weight 2 · round to Bitwarden
   Bitwarden~partialprobed6/10

   Bitwarden ships a fully-featured CLI and a Vault Management API (`bw serve`) covering item/vault CRUD, TOTP retrieval, and org management via a Public API and personal API key for automated workflows, giving strong but not fully documented parity with the UI. There's no explicit vendor claim or evidence that every UI feature (e.g., passkey autofill, browser-context auto-fill, vault health reports) is exposed via API/CLI, and a hands-on report shows the CLI's `bw list` behaves differently than expected (dumping all secrets) rather than mirroring UI workflows cleanly. missing for 10: explicit API/CLI equivalents for passkey autofill and browser-based auto-fill, API access to vault health reports, and a documented feature-parity statement.

   • [claimed-docs] “The Bitwarden command-line interface (CLI) is a powerful, fully-featured tool for accessing and managing your vault.”
   • [claimed-docs] “The Bitwarden Public API provides organizations a suite of tools for managing members, collections, groups, event logs, and policies.”
   • [claimed-docs] “Using the personal API key for CLI authentication is suitable for automated workflows, for providing access to an external appli”
   • [probe] “PROBE runtime (recorded 2026-09-15): the official bw CLI installs keylessly from npm (@bitwarden/cli, registry latest 2026.8.0) and prints i…”
   • [community] “I had a really bad experience with the bitwarden cli. I ran 'bw list', assuming it would list names, but it listed everything including pass…”

   proof ↗⚑ flag

   Ente Auth—none0/10

   Ente Auth exposes only a CLI for exporting/decrypting backups, not a general API covering all UI actions (add/edit/share/organize codes, etc.); probes for OpenAPI/API docs all returned 404, and no documentation describes a comprehensive API surface.

   • [probe] “PROBE openapi: all candidate paths 404 (https://ente.com/openapi.json, https://ente.com/swagger.json, https://ente.com/api/openapi.json, htt…”
   • [probe] “PROBE runtime (recorded 2026-09-15): Ente's official CLI is packaged in Homebrew as ente-cli 0.3.0, described by the formula itself as 'Util…”
   • [claimed-docs] “You can use [Ente's CLI](https://github.com/ente/ente/tree/main/cli#readme) to automatically backup your Auth codes.”

   proof ↗⚑ flag

2. ai-native userExport all of my data in open formats and leave

   weight 3 · round to Bitwarden
   Bitwarden✓fullclaimed9/10

   Bitwarden's docs explicitly support exporting full vault data (logins, notes) for backup or transfer, plus separate authenticator/TOTP export in open formats (JSON), and CLI/API access for automated bulk export. This directly satisfies the 'export all data in open formats and leave' story with strong first-party documentation. Missing for 10: no independent/hands-on confirmation of export format fidelity or completeness verification by a third party.

   • [claimed-docs] “Export your vault data, including logins and notes, to back up important information or transfer to a new Bitwarden vault.”
   • [claimed-docs] “Export your vault data, including logins and notes, to back up important information or transfer to a new Bitwarden vault”
   • [claimed-docs] “Google Authenticator (QR code): Import from Google Authenticator using a QR code... LastPass (JSON): Import a LastPass Authenticator account…”
   • [claimed-docs] “Google Authenticator (QR code): Import from Google Authenticator using a QR code... LastPass (JSON): Import a LastPass Authenticator account…”
   • [claimed-docs] “The Bitwarden command-line interface (CLI) is a powerful, fully-featured tool for accessing and managing your vault.”
   • [claimed-docs] “Import logins and data from different password managers, other Bitwarden vaults, or encrypted exports to instantly transfer your information…”

   proof ↗⚑ flag

   Ente Auth!disputedcontradicted5/10

   Ente ships an official CLI to export and decrypt Auth data and documents password-encrypted local backups, and some HN commenters confirm easy export/import between apps (comm-6,7,8; probe-rt-1). But a first-hand HN commenter explicitly states 'You cant easily export your codes into a different format using this app, meaning that it is difficult to migrate away' (comm-2), directly contradicting the frictionless open-format export claim. Missing for 10: a documented plain/open (non-proprietary) full export format, resolution of the lock-in complaint, and independent verification that CLI-exported data is usable outside Ente.

   • [claimed-docs] “Automatic daily backups: When enabled, Ente Auth creates one local backup per day when you open the app.”
   • [claimed-docs] “Password-protected: All local backups are encrypted with a password you set. Keep this password safe, because Ente cannot recover it for you…”
   • [claimed-docs] “You can use [Ente's CLI](https://github.com/ente/ente/tree/main/cli#readme) to automatically backup your Auth codes.”
   • [claimed-docs] “the data is encrypted using a key derived from the user's password”
   • [probe] “PROBE runtime (recorded 2026-09-15): Ente's official CLI is packaged in Homebrew as ente-cli 0.3.0, described by the formula itself as 'Util…”
   • [community] “I'm waiting for bitwarden or aegis export capability before trying this out. You cant easily export your codes into a different format using…”
   • [community] “I have been using Aegis but switched to Ente Auth as I decided to use Ente Photos as well. Both Aegis and Ente Auth are great options. This …”
   • [community] “I think it has its own backup service. But it otherwise lets you export/import your data. I feel like as long as I can do an export in some …”

   proof ↗⚑ flag

3. ai-native userRead the product's source under an open license

   weight 2 · round to Ente Auth
   Bitwarden~partialprobed6/10

   Community evidence and the MCP server repo confirm Bitwarden ships components under open licenses (e.g., bitwarden/mcp-server is GPL-3.0) and is broadly known/marketed as 'the most trusted open source password manager,' and users cite valuing its open client source. However, the same evidence documents a real controversy where Bitwarden relicensed its SDK away from a fully open license, only reversing course after backlash — a concrete counter-example to unconditional openness. missing for 10: explicit license file/repo evidence for the core vault clients, resolution details confirming all components are now uniformly open-licensed, independent audit confirming no remaining non-open components.

   • [probe] “PROBE runtime (recorded 2026-09-15): Bitwarden's OFFICIAL MCP server completed a FULL keyless stdio initialize handshake — `npx -y @bitwarde…”
   • [community] “Props for them to step in the right direction, it wasn’t obvious at all for a few days what they would do (re: SDK relicensing controversy).”
   • [community] “Thank you to Bitwarden for relicensing back to Free/Open License... I no longer recommend Bitwarden for normal people because the built-in p…”
   • [community] “I’m relieved... I hope they realized that being FOSS is their moat... I’m still not sure how I feel about them now. Trust in the company has…”
   • [community] “I use BitWarden because I'd never trust a password manager with closed source clients... Needless to say I move to the next ethical e2ee pas…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://bitwarden.com/llms.txt # Bitwarden > The most trusted open source password manager for passwords, passk…”

   proof ↗⚑ flag

   Ente Auth✓fullprobed7/10

   Ente's own llms.txt explicitly states 'Ente's apps and server are open source,' and a GitHub repo (ente/ente) is referenced for the CLI/export tooling; independent HN commentary corroborates ('thank you for releasing it open source'). Missing for 10: explicit license name/text and a direct link to the license file are not shown in the evidence pack.

   • [probe] “PROBE llms.txt: HTTP 200 at https://ente.com/llms.txt # Ente > Ente builds private, end-to-end encrypted apps for photos, two-factor authen…”
   • [probe] “PROBE runtime (recorded 2026-09-15): ente.com serves a live llms.txt — '# Ente — Ente builds private, end-to-end encrypted apps for photos, …”
   • [community] “This looks quite nice, thank you for releasing it open source... One note as I signed up for an account is that the email verification went …”
   • [claimed-docs] “You can use [Ente's CLI](https://github.com/ente/ente/tree/main/cli#readme) to automatically backup your Auth codes.”

   proof ↗⚑ flag

4. ai-native userSelf-host the core product

   weight 3 · round to Bitwarden
   Bitwarden✓fullprobed9/10

   Bitwarden provides official, well-documented on-premise/self-hosting instructions for Linux servers, and it is open-source, aligning strongly with an AI-native user's openness needs. missing for 10: independent hands-on verification of self-hosted deployment specifically (evidence is docs-only, not community confirmation of self-hosting success).

   • [claimed-docs] “This article will walk you through the procedure to install and deploy Bitwarden to your own Linux server.”
   • [probe] “PROBE llms.txt: HTTP 200 at https://bitwarden.com/llms.txt # Bitwarden > The most trusted open source password manager for passwords, passk…”

   proof ↗⚑ flag

   Ente Auth✓fullprobed8/10

   Ente explicitly documents self-hosting instructions, pointing users to run Ente Auth at localhost/machine-ip:3003, and the product is described as open source, consistent with independent verification via the llms.txt runtime probe. missing for 10: independent hands-on report of a full self-hosted deployment (beyond docs/probe), and details on self-hosting server setup/requirements beyond the port reference.

   • [claimed-docs] “Alternatively, if using Ente Auth, get started by adding an account (assuming you are running Ente Auth at `http://<machine-ip>:3003` or `ht…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://ente.com/llms.txt # Ente > Ente builds private, end-to-end encrypted apps for photos, two-factor authen…”
   • [probe] “PROBE runtime (recorded 2026-09-15): ente.com serves a live llms.txt — '# Ente — Ente builds private, end-to-end encrypted apps for photos, …”

   proof ↗⚑ flag

Storage

1. everyday userThe app stores passkeys and signs me into websites and apps with them, not just TOTP codes

   weight 3 · round to Bitwarden
   Bitwarden✓fullclaimed8/10

   Bitwarden documents storing passkeys in the vault and using the browser extension or mobile apps to autofill/sign in with them across websites and apps, going beyond TOTP-only support (bitwarden-docs-4), which aligns directly with the story's requirement of passkey-based sign-in, not just TOTP codes. Missing for 10: independent/hands-on user reports specifically confirming passkey sign-in reliability (community evidence only discusses TOTP/autofill issues, not passkeys) and detail on cross-platform (desktop app) passkey support beyond browser/mobile.

   • [claimed-docs] “Save passkeys in your Bitwarden vault and use the browser extension or mobile apps to autofill them across the apps and websites you use eve…”
   • [claimed-docs] “it automatically produces the time-based one-time passwords (TOTPs), six-digit codes using SHA-1 that rotate every 30 seconds”
   • [claimed-docs] “Connect Authenticator with Password Manager to sync your verification codes. Once activated, the Bitwarden apps stay synchronized with any c…”

   proof ↗⚑ flag

   Ente Auth—none0/10

   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". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

Sync

1. power userMy passkeys sync across ecosystems — iOS, Android, Windows, Linux, browsers — instead of being locked to one platform vendor

   weight 2 · round to Bitwarden
   Bitwarden~partialclaimed6/10

   Bitwarden explicitly stores passkeys in the vault and lets the browser extension and mobile apps autofill them across apps and sites, which is the platform-agnostic model (unlike Apple/Google's device-locked passkey sync) [bitwarden-docs-4]. However, the docs only call out browser extension and mobile apps, not desktop apps on Windows/Linux specifically, and there's no independent hands-on confirmation of passkey sync working seamlessly across all five named platforms. Missing for 10: explicit desktop (Windows/Linux) passkey autofill documentation, and independent/community verification of cross-platform passkey sync reliability.

   • [claimed-docs] “Save passkeys in your Bitwarden vault and use the browser extension or mobile apps to autofill them across the apps and websites you use eve…”

   proof ↗⚑ flag

   Ente Auth—none0/10

   Ente Auth is a TOTP/2FA code manager; the only passkey mention in evidence (doc-14) refers to passkey login for the separate Ente Photos account, not Ente Auth storing/syncing passkeys as credentials across iOS/Android/Windows/Linux/browsers. No evidence shows Ente Auth itself functions as a cross-platform passkey vault.

   • [claimed-docs] “Ente also offers [Legacy](/help/photos/features/legacy/) (emergency contacts) and support for [Passkeys](/help/photos/features/passkeys).”
   • [claimed-docs] “Auth has an app for every platform. Mobile, desktop and web. Your codes sync across all your devices, end-to-end encrypted.”

   proof ↗⚑ flag

Export

1. power userExport all my TOTP secrets in an open, readable format and leave for another app whenever I choose — no lock-in

   weight 3 · round to Bitwarden
   Bitwarden~partialclaimed4/10

   Bitwarden documents a general vault export (JSON/CSV) for 'logins and notes' and back-up/transfer purposes, but the evidence never explicitly confirms that TOTP secrets are included in that export or specifies an open, human-readable format for them — only import paths for other authenticators (Google Authenticator QR, LastPass JSON, 2FAS) are detailed, which is the opposite direction (lock-in mitigation on entry, not exit). Missing for 10: explicit confirmation that TOTP seeds are present in the standard export file, documentation of the exact readable TOTP export format, and any independent/hands-on verification that exported TOTP secrets can be reimported elsewhere.

   • [claimed-docs] “Export your vault data, including logins and notes, to back up important information or transfer to a new Bitwarden vault.”
   • [claimed-docs] “Export your vault data, including logins and notes, to back up important information or transfer to a new Bitwarden vault”
   • [claimed-docs] “Google Authenticator (QR code): Import from Google Authenticator using a QR code... LastPass (JSON): Import a LastPass Authenticator account…”
   • [claimed-docs] “Google Authenticator (QR code): Import from Google Authenticator using a QR code... LastPass (JSON): Import a LastPass Authenticator account…”

   proof ↗⚑ flag

   Ente Auth!disputedcontradicted4/10

   Ente Auth does offer local encrypted backups and a CLI ('ente-cli') that can export and decrypt Auth data (docs-8/9/11, probe-rt-1), and Authy-specific tooling explicitly produces a 'plaintext export format' for importing into Ente (docs-5/40) — but this is import-facing, not an open export for leaving Ente. A hands-on community report explicitly states the opposite of the 'no lock-in' claim: 'You cant easily export your codes into a different format using this app, meaning that it is difficult to migrate away once you have already moved your codes over' (comm-2), while other users only describe importing into Ente, not exporting out to a different app's format. Missing for 10: documented open/standard export format usable directly by other authenticator apps, and independent confirmation that migrating away (not just in) is easy.

   • [claimed-docs] “Automatic daily backups: When enabled, Ente Auth creates one local backup per day when you open the app.”
   • [claimed-docs] “Password-protected: All local backups are encrypted with a password you set. Keep this password safe, because Ente cannot recover it for you…”
   • [claimed-docs] “You can use [Ente's CLI](https://github.com/ente/ente/tree/main/cli#readme) to automatically backup your Auth codes.”
   • [claimed-docs] “you should type this for MacOS... This will generate a text file called authy_codes.txt, which contains your Authy codes in Ente's plaintext…”
   • [probe] “PROBE runtime (recorded 2026-09-15): Ente's official CLI is packaged in Homebrew as ente-cli 0.3.0, described by the formula itself as 'Util…”
   • [community] “I'm waiting for bitwarden or aegis export capability before trying this out. You cant easily export your codes into a different format using…”
   • [community] “Ente has free backups and it's own encrypted export format, which sounds promissing.”

   proof ↗⚑ flag

Import

1. power userImport tokens in bulk from other authenticator apps instead of re-enrolling every account by hand

   weight 2 · round to Ente Auth
   Bitwarden✓fullclaimed8/10

   Bitwarden's official docs explicitly support bulk import of TOTP/authenticator tokens from Google Authenticator (QR), LastPass Authenticator (JSON), and 2FAS (.2fas) backups, directly enabling power users to migrate accounts without re-enrolling each one by hand. This is a first-party, documented dedicated import flow, not a workaround. missing for 10: independent hands-on confirmation of the bulk import UX working smoothly, and coverage of additional popular authenticator export formats (e.g., Authy, Microsoft Authenticator).

   • [claimed-docs] “Google Authenticator (QR code): Import from Google Authenticator using a QR code... LastPass (JSON): Import a LastPass Authenticator account…”
   • [claimed-docs] “Google Authenticator (QR code): Import from Google Authenticator using a QR code... LastPass (JSON): Import a LastPass Authenticator account…”

   proof ↗⚑ flag

   Ente Auth✓fullcommunity9/10

   Ente Auth has a dedicated bulk-import feature and docs listing native support for many 2FA providers (2FAS, Aegis, andOTP, Bitwarden, Google Authenticator, LastPass, Proton, Raivo OTP) plus conversion paths for others like Authy, with community testimony confirming easy export/import migration from Aegis. missing for 10: no independent hands-on walkthrough of the bulk-import UI itself, only docs and one community mention.

   • [claimed-docs] “Ente Auth natively supports imports from many 2FA providers.”
   • [claimed-docs] “Bulk import from other 2FA apps”
   • [claimed-docs] “2FAS Authenticator * Aegis Authenticator * andOTP (including encrypted backups, except MOTP) * Bitwarden * Google Authenticator * …”
   • [claimed-docs] “you might be still able to import from them by first converting the data from your old provider into these plaintext files and then importin…”
   • [claimed-docs] “you should type this for MacOS... This will generate a text file called authy_codes.txt, which contains your Authy codes in Ente's plaintext…”
   • [community] “I have been using Aegis but switched to Ente Auth as I decided to use Ente Photos as well. Both Aegis and Ente Auth are great options. This …”

   proof ↗⚑ flag

Migration

1. everyday userMoving to a new phone transfers all my tokens in one guided step

   weight 2 · round to Ente Auth
   Bitwarden~partialcommunity6/10

   Bitwarden's cloud vault syncs logins, passkeys, and TOTP codes across devices automatically (docs-1, docs-2, docs-4), so logging into a new phone with the same account would pull in tokens without manual export/import — effectively delivering the outcome. However, no evidence describes a dedicated 'guided' new-device setup wizard, and one community report (bitwarden-comm-9) describes lost generated data tied to connectivity issues, raising reliability caveats for a seamless one-step transfer. Missing for 10: documented guided device-migration flow/wizard, and independent hands-on confirmation that TOTP/passkeys transfer flawlessly to a new phone.

   • [claimed-docs] “it automatically produces the time-based one-time passwords (TOTPs), six-digit codes using SHA-1 that rotate every 30 seconds”
   • [claimed-docs] “Connect Authenticator with Password Manager to sync your verification codes. Once activated, the Bitwarden apps stay synchronized with any c…”
   • [claimed-docs] “Save passkeys in your Bitwarden vault and use the browser extension or mobile apps to autofill them across the apps and websites you use eve…”
   • [community] “I tried switching to Bitwarden and forced myself to live with it for 3 months. I gave up when it lost generated password. Apparently it is q…”

   proof ↗⚑ flag

   Ente Auth✓fullprobed7/10

   Ente Auth syncs codes end-to-end encrypted across all devices (docs-27, docs-34), so on a new phone a user simply logs into their existing account and their tokens reappear automatically—effectively a single guided step. Community feedback corroborates that switching devices via export/import was 'very easy' (ente-auth-comm-6), and offline-mode users can restore via password-protected local/CLI backups (docs-7, docs-8, docs-9, docs-11, ente-auth-probe-rt-1). Missing for 10: no explicit first-party step-by-step 'new phone setup/restore' walkthrough, and no independent hands-on account of the exact new-device login-and-sync flow.

   • [claimed-docs] “Auth has an app for every platform. Mobile, desktop and web. Your codes sync across all your devices, end-to-end encrypted.”
   • [claimed-docs] “Auth provides end-to-end encrypted cloud backups so you don't have to worry about losing your tokens.”
   • [claimed-docs] “Ente Auth can be used without an account by choosing **Use without backups**. In offline mode, your codes are stored only on that device.”
   • [claimed-docs] “Automatic daily backups: When enabled, Ente Auth creates one local backup per day when you open the app.”
   • [claimed-docs] “You can use [Ente's CLI](https://github.com/ente/ente/tree/main/cli#readme) to automatically backup your Auth codes.”
   • [community] “I have been using Aegis but switched to Ente Auth as I decided to use Ente Photos as well. Both Aegis and Ente Auth are great options. This …”
   • [probe] “PROBE runtime (recorded 2026-09-15): Ente's official CLI is packaged in Homebrew as ente-cli 0.3.0, described by the formula itself as 'Util…”

   proof ↗⚑ flag

1. ai-native userChoose where my data is stored (region/residency)

   weight 2 · round to Ente Auth
   Bitwarden—none0/10

   No evidence pack item mentions data residency, region selection, or self-hosting for regional compliance beyond a generic on-premise Linux install guide, which does not address choosing a storage region. Missing for 10: any documentation of region/data-residency selection (e.g., EU vs US data centers), enterprise residency options, or explicit control over where vault data is stored.

   ⚑ flag

   Ente Auth~partialprobed5/10

   Ente Auth offers self-hosting instructions (running your own Ente Auth server) and an offline mode that keeps codes only on-device, both of which let a user control where their data lives rather than being forced into a fixed cloud region. However, there's no explicit region/residency selection (e.g., choosing an EU vs US data center) for its hosted cloud service. Missing for 10: explicit multi-region cloud storage options, documented data-residency guarantees for the hosted service.

   • [claimed-docs] “Alternatively, if using Ente Auth, get started by adding an account (assuming you are running Ente Auth at `http://<machine-ip>:3003` or `ht…”
   • [claimed-docs] “Ente Auth can be used without an account by choosing **Use without backups**. In offline mode, your codes are stored only on that device.”
   • [probe] “PROBE llms.txt: HTTP 200 at https://ente.com/llms.txt # Ente > Ente builds private, end-to-end encrypted apps for photos, two-factor authen…”

   proof ↗⚑ flag

2. ai-native userPrevent my data from being used to train AI models

   weight 3 · round to Ente Auth
   Bitwarden—none0/10

   The evidence pack contains no documentation, policy statement, or setting from Bitwarden addressing whether vault data or user data is used to train AI models, nor any opt-out mechanism for such use. This is a fair privacy-posture question for a SaaS handling sensitive personal data, but nothing in the pack confirms or denies a stance, so it cannot be credited as delivered.

   ⚑ flag

   Ente Auth~partialprobed5/10

   Ente Auth stores codes with end-to-end encryption, meaning Ente itself cannot access plaintext data, which structurally prevents it from being used to train AI models — but there is no explicit policy statement addressing AI training use of data. Missing for 10: an explicit AI-training data-use policy/statement, and any independent confirmation of this posture beyond the general E2E encryption claim.

   • [claimed-docs] “Auth provides end-to-end encrypted cloud backups so you don't have to worry about losing your tokens.”
   • [claimed-docs] “the data is encrypted using a key derived from the user's password”
   • [probe] “PROBE docs-md: HTTP 404 at https://ente.com/help/auth/.md”

   proof ↗⚑ flag

3. ai-native userControl data retention and deletion

   weight 2 · round to Ente Auth
   Bitwarden~partialcommunity3/10

   Bitwarden docs show users can export their vault data (for backup or account transfer) and community evidence indicates an account-deletion path exists (export → delete account → recreate), but there is no dedicated, first-party documentation on data retention policies, granular deletion controls, or how these apply to AI/agent access (e.g., MCP server or CLI-served vault data). Missing for 10: explicit retention policy documentation, dedicated account/vault deletion docs, and clarity on data lifecycle when accessed via CLI/MCP for AI agents.

   • [claimed-docs] “Export your vault data, including logins and notes, to back up important information or transfer to a new Bitwarden vault.”
   • [claimed-docs] “Export your vault data, including logins and notes, to back up important information or transfer to a new Bitwarden vault”
   • [community] “BitWarden has lost the trust. There was a blocker bug on iOS, they went radio silent on follow-ups, and their fix suggestion was 'export dat…”

   proof ↗⚑ flag

   Ente Auth~partialprobed7/10

   Ente Auth lets users delete/trash codes with recovery or permanent deletion (docs-18/33/38), control backup location and encryption (docs-9/10), run fully offline with no cloud retention (doc-7), and export/decrypt all data via the official CLI for full portability (docs-11, probe-rt-1). However there's no explicit documentation on cloud-side account/data deletion policies or retention periods for encrypted server backups. Missing for 10: documented cloud account deletion/retention policy, independent confirmation of full data erasure on request.

   • [claimed-docs] “You can now trash codes that you don't need. ... You can recover codes from here, in case of accidental deletions, or delete them permanentl…”
   • [claimed-docs] “You can delete or edit a code by long pressing (or right clicking on desktop) on that item.”
   • [claimed-docs] “You can now trash codes that you don't need. These items will be moved to a separate section within the app, under the "Trash" header.”
   • [claimed-docs] “Ente Auth can be used without an account by choosing **Use without backups**. In offline mode, your codes are stored only on that device.”
   • [claimed-docs] “Password-protected: All local backups are encrypted with a password you set. Keep this password safe, because Ente cannot recover it for you…”
   • [claimed-docs] “Custom backup location: Choose where to store your backups on your device.”
   • [claimed-docs] “You can use [Ente's CLI](https://github.com/ente/ente/tree/main/cli#readme) to automatically backup your Auth codes.”
   • [probe] “PROBE runtime (recorded 2026-09-15): Ente's official CLI is packaged in Homebrew as ente-cli 0.3.0, described by the formula itself as 'Util…”

   proof ↗⚑ flag

4. ai-native userOpt out of telemetry and usage tracking

   weight 2 · round drawn
   Bitwarden—none0/10

   The evidence pack contains no documentation, settings, or community reports describing a telemetry/usage-tracking opt-out control in Bitwarden clients, CLI, or self-hosted server. While the axis is fair to ask of any privacy-focused product, nothing here confirms such a toggle exists or how it works.

   ⚑ flag

   Ente Auth—none0/10

   No evidence pack mentions any telemetry, analytics, or usage-tracking settings, opt-out toggles, or privacy policy statements about data collection in Ente Auth; the evidence covers import/export, backups, and sync features only.

   ⚑ flag

App lock

1. everyday userThe app itself locks behind biometrics or a PIN, so a borrowed phone doesn't expose my codes

   weight 2 · round to Ente Auth
   Bitwarden~partialcommunity3/10

   No official documentation in the evidence pack describes a PIN/biometric app-lock feature; the only signal is an indirect community comment implying fingerprint unlock already exists on some platforms but is missing on Linux, which weakly corroborates the capability without detailing scope or coverage. Missing for 10: first-party docs on biometric/PIN unlock, mobile-specific confirmation, and independent hands-on validation of the lock behavior.

   • [community] “Yeah it's nice and all but I wish they brought fingerprint auth to Linux already.”

   proof ↗⚑ flag

   Ente Auth✓fullclaimed8/10

   Docs explicitly confirm FaceID lock (Settings → Security → Lockscreen) and a custom lock screen supporting PINs and passwords, directly matching the story's biometric/PIN app-lock requirement. missing for 10: no independent/hands-on confirmation that the lock actually blocks access on a borrowed device, and no mention of Android biometric or desktop lock parity beyond FaceID/PIN.

   • [claimed-docs] “You can enable FaceID lock under Settings → Security → Lockscreen.”
   • [claimed-docs] “You can now further protect your codes with a custom lock screen that supports PINs and passwords.”

   proof ↗⚑ flag

Audits

1. security engineerThe vendor publishes independent security audits of the app and its sync protocol

   weight 2 · round drawn
   Bitwarden—none0/10

   No evidence pack items reference independent third-party security audits, penetration tests, or cryptographic/protocol reviews of Bitwarden's app or sync protocol; the pack only covers docs on features (TOTP, autofill, CLI, import/export) and community sentiment/complaints unrelated to audits. Missing for 10: published audit reports (e.g., Cure53), audit scope/dates, sync protocol review findings, remediation disclosures.

   ⚑ flag

   Ente Auth—none0/10

   No evidence pack item references any independent security audit of Ente Auth or its sync protocol; documentation focuses on features, encryption claims, and migration, not third-party audit reports.

   ⚑ flag

Monitoring

1. power userThe app warns me when a service I use is breached or a stored credential is weak, reused, or exposed

   weight 2 · round to Bitwarden
   Bitwarden~partialclaimed5/10

   Bitwarden's Vault Health Reports (docs-11/17) explicitly check for reused and weak passwords locally on the client, covering part of the story, but no evidence in the pack documents breach monitoring (e.g., known data-breach alerts) or an 'exposed passwords' check against breach databases. Missing for 10: evidence of breach/exposure alerts for compromised services, and any exposed-credential detection feature.

   • [claimed-docs] “Vault health reports can help you evaluate the security of your Bitwarden individual or organization vault... Reports... are run locally on …”
   • [claimed-docs] “Vault health reports can help you evaluate the security of your Bitwarden individual or organization vault. Reports, such as the Reused Pass…”

   proof ↗⚑ flag

   Ente Auth—none0/10

   Ente Auth is a TOTP/HOTP authenticator app; nothing in the evidence pack shows breach-monitoring, weak/reused-credential detection, or exposure alerts — its documented features are around code storage, import/export, sharing, and lockscreen security.

   ⚑ flag

Push

1. it adminPush-based sign-in includes phishing defenses — number matching, location context, and admin-enforced MFA policies

   weight 2 · round drawn
   Bitwarden—none0/10

   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". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

   Ente Auth—none0/10

   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". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

Server

1. it adminSelf-host the sync server on my own infrastructure and keep every secret inside my perimeter

   weight 2 · round to Bitwarden
   Bitwarden✓fullclaimed8/10

   Bitwarden provides official documentation for installing and deploying the self-hosted server on a Linux server, keeping vault data on the admin's own infrastructure — the core of this story. Missing for 10: independent hands-on verification of a real-world self-hosted deployment and details on ongoing maintenance/upgrade complexity for self-hosted instances.

   • [claimed-docs] “This article will walk you through the procedure to install and deploy Bitwarden to your own Linux server.”

   proof ↗⚑ flag

   Ente Auth~partialprobed6/10

   Ente explicitly documents running the Auth server locally (e.g. at http://localhost:3003) and its server code is confirmed open source, supporting self-hosting for IT admins wanting to keep secrets in-perimeter. However, the evidence pack lacks detailed self-hosting setup docs (Docker/compose instructions, hardware requirements, upgrade/security guidance) and no independent community reports specifically about self-hosting the Auth server (only cloud usage is discussed in community threads). Missing for 10: full self-hosting deployment guide, independent hands-on verification of self-hosted Auth server, and security/perimeter assurances specific to self-hosted mode.

   • [claimed-docs] “Alternatively, if using Ente Auth, get started by adding an account (assuming you are running Ente Auth at `http://<machine-ip>:3003` or `ht…”
   • [probe] “PROBE runtime (recorded 2026-09-15): ente.com serves a live llms.txt — '# Ente — Ente builds private, end-to-end encrypted apps for photos, …”
   • [probe] “PROBE llms.txt: HTTP 200 at https://ente.com/llms.txt # Ente > Ente builds private, end-to-end encrypted apps for photos, two-factor authen…”

   proof ↗⚑ flag

Source

1. security engineerThe client apps are open source, so the code handling my seeds can be inspected and community-reviewed

   weight 2 · round to Ente Auth
   Bitwarden~partialprobed6/10

   Bitwarden markets itself as 'the most trusted open source password manager' and community members explicitly cite open-source clients as the reason they trust it with secrets (bitwarden-probe-1, bitwarden-comm-15). However, the evidence also documents a real controversy where SDK code (used by clients) was briefly relicensed away from a fully open license before being reverted after community pressure, which shows scrutiny worked but also that openness has not always been airtight (bitwarden-comm-1, bitwarden-comm-3, bitwarden-comm-4). Missing for 10: direct links to client-app GitHub repos, explicit confirmation that seed/TOTP-handling code specifically is open and audited, and independent third-party code audits corroborating the open-source claim.

   • [probe] “PROBE llms.txt: HTTP 200 at https://bitwarden.com/llms.txt # Bitwarden > The most trusted open source password manager for passwords, passk…”
   • [community] “I use BitWarden because I'd never trust a password manager with closed source clients... Needless to say I move to the next ethical e2ee pas…”
   • [community] “Props for them to step in the right direction, it wasn’t obvious at all for a few days what they would do (re: SDK relicensing controversy).”
   • [community] “Thank you to Bitwarden for relicensing back to Free/Open License... I no longer recommend Bitwarden for normal people because the built-in p…”
   • [community] “I’m relieved... I hope they realized that being FOSS is their moat... I’m still not sure how I feel about them now. Trust in the company has…”

   proof ↗⚑ flag

   Ente Auth✓fullprobed7/10

   Ente's own llms.txt explicitly states 'Ente's apps and server are open source,' and a community poster on HN independently confirms 'thank you for releasing it open source,' corroborating that the client code is publicly available for inspection. Missing for 10: a direct link/reference to the actual auth client source repo, and independent evidence of community security review or audits of the seed-handling code.

   • [probe] “PROBE runtime (recorded 2026-09-15): ente.com serves a live llms.txt — '# Ente — Ente builds private, end-to-end encrypted apps for photos, …”
   • [community] “This looks quite nice, thank you for releasing it open source... One note as I signed up for an account is that the email verification went …”

   proof ↗⚑ flag

Automation

1. ai-native userAn agent can fetch a current TOTP code programmatically — via CLI or API — to complete a 2FA login inside an automated workflow

   weight 2 · round to Bitwarden
   Bitwarden✓fullprobed8/10

   Bitwarden's integrated authenticator generates TOTP codes (bitwarden-docs-1) and the CLI is documented as a full vault-management tool suitable for automated workflows via personal API key (bitwarden-docs-7, bitwarden-docs-9); runtime probes confirm 'bw serve' exposes a local REST Vault Management API and an official MCP server completes a full handshake, both surfaces an agent could use to fetch TOTP codes programmatically (bitwarden-probe-rt-1, bitwarden-probe-rt-2). Hands-on community evidence independently corroborates that 'bw list' actually returns current TOTP codes in plaintext, confirming the CLI does return live TOTP data (bitwarden-comm-13). Missing for 10: explicit documentation naming a dedicated 'get totp' command/API endpoint and a clean (non-complaint) hands-on workflow example.

   • [claimed-docs] “it automatically produces the time-based one-time passwords (TOTPs), six-digit codes using SHA-1 that rotate every 30 seconds”
   • [claimed-docs] “The Bitwarden command-line interface (CLI) is a powerful, fully-featured tool for accessing and managing your vault.”
   • [claimed-docs] “Using the personal API key for CLI authentication is suitable for automated workflows, for providing access to an external appli”
   • [probe] “PROBE runtime (recorded 2026-09-15): the official bw CLI installs keylessly from npm (@bitwarden/cli, registry latest 2026.8.0) and prints i…”
   • [probe] “PROBE runtime (recorded 2026-09-15): Bitwarden's OFFICIAL MCP server completed a FULL keyless stdio initialize handshake — `npx -y @bitwarde…”
   • [community] “I had a really bad experience with the bitwarden cli. I ran 'bw list', assuming it would list names, but it listed everything including pass…”

   proof ↗⚑ flag

   Ente Auth—none0/10

   Evidence only shows a CLI for exporting/backing up and decrypting Ente Auth data (ente-auth-docs-11, ente-auth-probe-rt-1), not for programmatically retrieving a live/current TOTP code for use in an automated 2FA login. No API, CLI subcommand, or docs describe generating a real-time code for agent consumption.

   • [claimed-docs] “You can use [Ente's CLI](https://github.com/ente/ente/tree/main/cli#readme) to automatically backup your Auth codes.”
   • [probe] “PROBE runtime (recorded 2026-09-15): Ente's official CLI is packaged in Homebrew as ente-cli 0.3.0, described by the formula itself as 'Util…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://ente.com/openapi.json, https://ente.com/swagger.json, https://ente.com/api/openapi.json, htt…”

   proof ↗⚑ flag

2. ai-native userExpose the vault through a local programmatic endpoint an agent can query for codes and secrets without screen-scraping the app

   weight 1 · round to Bitwarden
   Bitwarden✓fullprobed8/10

   Bitwarden's CLI supports a documented `bw serve` mode exposing the vault as a local RESTful API, and Bitwarden ships an official MCP server (bitwarden/mcp-server) that completed a live stdio handshake, both giving agents programmatic access to vault items and TOTP codes without screen-scraping. missing for 10: no independent hands-on validation of `bw serve` specifically for TOTP retrieval by an agent, and no broader third-party corroboration beyond the vendor-run probes.

   • [probe] “PROBE runtime (recorded 2026-09-15): the official bw CLI installs keylessly from npm (@bitwarden/cli, registry latest 2026.8.0) and prints i…”
   • [probe] “PROBE runtime (recorded 2026-09-15): Bitwarden's OFFICIAL MCP server completed a FULL keyless stdio initialize handshake — `npx -y @bitwarde…”
   • [probe] “official MCP server documented at https://github.com/bitwarden/mcp-server”
   • [claimed-docs] “The Bitwarden command-line interface (CLI) is a powerful, fully-featured tool for accessing and managing your vault.”

   proof ↗⚑ flag

   Ente Auth—none0/10

   No evidence of any local API, IPC endpoint, or programmatic interface for querying codes; the only related tooling is the export/backup CLI (docs-11, probe-rt-1), which produces files rather than a queryable local endpoint an agent could hit live. No OpenAPI/local server documentation was found (probe-3 confirms no openapi endpoint).

   • [claimed-docs] “You can use [Ente's CLI](https://github.com/ente/ente/tree/main/cli#readme) to automatically backup your Auth codes.”
   • [probe] “PROBE runtime (recorded 2026-09-15): Ente's official CLI is packaged in Homebrew as ente-cli 0.3.0, described by the formula itself as 'Util…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://ente.com/openapi.json, https://ente.com/swagger.json, https://ente.com/api/openapi.json, htt…”

   proof ↗⚑ flag

Browser

1. everyday userA browser extension autofills my TOTP codes and passkeys during login instead of making me retype them

   weight 2 · round to Bitwarden
   Bitwarden✓fullcommunity8/10

   Docs confirm browser extension autofills matching credentials on login pages (docs-12), autofills stored passkeys across apps/websites (docs-4), and generates/syncs TOTP codes (docs-1, docs-2) which are surfaced during autofill in the extension. One community mention notes TOTP setup friction, but no concrete evidence contradicts the core autofill-of-TOTP/passkeys capability. Missing for 10: independent hands-on confirmation specifically that TOTP codes (not just passwords/passkeys) are auto-filled into login forms without manual copy-paste.

   • [claimed-docs] “When you visit a website, the browser extension recognizes it and enters matching credentials from your vault into the login fields.”
   • [claimed-docs] “Save passkeys in your Bitwarden vault and use the browser extension or mobile apps to autofill them across the apps and websites you use eve…”
   • [claimed-docs] “it automatically produces the time-based one-time passwords (TOTPs), six-digit codes using SHA-1 that rotate every 30 seconds”
   • [claimed-docs] “Connect Authenticator with Password Manager to sync your verification codes. Once activated, the Bitwarden apps stay synchronized with any c…”
   • [community] “I always enjoyed the value that Bitwarden provides: free to use, password generator, and a vault to keep other texts. But somehow I never go…”

   proof ↗⚑ flag

   Ente Auth—none0/10

   No evidence of a browser extension for Ente Auth; the product is described as apps for mobile, desktop and web with manual QR-scan/setup-key entry, not autofill via a browser extension for TOTP or passkeys during login.

   ⚑ flag

Desktop

1. power userA first-class desktop app gives me codes and vault access on my computer, not just on mobile

   weight 2 · round to Ente Auth
   Bitwarden~partialprobed5/10

   Evidence confirms TOTP codes sync across 'Bitwarden apps' and vault access is available via browser extension and CLI on a computer, implying desktop-class access, but no citation explicitly documents a native desktop application (GUI) separate from the browser extension/CLI. Missing for 10: explicit desktop app documentation, screenshots/feature parity claims, and independent confirmation that a first-class desktop GUI (not just extension/CLI) exists and works well.

   • [claimed-docs] “it automatically produces the time-based one-time passwords (TOTPs), six-digit codes using SHA-1 that rotate every 30 seconds”
   • [claimed-docs] “Connect Authenticator with Password Manager to sync your verification codes. Once activated, the Bitwarden apps stay synchronized with any c…”
   • [claimed-docs] “The Bitwarden command-line interface (CLI) is a powerful, fully-featured tool for accessing and managing your vault.”
   • [claimed-docs] “When you visit a website, the browser extension recognizes it and enters matching credentials from your vault into the login fields.”
   • [probe] “PROBE runtime (recorded 2026-09-15): the official bw CLI installs keylessly from npm (@bitwarden/cli, registry latest 2026.8.0) and prints i…”

   proof ↗⚑ flag

   Ente Auth✓fullcommunity7/10

   Ente Auth explicitly ships native desktop clients (Flathub Linux app, plus 'app for every platform: Mobile, desktop and web' with full sync) and desktop-specific UI features like right-click code editing, matching a first-class desktop experience; a HN user corroborates switching to it specifically for its desktop app after Authy dropped theirs. missing for 10: explicit list/docs of Windows/Mac desktop builds beyond Flathub, and an independent hands-on review confirming full feature parity with mobile.

   • [claimed-docs] “Auth is now officially available on [Flathub](https://flathub.org/apps/io.ente.auth)!”
   • [claimed-docs] “Auth has an app for every platform. Mobile, desktop and web. Your codes sync across all your devices, end-to-end encrypted.”
   • [claimed-docs] “You can delete or edit a code by long pressing (or right clicking on desktop) on that item.”
   • [community] “Ente Auth is awesome - I've been using it ever since Authy discontinued their desktop app.”

   proof ↗⚑ flag

Watch

1. everyday userRead my codes from my smartwatch without pulling out my phone

   weight 1 · round drawn
   Bitwarden—none0/10

   The evidence pack covers TOTP generation, syncing, browser extension, CLI, and API features, but contains no mention of a smartwatch app, Wear OS/watchOS companion, or any glanceable code display for wearables. This is a fair capability question for a password manager with a built-in authenticator, but no evidence shows it is delivered.

   ⚑ flag

   Ente Auth—none0/10

   The evidence pack covers mobile/desktop/web platform support, import/export, sharing, and lockscreen features, but contains no mention of smartwatch (e.g. Wear OS, watchOS) support or companion app for viewing codes without pulling out a phone.

   ⚑ flag

Backup

1. security engineerBackups are end-to-end encrypted with a key the vendor never holds, and the encryption design is documented

   weight 3 · round to Ente Auth
   Bitwarden~partialclaimed4/10

   Docs confirm Bitwarden supports vault export/import and mention an 'encrypted exports' option (bitwarden-docs-5, bitwarden-docs-6, bitwarden-docs-16), implying some backups can be encrypted, but no evidence pack item documents the underlying encryption design, key derivation, or explicitly states the vendor cannot access backup contents. missing for 10: a linked security whitepaper or architecture doc describing zero-knowledge key management for exports, explicit vendor-can't-decrypt-backups statement, and independent verification of the encrypted export format.

   • [claimed-docs] “Export your vault data, including logins and notes, to back up important information or transfer to a new Bitwarden vault.”
   • [claimed-docs] “Import logins and data from different password managers, other Bitwarden vaults, or encrypted exports to instantly transfer your information…”
   • [claimed-docs] “Export your vault data, including logins and notes, to back up important information or transfer to a new Bitwarden vault”

   proof ↗⚑ flag

   Ente Auth~partialprobed6/10

   Ente docs state cloud backups are end-to-end encrypted (docs-27, docs-34) and local backups are encrypted with a password-derived key that Ente cannot recover (docs-9, docs-12), plus open-source apps/server are confirmed (probe-rt-2), supporting a 'vendor never holds key' claim. However there is no detailed cryptographic design doc (key derivation algorithm, protocol specifics, audit report) in the evidence, only high-level marketing/FAQ statements. Missing for 10: a published encryption whitepaper or technical spec, and independent security audit/corroboration of the E2E design.

   • [claimed-docs] “Auth has an app for every platform. Mobile, desktop and web. Your codes sync across all your devices, end-to-end encrypted.”
   • [claimed-docs] “Auth provides end-to-end encrypted cloud backups so you don't have to worry about losing your tokens.”
   • [claimed-docs] “Password-protected: All local backups are encrypted with a password you set. Keep this password safe, because Ente cannot recover it for you…”
   • [claimed-docs] “the data is encrypted using a key derived from the user's password”
   • [probe] “PROBE runtime (recorded 2026-09-15): ente.com serves a live llms.txt — '# Ente — Ente builds private, end-to-end encrypted apps for photos, …”

   proof ↗⚑ flag

Multi device

1. everyday userMy tokens are available on my phone, tablet, and computer at the same time, kept in sync automatically

   weight 2 · round to Ente Auth
   Bitwarden!disputedcontradicted6/10

   Bitwarden's docs describe cloud-based vault sync (TOTP codes staying synchronized across apps, passkeys usable across browser extension and mobile apps, auto-fill working consistently) which underlies cross-device availability of stored items (bitwarden-docs-2, bitwarden-docs-4, bitwarden-docs-12). However, a hands-on community report describes losing a generated password due to sync failures on bad connections, calling it 'quite common' (bitwarden-comm-9), directly contradicting the claim of seamless automatic sync. missing for 10: independent verification of reliable real-time sync across phone/tablet/computer simultaneously, and resolution/acknowledgment of the reported data-loss-on-sync issue.

   • [claimed-docs] “Connect Authenticator with Password Manager to sync your verification codes. Once activated, the Bitwarden apps stay synchronized with any c…”
   • [claimed-docs] “Save passkeys in your Bitwarden vault and use the browser extension or mobile apps to autofill them across the apps and websites you use eve…”
   • [claimed-docs] “When you visit a website, the browser extension recognizes it and enters matching credentials from your vault into the login fields.”
   • [community] “I tried switching to Bitwarden and forced myself to live with it for 3 months. I gave up when it lost generated password. Apparently it is q…”

   proof ↗⚑ flag

   Ente Auth✓fullcommunity8/10

   Ente Auth explicitly advertises multi-platform apps (mobile, desktop, web) with end-to-end encrypted cloud sync so codes stay in sync across devices, and community evidence corroborates real-world use across app switches without complaint about sync failures. Missing for 10: independent hands-on confirmation of real-time multi-device sync latency/reliability and any edge-case sync bugs reported by users.

   • [claimed-docs] “Auth has an app for every platform. Mobile, desktop and web. Your codes sync across all your devices, end-to-end encrypted.”
   • [claimed-docs] “Auth provides end-to-end encrypted cloud backups so you don't have to worry about losing your tokens.”
   • [community] “Ente Auth is awesome - I've been using it ever since Authy discontinued their desktop app.”
   • [community] “I have been using Aegis but switched to Ente Auth as I decided to use Ente Photos as well. Both Aegis and Ente Auth are great options. This …”

   proof ↗⚑ flag

Recovery

1. everyday userLosing my phone doesn't lose my accounts — a documented recovery path restores my tokens on a new device

   weight 3 · round to Ente Auth
   Bitwarden~partialcommunity6/10

   Bitwarden's docs show that TOTP codes are synced across the Bitwarden apps (docs-2) and that vault data (including logins) can be exported/imported to restore to a new install (docs-5, docs-6), which together give a de facto path to recover accounts/tokens on a new device after losing a phone. However there is no explicit 'lost my phone' recovery guide, and community reports mention TOTP/sync reliability problems (bitwarden-comm-12, bitwarden-comm-9) that add real-world caveats. Missing for 10: a dedicated 'device loss/account recovery' doc, evidence of automatic cloud vault sync restoring a fresh install without manual export/import, and confirmation that community-reported sync/TOTP glitches don't block this flow.

   • [claimed-docs] “Connect Authenticator with Password Manager to sync your verification codes. Once activated, the Bitwarden apps stay synchronized with any c…”
   • [claimed-docs] “Export your vault data, including logins and notes, to back up important information or transfer to a new Bitwarden vault.”
   • [claimed-docs] “Import logins and data from different password managers, other Bitwarden vaults, or encrypted exports to instantly transfer your information…”
   • [community] “I always enjoyed the value that Bitwarden provides: free to use, password generator, and a vault to keep other texts. But somehow I never go…”
   • [community] “I tried switching to Bitwarden and forced myself to live with it for 3 months. I gave up when it lost generated password. Apparently it is q…”

   proof ↗⚑ flag

   Ente Auth✓fullprobed8/10

   Ente Auth documents end-to-end encrypted cloud sync/backups so codes restore on a new device after login, plus a recovery key to bypass 2FA lockouts, local encrypted backups, and a CLI export tool as additional restore paths. missing for 10: no independent hands-on account of a real device-loss recovery walkthrough, and no detail on exact steps to restore cloud-synced codes on a fresh device beyond general sync claims.

   • [claimed-docs] “Auth has an app for every platform. Mobile, desktop and web. Your codes sync across all your devices, end-to-end encrypted.”
   • [claimed-docs] “Auth provides end-to-end encrypted cloud backups so you don't have to worry about losing your tokens.”
   • [claimed-docs] “We recommend that you ensure you store your recovery key in a safe place (writing it down on a paper is a good idea). This key can be used t…”
   • [claimed-docs] “Automatic daily backups: When enabled, Ente Auth creates one local backup per day when you open the app.”
   • [claimed-docs] “Password-protected: All local backups are encrypted with a password you set. Keep this password safe, because Ente cannot recover it for you…”
   • [claimed-docs] “You can use [Ente's CLI](https://github.com/ente/ente/tree/main/cli#readme) to automatically backup your Auth codes.”
   • [probe] “PROBE runtime (recorded 2026-09-15): Ente's official CLI is packaged in Homebrew as ente-cli 0.3.0, described by the formula itself as 'Util…”
   • [community] “Ente has free backups and it's own encrypted export format, which sounds promissing.”

   proof ↗⚑ flag

Automation

1. ai-native userAn agent can create and update vault entries — seeding new TOTP secrets, storing credentials — through documented programmatic surfaces

   weight 2 · round to Bitwarden
   Bitwarden✓fullprobed7/10

   Bitwarden documents multiple programmatic surfaces for vault management — the fully-featured CLI (which supports create/edit item operations and a `bw serve` mode exposing a local REST API for TOTP/items), a personal API key explicitly recommended for 'automated workflows' and 'external applications,' and an official first-party MCP server that completed a live stdio handshake, giving agents a documented path to create and update vault entries including TOTP secrets. Missing for 10: an explicit doc/code example showing the exact CLI/API call syntax for adding a TOTP field to a new item, and independent (non-vendor) confirmation that an agent successfully created/updated entries end-to-end via these surfaces.

   • [claimed-docs] “The Bitwarden command-line interface (CLI) is a powerful, fully-featured tool for accessing and managing your vault.”
   • [claimed-docs] “Using the personal API key for CLI authentication is suitable for automated workflows, for providing access to an external appli”
   • [probe] “official CLI documented at https://bitwarden.com/help/cli/”
   • [probe] “PROBE runtime (recorded 2026-09-15): the official bw CLI installs keylessly from npm (@bitwarden/cli, registry latest 2026.8.0) and prints i…”
   • [probe] “PROBE runtime (recorded 2026-09-15): Bitwarden's OFFICIAL MCP server completed a FULL keyless stdio initialize handshake — `npx -y @bitwarde…”

   proof ↗⚑ flag

   Ente Auth—none0/10

   Evidence shows only manual QR-scan/setup-key entry, GUI import/export, and a CLI limited to exporting and decrypting backups—no documented API, SDK, or CLI subcommand for programmatically creating or updating vault entries. No OpenAPI/API surface was found (ente-auth-probe-3 confirms no openapi.json), so an agent has no documented programmatic surface to seed or update TOTP secrets.

   • [claimed-docs] “You can use [Ente's CLI](https://github.com/ente/ente/tree/main/cli#readme) to automatically backup your Auth codes.”
   • [probe] “PROBE runtime (recorded 2026-09-15): Ente's official CLI is packaged in Homebrew as ente-cli 0.3.0, described by the formula itself as 'Util…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://ente.com/openapi.json, https://ente.com/swagger.json, https://ente.com/api/openapi.json, htt…”
   • [claimed-docs] “Scan the QR code shown by the service.”
   • [claimed-docs] “Enter the account name, issuer, and secret (setup key).”

   proof ↗⚑ flag

Policy

1. it adminEnforce org-wide policies — require app lock, restrict export, mandate strong master credentials — across every member's app

   weight 1 · round to Bitwarden
   Bitwarden~partialclaimed3/10

   The evidence only shows that Bitwarden's Public API lets organizations manage 'members, collections, groups, event logs, and policies,' implying policy management exists, but there is no documentation shown for specific policies like app-lock enforcement, export restriction, or master-password strength requirements. Missing for 10: explicit documentation of individual policy types (master password strength, disable personal vault export, require app lock/timeout), admin console UI screenshots or workflow, and any hands-on confirmation that these policies are enforced across all members' apps.

   • [claimed-docs] “The Bitwarden Public API provides organizations a suite of tools for managing members, collections, groups, event logs, and policies.”

   proof ↗⚑ flag

   Ente Auth—none0/10

   No evidence of any org-wide admin console, centralized policy enforcement, mandated master password strength, or app lock/export restrictions applied across members — Ente Auth is a personal/individual authenticator with local lock screen (per-device) and personal backup/export options, not a managed enterprise policy tool.

   • [claimed-docs] “You can now further protect your codes with a custom lock screen that supports PINs and passwords.”
   • [claimed-docs] “Password-protected: All local backups are encrypted with a password you set. Keep this password safe, because Ente cannot recover it for you…”
   • [claimed-docs] “You can use [Ente's CLI](https://github.com/ente/ente/tree/main/cli#readme) to automatically backup your Auth codes.”

   proof ↗⚑ flag

Sharing

1. it adminMy team can share TOTP-protected logins through shared vaults or collections with per-member access control

   weight 2 · round to Bitwarden
   Bitwarden~partialcommunity6/10

   Bitwarden's docs confirm built-in TOTP generation/sync (bitwarden-docs-1, bitwarden-docs-2) and its Public API supports managing organization members, collections, and groups (bitwarden-docs-8), and a real-world team user cites 'safer account sharing, including 2FA' as a killer feature (bitwarden-comm-8). However, the evidence pack lacks explicit documentation tying TOTP fields to collection-level per-member permissions/access control, so the granular sharing mechanics aren't directly evidenced. Missing for 10: dedicated docs on collection permission levels (view/edit/manage) applied to TOTP-containing items, and independent confirmation of this exact workflow.

   • [claimed-docs] “it automatically produces the time-based one-time passwords (TOTPs), six-digit codes using SHA-1 that rotate every 30 seconds”
   • [claimed-docs] “Connect Authenticator with Password Manager to sync your verification codes. Once activated, the Bitwarden apps stay synchronized with any c…”
   • [claimed-docs] “The Bitwarden Public API provides organizations a suite of tools for managing members, collections, groups, event logs, and policies.”
   • [community] “We use BitWarden at work, paying $3600/year. Their product is great for teams... The killer feature for me has been safer account sharing, i…”

   proof ↗⚑ flag

   Ente Auth~partialclaimed4/10

   Ente Auth documents sharing individual TOTP codes via temporary, end-to-end encrypted links with teammates (docs-16, docs-35), and explicitly restricts sharing to TOTP (not HOTP) entries (docs-30), which covers the core 'share TOTP logins with team' idea. However there is no evidence of a vault/collection construct or per-member access control (e.g., role-based permissions, group vaults, admin-managed membership) — sharing appears to be per-code link generation rather than an admin-managed shared vault. Missing for 10: evidence of collection/vault-based sharing, per-member access control or roles, and admin management console for team access.

   • [claimed-docs] “You can now easily share specific codes with your team, with temporary links that are end-to-end encrypted.”
   • [claimed-docs] “Share codes with your team securely”
   • [claimed-docs] “Sharing is now limited to TOTP codes; the share option is hidden for HOTP entries.”

   proof ↗⚑ flag

Enrollment

1. everyday userScan a QR code and immediately start generating TOTP codes for a new account

   weight 3 · round to Ente Auth
   Bitwarden~partialcommunity6/10

   Docs confirm Bitwarden's integrated authenticator automatically generates rotating TOTP codes once a key/QR is added to a login item (bitwarden-docs-1, bitwarden-docs-13), which covers the core capability, but the pack lacks explicit documentation of the actual camera-scan-QR flow for a brand-new account (only QR-based *import* from another authenticator app is documented, bitwarden-docs-3/14). One community report also describes difficulty getting TOTP working at all (bitwarden-comm-12), though it's anecdotal and not a concrete reproducible failure. missing for 10: explicit doc/screenshot of scanning a QR to add a brand-new TOTP secret (not import), and independent hands-on confirmation that codes generate immediately after scan.

   • [claimed-docs] “it automatically produces the time-based one-time passwords (TOTPs), six-digit codes using SHA-1 that rotate every 30 seconds”
   • [claimed-docs] “Let's start your Bitwarden browser extension journey by adding a new login item to your vault”
   • [claimed-docs] “Google Authenticator (QR code): Import from Google Authenticator using a QR code... LastPass (JSON): Import a LastPass Authenticator account…”
   • [community] “I always enjoyed the value that Bitwarden provides: free to use, password generator, and a vault to keep other texts. But somehow I never go…”

   proof ↗⚑ flag

   Ente Auth✓fullclaimed8/10

   Docs explicitly describe scanning a QR code shown by a service to add a new account, both generally (docs-1) and for specific migration flows (docs-6/41), which immediately generates TOTP codes in the app. This core flow is directly and simply documented as the primary onboarding method. Missing for 10: independent hands-on confirmation of the exact scan-to-code-generation moment and any UX friction reports.

   • [claimed-docs] “Scan the QR code shown by the service.”
   • [claimed-docs] “Enter the account name, issuer, and secret (setup key).”
   • [claimed-docs] “Tap the add button and scan the QR code shown by the service.”
   • [claimed-docs] “Open Ente Auth. Tap the add button and scan the QR code shown by the service.”

   proof ↗⚑ flag

Offline

1. power userCodes generate fully offline — no network, no vendor account required just to see my TOTP codes

   weight 2 · round to Ente Auth
   Bitwarden—none0/10

   Bitwarden's TOTP generation is tightly coupled to the vault: codes are stored and computed inside a Bitwarden vault item, which requires a Bitwarden account/vault (docs-1, docs-2) and typically syncs across the vendor's cloud infrastructure. No evidence describes a standalone, account-free offline TOTP mode; self-hosting (docs-10) still requires an account/server setup, not a vendor-free path. missing for 10: evidence of a no-account, no-vendor-server offline TOTP mode; confirmation that code generation works without ever creating/authenticating a Bitwarden account.

   • [claimed-docs] “it automatically produces the time-based one-time passwords (TOTPs), six-digit codes using SHA-1 that rotate every 30 seconds”
   • [claimed-docs] “Connect Authenticator with Password Manager to sync your verification codes. Once activated, the Bitwarden apps stay synchronized with any c…”
   • [claimed-docs] “This article will walk you through the procedure to install and deploy Bitwarden to your own Linux server.”

   proof ↗⚑ flag

   Ente Auth✓fullclaimed8/10

   Docs explicitly confirm offline mode with no account required, codes stored only on-device, and no network dependency for viewing codes. Missing for 10: independent hands-on verification (e.g. airplane-mode test) beyond vendor docs, and no detail on how backups/imports work fully offline without any cloud touchpoint.

   • [claimed-docs] “Ente Auth can be used without an account by choosing **Use without backups**. In offline mode, your codes are stored only on that device.”
   • [claimed-docs] “Use without an account”

   proof ↗⚑ flag

Organization

1. power userKeep dozens of tokens organized — search, folders or groups, and service icons — so the right code is always two taps away

   weight 2 · round to Ente Auth
   Bitwarden~partialclaimed4/10

   Docs confirm Bitwarden generates and syncs TOTP codes across devices and lets users import/export authenticator data (bitwarden-docs-1, bitwarden-docs-2, bitwarden-docs-3), which supports storing many tokens, but nothing in the evidence pack speaks to search, folders/groups, or service icons specifically for TOTP entries — organization is only implied through the general vault (login) item structure. missing for 10: explicit documentation of folder/collection organization for TOTP items, search functionality across TOTP entries, and service icon display for stored codes.

   • [claimed-docs] “it automatically produces the time-based one-time passwords (TOTPs), six-digit codes using SHA-1 that rotate every 30 seconds”
   • [claimed-docs] “Connect Authenticator with Password Manager to sync your verification codes. Once activated, the Bitwarden apps stay synchronized with any c…”
   • [claimed-docs] “Google Authenticator (QR code): Import from Google Authenticator using a QR code... LastPass (JSON): Import a LastPass Authenticator account…”

   proof ↗⚑ flag

   Ente Auth~partialclaimed6/10

   Ente Auth's marketing docs confirm search (deep-link search feature), service icons, and favoriting/organizing features ('Organize with ease', 'Favorite services to the top', 'Don't scroll'), directly supporting quick access to tokens. However, there is no concrete evidence of folder or group/category organization for large token sets — only vague 'organize with ease' copy and free-text notes (500-char annotations), not structured grouping. Missing for 10: explicit folder/category/tagging feature documentation, evidence of grouping many tokens, independent hands-on confirmation of organization UX at scale.

   • [claimed-docs] “Save time by viewing your next code”
   • [claimed-docs] “Easily identify your tokens by their icons”
   • [claimed-docs] “Organize with ease”
   • [claimed-docs] “Favorite services to the top”
   • [claimed-docs] “Don't scroll”
   • [claimed-docs] “Added support for search deep links via enteauth://search.”
   • [claimed-docs] “You can attach any text (upto a maximum of 500 characters), to provide more information about your accounts.”

   proof ↗⚑ flag

Variants

1. power userNon-standard tokens work too — Steam Guard, HOTP counters, custom periods and digit lengths

   weight 2 · round to Ente Auth
   Bitwarden—none0/10

   The evidence only describes Bitwarden's standard TOTP support (six-digit SHA-1 codes rotating every 30 seconds) with no mention of Steam Guard tokens, HOTP counters, or custom periods/digit lengths anywhere in the docs, community, or probe items.

   • [claimed-docs] “it automatically produces the time-based one-time passwords (TOTPs), six-digit codes using SHA-1 that rotate every 30 seconds”

   proof ↗⚑ flag

   Ente Auth~partialclaimed4/10

   Evidence confirms HOTP entries are supported (the changelog notes sharing is now limited to TOTP and hidden for HOTP entries), implying native HOTP counter support. However, there is no mention anywhere in the evidence pack of Steam Guard token support, or of custom period/digit-length configuration for TOTP entries. missing for 10: explicit Steam Guard support, custom period/digit-length configuration, and any hands-on confirmation beyond the changelog note.

   • [claimed-docs] “Sharing is now limited to TOTP codes; the share option is hidden for HOTP entries.”

   proof ↗⚑ flag