Password Management
Bitwarden
Rest of world Report an error0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Bitwarden Inc. · bitwarden.com
Report an error on this page Is this your product? →
Link to this page
Add ?theme=dark to the image address for dark backgrounds.
The badge shows the category and the month of the latest evaluation, and EU-Made where
that is the product’s provenance. It never shows a score.
Bitwarden at a glance
- Vendor
- Bitwarden Inc.
- Headquarters
- Not stated on the vendor’s pages as of 13 Oct 2026
- Data hosting
- Not stated on the vendor’s pages as of 13 Oct 2026
- Free plan
- Not stated on the vendor’s pages as of 13 Oct 2026
- Panel verdict
- The AI panel rates Bitwarden 3/5, the mean of 6 judges. Bitwarden is an open-source password manager; its strongest scores are identity integration at 7-8 and audit and policy at 7-8, its weakest pricing transparency at 1-2 and sovereignty at 3-4. how scores are made
- As of
- Vendor pages captured 1 Oct 2026 to 13 Oct 2026; evaluated by the panel 15 Oct 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Bitwarden is an open-source password manager; its strongest scores are identity integration at 7-8 and audit and policy at 7-8, its weakest pricing transparency at 1-2 and sovereignty at 3-4. Judges credited SSO over SAML 2.0 and OIDC, with the identity provider stated never to hold the decryption key and a customer-run key connector among three decryption paths, plus event logs of over 60 types, CSV and JSON export through a public API, six named SIEM integrations, indefinite retention behind a 367-day viewable window. On pricing, the captured pages show tier features but judges found no public price figures — no per-user cost, seat minimum, term or VAT treatment — so an annual invoice cannot be computed. Sovereignty scores rest on storage stated primarily in the EEA and the United States on Microsoft Azure, a Delaware incorporation recorded in the vendor's terms, and we found no public information on a subprocessor list with locations. Scores spread widest on security architecture, at 5-7, where open-source reviewability sits against no public information on a named independent audit or disclosed incident history. Self-hosting is the recurring mitigating factor.
Speaks for it
- SSO over SAML 2.0 and OIDC with SCIM and directory sync, three decryption paths including a customer-run key connector, and the stated position that the identity provider never holds the decryption key
- Event logs for Teams and Enterprise with over 60 event types, CSV and JSON export through a public API, and named integrations for Splunk, Microsoft Sentinel, Elastic, Panther, Rapid7 and Sumo Logic
- Self-hosting in standard and lite deployments for Windows, Linux, Docker and Kubernetes, with a Helm chart and compatibility with all clients
- Export covers encrypted JSON recommended as most complete, a ZIP with attachments, decryption local to the client, and transfer to other apps over the FIDO credential exchange protocol
- Account recovery on the Enterprise plan is documented down to its key model, with the old master password never visible to anyone and recovery actions logged
Held against it
- We found no public price figures on the captured pricing pages — no per-user cost, seat minimum, add-on price, self-hosted licence, minimum term or VAT treatment
- We found no public information on a named independent audit, certification or penetration test with its date and results, or on disclosed incident history
- We found no public information on a subprocessor list with locations or a data-processing agreement covering vault metadata and logs
- We found no public information on a status page with incident history, offline vault access during a vendor outage, or import from named competitors
- We found no public information on approval workflows for sensitive items, a waiting period for emergency access, or hiding a password while autofill remains allowed
Best for
- You need SSO over SAML 2.0 and OIDC with SCIM or directory sync and want to run your own key connector for decryption
- Your security operations team needs event logs piped into Splunk, Microsoft Sentinel, Elastic, Panther, Rapid7 or Sumo Logic
- You intend to self-host on Windows, Linux, Docker or Kubernetes and keep the vendor out of the data path
- You are replacing shared spreadsheets with organizations, collections and group-based permissions, with account recovery and enterprise policies on the Enterprise plan
Avoid if
- You must be able to compute an annual invoice from published per-user prices before committing
- You require storage confined to the EEA or a European contracting entity — the captured pages state storage primarily in the EEA and the United States on Microsoft Azure and record a Delaware incorporation
- You need event logs, account recovery or enterprise policies while staying on a plan other than Teams or Enterprise, where the captured help pages place them
The scores
| Criterion | Panel median |
|---|---|
| Encryption model & independent audits | 3 of 5 |
| Sharing, roles & recovery | 3.5 of 5 |
| SSO, directory sync & provisioning | 3.5 of 5 |
| Audit logs, policies & reporting | 4 of 5 |
| Hosting choice, offline access & export | 3.5 of 5 |
| European sovereignty | 2 of 5 |
| Pricing transparency | 1 of 5 |
Encryption model & independent audits
Show reasoningHide reasoning
How this is scored
What the vendor can prove about its security design: end-to-end encryption with named algorithms and key derivation, which fields are encrypted on the device and which are not, independent audits and penetration tests with published results, a bug bounty, and incident history disclosed.
0 — Security described in adjectives ("bank-grade", "military encryption") with no architecture, no audit and no statement of what the vendor can read.
3 — Encryption algorithms named and "zero knowledge" claimed, but no whitepaper, no statement of which fields stay unencrypted, and audits mentioned without dates, auditors or results.
5 — A published security whitepaper naming algorithms, key derivation and the client-side encryption model, a stated list of what is and is not encrypted (including URLs and metadata), and a named independent audit or certification (ISO 27001, SOC 2) with its date.
8 — Recurring independent penetration tests or code audits with reports or summaries published, a public bug bounty or vulnerability disclosure policy, past security incidents documented with their impact, and open-source clients or cryptography that can be reviewed.
10 — The design is verifiable end to end: full source or cryptographic design public, every field encrypted client-side including metadata, audits by named firms repeated yearly with full reports, a threat model that states what a compromise of the vendor's servers would expose, and incident post-mortems published.
The CISO
The security whitepaper names the cryptography — AES-CBC 256-bit with HMAC-SHA256, PBKDF2 at 600,000 iterations or Argon2id, RSA-OAEP for sharing — and the source is published for review with a HackerOne-backed disclosure program. What a board needs on the worst day is missing: we found no public information on independent audits by named firms with dates, on any disclosed incident history, or on which fields remain unencrypted. 5 6 13
The Identity Engineer
The security whitepaper names the actual design — AES-CBC 256-bit with HMAC-SHA256, PBKDF2 at 600,000 iterations or Argon2id, RSA-OAEP for sharing — and open-source code plus a HackerOne-backed vulnerability disclosure program let my team verify rather than trust. What holds it back for a two-thousand-seat estate is that we found no public information on an independent audit or certification with its date, published penetration-test results, disclosed incident history, or a stated list of which fields stay unencrypted. 5 6 13
The Compliance Auditor
The security whitepaper names the algorithms, key derivation and the client-side encryption model in more detail than I can usually extract for a file — AES-CBC 256-bit with HMAC-SHA256, PBKDF2 at 600,000 iterations with an Argon2id option, RSA-OAEP for sharing, server-side re-hashing of the master password and column-level encryption — and open-source code plus a HackerOne vulnerability disclosure program make the design reviewable. What I cannot file is a named independent audit, certification or penetration test with its date and results, and we found no public information on past security incidents or their impact. 5 6 13
The SME Owner
The security whitepaper names the algorithms, key derivation functions, iteration counts and the client-side encryption model, and the open-source code plus a HackerOne vulnerability disclosure program let outsiders check the claims. We found no public information on a named independent audit or certification with its date, published penetration-test reports, incident post-mortems, or a statement of which fields stay unencrypted. 5 6 13
The DevOps Engineer
The security white paper names the cipher, both key-derivation options with iteration counts and the RSA scheme behind sharing, the code is open for me to read rather than take on faith, and a HackerOne-run disclosure program plus scanning on every push round it out. We found no public information on a dated, named third-party audit, published penetration-test summaries, past incident disclosures, or a statement of which fields such as URLs and metadata remain unencrypted. 5 6 13
The Skeptic
The published security whitepaper names the design in full — AES-CBC 256-bit with HMAC-SHA256 integrity, PBKDF2 stretched to 600,000 iterations or Argon2id as an option, RSA-OAEP for sharing — and open-source clients plus a HackerOne-run disclosure program allow outside inspection. We found no public information on any independent audit or certification with a firm and date, any published penetration test, any statement of which fields remain unencrypted, or any disclosed incident history. An incident-response policy is not a disclosure, and a silent incident record is an answer in itself. 5 6 13
Sharing, roles & recovery
Show reasoningHide reasoning
How this is scored
How credentials are shared and governed across a company: shared vaults or collections, role-based permissions, view-only and time-limited access, admin account recovery, emergency access, and what happens to shared items when an employee leaves.
0 — Personal vaults only, or sharing by sending a password to another user with no permissions and no record.
3 — Shared folders with all-or-nothing access, no roles, and no stated process for recovering an account or reclaiming credentials from a departing employee.
5 — Shared vaults or collections with read, edit and manage permissions, groups and admin roles, an admin recovery mechanism documented with its key model, and offboarding that transfers a leaver's shared items.
8 — Granular permissions down to hiding the password while allowing autofill, time-limited and one-time sharing with external parties, emergency access with a waiting period, delegated administration per team or location, and approval workflows for sensitive items.
10 — Access is governed and provable: least-privilege defaults, recovery and emergency access designed so the vendor never holds a key and stated so, periodic access reviews supported in the product, and every grant, change and revocation attributable to a person.
The CISO
Sharing runs through organizations with collections, groups, roles and custom permissions, and Enterprise account recovery is documented down to its key model — the member's key wrapped with the organization's public key, the old master password never visible, and recovery events logged. Emergency access exists; we found no public information on hiding the password while allowing autofill, approval workflows, or a waiting period on emergency access. 6 7 8 7
The Identity Engineer
Collections with access settings, groups, and member plus custom roles give real governance, and admin account recovery is unusually well documented — the member key is wrapped with the organization's public key, the old master password is never visible to the resetting administrator, recovery events are logged, and the role hierarchy is spelled out. Emergency access and transfer of ownership to the organization cover the offboarding side. We found no public information on hiding a password while still permitting autofill, a waiting period on emergency access, approval workflows for sensitive items, or periodic access reviews. 6 7 8 7
The Compliance Auditor
Sharing runs through organizations with collections, groups, member roles and custom permissions, and the account recovery documentation is exactly what I ask for: the key model is stated (the member key encrypted with the organization public key), the old master password is never visible even to the resetting administrator, the role hierarchy is defined, and every recovery action is logged. We found no public information on hiding the password while allowing autofill, on a waiting period for emergency access, on approval workflows, or on an explicit offboarding transfer of a leaver's shared items beyond organization ownership. 6 7 8 13 7
The SME Owner
Organizations with collections, groups and member roles, sharing that transfers ownership of an item to the organization so credentials survive a leaver, and admin account recovery documented down to the organization-key model, role hierarchy and logging are exactly what I need to retire our spreadsheet. Account recovery sits on the Enterprise plan, and we found no public information on hiding a password while autofill still works, emergency-access waiting periods, or approval workflows for sensitive items. 6 7 8 7
The DevOps Engineer
Organizations, collections, groups and member roles give real permission structure, and admin recovery is documented down to the key model — the member's key wrapped with the organization's public key, with the old master password never visible to anyone including the executing admin. Shared items become organization-owned, so a leaver cannot walk off with them. We found no public information on hiding a password while still allowing autofill, waiting periods for emergency access, or approval workflows for sensitive items. 6 7 8 7
The Skeptic
Collections, projects, groups and per-collection permissions are documented, and account recovery states its key model plainly — the member's encryption key is wrapped with the organization's public key, the old master password is never visible to anyone, and enrollments, resets and withdrawals are all logged — an organization-held key rather than a vendor backdoor. We found no public information on a waiting period for emergency access, on one-time or time-limited external sharing, on hiding a password while autofill remains allowed, or on approval workflows. Solidly above the base, short of the governed-and-provable tier. 6 7 8 7
SSO, directory sync & provisioning
Show reasoningHide reasoning
How this is scored
How the vault fits into the company's identity stack: SSO with Entra ID, Okta or Google, and the key model behind an SSO unlock; SCIM or directory sync for joiners and leavers; MFA options including hardware keys; and passkey support for users and the vault itself.
0 — Each user creates an account by email; no SSO, no directory sync and no MFA beyond an app code.
3 — SSO available only to sign in to the admin console or on the top tier with no description of how the vault is then decrypted, and users provisioned by CSV invite.
5 — SSO with named identity providers (Entra ID, Okta, Google) documented with how the vault key is derived or released, SCIM or directory sync for provisioning and deprovisioning, and MFA including FIDO2 or hardware keys.
8 — SSO unlock designed so the vendor cannot derive the vault key and stated so, group sync driving vault permissions, automated suspension on deprovisioning, conditional access or device policies, and passkeys stored and used across platforms.
10 — Identity is integrated without trust shortcuts: the SSO key model published and independently reviewed, deprovisioning that revokes vault access and shared items immediately with a log entry, passwordless vault unlock with passkeys, and support for the customer's own key-management or trusted-device approval.
The CISO
SSO over SAML 2.0 and OIDC with just-in-time provisioning, SCIM or Directory Connector for directory sync, and three documented decryption paths — master password, trusted devices, and a self-hosted key connector — with the pages stating the identity provider never holds the decryption key. We found no public naming of specific identity providers such as Entra ID, Okta or Google, and no statement that deprovisioning revokes vault access immediately with a log entry. 6 9 10 13
The Identity Engineer
This is the criterion I live in, and the key model is genuinely documented: SSO over SAML 2.0 and OIDC with three decryption options — master password, device-stored keys on trusted devices, or a self-hosted Key Connector we would run ourselves — and the explicit statement that the identity provider never holds the decryption key; passkeys can live in the vault and, when PRF-capable, log in to and decrypt it. SCIM and the Directory Connector handle user and group provisioning. What I could not verify: we found no public information naming Entra ID, Okta or Google as documented providers, on FIDO2 hardware keys as a two-step method, on what happens to vault access the moment a directory account is disabled, or on conditional access and device policies. 6 9 10 13
The Compliance Auditor
SSO is documented across SAML 2.0 and OIDC with the decryption model spelled out — the identity provider never holds the vault decryption key — and three unlock paths are stated, including trusted devices and a self-hosted key connector, which amounts to the customer running its own key management. SCIM and the Directory Connector cover user and group provisioning, and passkey login can decrypt the vault on PRF-capable devices. We found no public information on automated suspension at deprovisioning or on independent review of the SSO key model. 6 9 10 13
The SME Owner
SSO over SAML 2.0 and OIDC with three spelled-out decryption paths — master password, trusted devices, or a self-hosted key connector — and the stated position that neither the vendor nor the identity provider holds the decryption key, plus SCIM or the Directory Connector and passkey unlock, make this credible. We found no public information naming specific identity providers like Entra ID, Okta or Google, on automatic suspension when someone is deprovisioned, or on independent review of the key model. 6 9 10 13
The DevOps Engineer
SSO over SAML 2.0 and OIDC keeps authentication decoupled from decryption — stated so that neither the identity provider nor Bitwarden can derive the vault key — and Key Connector lets me point decryption at my own self-hosted key server, which is the trust model I want. SCIM and the Directory Connector keep users and groups in sync, just-in-time provisioning is documented, and a PRF-capable passkey can unlock the vault without a master password. We found no public information naming specific identity-provider integrations, automated suspension on deprovisioning, or conditional-access and device policies. 6 9 10 13
The Skeptic
The SSO key model is spelled out: authentication is decoupled from decryption, the identity provider is stated never to hold the decryption key, and members unlock via master password, trusted devices or a self-hosted key connector — with the customer able to run their own key server. SCIM, a directory connector and just-in-time provisioning are documented, and a PRF-capable passkey can both log in and decrypt the vault. We found no public information on named identity providers, hardware-key two-step methods, automatic suspension on deprovisioning, or independent review of the key model, which stops this one step short of the top. 6 9 10 13
Audit logs, policies & reporting
Show reasoningHide reasoning
How this is scored
What an administrator and an auditor can see and enforce: event logs of access and changes, password health and breach reports, enforceable policies (master password, MFA, sharing, export), SIEM integration, and reports an ISO 27001 or NIS2 audit can use.
0 — No audit log and no admin policies; the administrator sees a user list.
3 — A basic activity list and a password-strength score, but no exportable log, no enforceable policies, and no record of who viewed or copied a shared credential.
5 — Event logs covering logins, item access, sharing and admin changes, exportable or available through an API, enforceable policies for master password and MFA, and password health and breach-monitoring reports.
8 — Native SIEM integration with named targets (Splunk, Microsoft Sentinel, Elastic or syslog), policies for sharing, export and browser-extension behaviour, log retention stated, and compliance reports aligned to ISO 27001, NIS2 or BSI IT-Grundschutz.
10 — Auditability is complete: every view, copy, autofill and permission change logged with user and device, logs tamper-evident and retained for a configurable period, alerting on anomalous access, and an auditor role that can read logs without access to secrets.
The CISO
Event logs cover over 60 event types for Teams and Enterprise, exportable as CSV or through the events API, retained indefinitely with a 367-day viewable window, and feed native SIEM integrations with Splunk, Microsoft Sentinel, Elastic, Panther, Rapid7 and Sumo Logic. Enterprise policies enforce master password requirements, two-step login, export removal and browser-extension behaviour, and health reports flag weak and reused passwords. We found no public information on tamper-evident logs, anomaly alerting, or compliance reports mapped to ISO 27001 or NIS2. 6 11 12 13
The Identity Engineer
Event logging is real auditability: over sixty event types, exportable as CSV or JSON through the public API, native integrations named for Splunk, Microsoft Sentinel, Elastic, Panther, Rapid7 and Sumo Logic, and retention stated as indefinite with a 367-day view window. Enterprise policies cover master password requirements, two-step login, export, Send, PIN unlock and browser autofill behaviour, and health reporting covers weak and reused passwords plus breach checks against known data breaches. We found no public information on compliance-report mapping for ISO 27001 or NIS2, tamper-evident logs, or alerting on anomalous access. 6 11 12 13
The Compliance Auditor
Event logs for Teams and Enterprise record more than sixty event types, export to CSV and JSON through the public API, and feed named SIEM targets including Splunk, Microsoft Sentinel and Elastic, with retention stated as indefinite and a 367-day viewable window; the enterprise policy catalogue enforces master password requirements, two-step login, export removal, Send management and browser autofill behaviour, plus password health and breach checks. For an ISO 27001 or NIS2 audit file I still miss reports aligned to those frameworks, and we found no public information confirming that individual item views and copies are logged with user and device. 6 11 12 13
The SME Owner
Event logs with over sixty event types, access through the web app and a public API, CSV or JSON export, stated indefinite retention, native integrations with six named SIEM platforms, weak- and reused-password reporting, and an enforceable policy set covering master passwords, two-step login, export and Send add up to a serious admin console. We found no public information on compliance reporting aligned to ISO 27001 or NIS2, or on log tamper-evidence. 6 11 12 13
The DevOps Engineer
Six named SIEM targets including Splunk, Sentinel and Elastic, a public API events endpoint with CSV and JSON export, stated indefinite retention behind a 367-day viewing window and sixty-plus event types — that feeds my pipeline directly. The policy set is deep: export removal, browser-extension autofill behaviour, session timeout, master-password requirements and account-recovery administration are all enforceable. We found no public information on compliance reporting aligned to ISO 27001, NIS2 or BSI IT-Grundschutz, tamper-evident logs, or alerting on anomalous access. 8 11 12 13
The Skeptic
Over sixty event types for Teams and Enterprise, exportable as CSV or through the public API, feeding six named SIEM platforms, with retention stated as indefinite and a 367-day viewable window — that is a real audit trail. The enforceable policy set is broad: master password requirements, required two-step login, export and PIN removal, autofill behaviour, session timeout. We found no public information on compliance reporting aligned to ISO 27001 or NIS2, on tamper-evident log storage, alerting on anomalous access, or an auditor role separated from access to secrets. 6 11 12 13
Hosting choice, offline access & export
Show reasoningHide reasoning
How this is scored
Where and how the vault runs and how the data leaves it: cloud region choice, a self-hosted or on-premises option, offline access during a vendor outage, client coverage across operating systems and browsers, and a complete, documented export and import path.
0 — Cloud only in an unstated region, no offline access, and no export or an export that drops attachments and shared items.
3 — Cloud with a region named, apps for common platforms, and an export in CSV only that leaves out attachments, folders, TOTP seeds or custom fields.
5 — An EU region or self-hosted option, offline read access on desktop and mobile, clients for Windows, macOS, Linux, iOS, Android and the major browsers, and an export that covers all item types including attachments.
8 — Both EU cloud and self-hosted or on-premises deployment documented, a status page with incident history, encrypted full-fidelity export and import from named competitors, and vault access continuing during an outage of the vendor's service.
10 — The customer can run and leave the vault on their own terms: self-hosting with documented high availability and backup, an open or documented export format that preserves structure, permissions and history, and a stated procedure for continued access if the vendor ends the service.
The CISO
Self-hosting is documented in standard and lite deployments for Windows, Linux, Docker and Kubernetes with a Helm chart, compatible with all clients, and export is genuinely complete — encrypted JSON recommended, a ZIP with attachments, password-protected files importable to any account, and FIDO credential exchange to other apps. We found no public information on a selectable EU cloud region, offline access during a vendor outage, a status page with incident history, or imports from named competitors. 1 3 13 14
The Identity Engineer
Self-hosting is documented deeply — standard and lite deployments across Windows, Linux, Docker and Kubernetes with a vendor Helm chart that fits an existing high-availability and recovery strategy, and every client stays compatible — and export covers encrypted JSON, a ZIP with attachments, local decryption before export, plus passkey portability via the FIDO credential exchange protocol. We found no public information on offline access during a vendor outage, a status page or incident history, a selectable EU cloud region for the hosted service, or import paths from named competitors. 3 13 14
The Compliance Auditor
Self-hosting is thoroughly documented — Docker, Kubernetes with a Helm chart, standard and lite deployments, compatible with all clients and fitting existing high-availability strategies — and the export path covers plaintext and encrypted JSON plus a ZIP with attachments, recommended encrypted, decrypted locally, with clear organization-level export roles. We found no public information on offline access during an outage, a status page with incident history, or import from named competitors. 1 13 14
The SME Owner
Self-hosting is documented in standard and lite deployments across Windows, Linux, Docker and Kubernetes with a Helm chart and compatibility with all clients, storage is stated for the EEA as well as the United States, and export covers encrypted JSON and attachments from every client. We found no public information on offline access during an outage, a status page with incident history, or import from named competitors. 1 3 13 14
The DevOps Engineer
Self-hosting is treated as a first-class deployment — standard and lite options across Windows, Linux, Docker and Kubernetes with a vendor Helm chart — and the self-hosted server speaks to every client including the CLI, which is my preferred topology. The export path is the most complete I have seen quoted: encrypted JSON recommended as most complete, a ZIP including attachments, organization export from web or CLI, decryption strictly local, and FIDO credential exchange to move passkeys out. We found no public information on documented high-availability and backup procedures for the self-hosted server, a status page with incident history, import from named competitors, or vault access continuing through a vendor outage. 1 6 13 14
The Skeptic
Cloud on Azure with storage stated for the EEA and the United States, plus self-hosting documented for Windows, Linux, Docker and Kubernetes with a Helm chart and both standard and lite deployments — the deployment story is genuinely two-track. Export is close to full fidelity: encrypted JSON, a ZIP including attachments, decrypted locally, portable to any Bitwarden account or to another app over the FIDO credential exchange protocol. We found no public information on offline read access during an outage, a status page with incident history, import from named competitors, or a stated procedure if the vendor ends the service. 3 6 13 14
European sovereignty
panel opinion
Show reasoningHide reasoning
How this is scored
Who the contracting entity and the parent company are, where vault data and metadata are hosted, and who the subprocessors are. Independently sourced by the sovereignty pipeline; end-to-end encryption narrows what a foreign authority could compel, but metadata, logs and the update channel for the client software remain in the vendor's hands, so the chain still counts.
0 — Non-EU vendor and contracting entity, hosting unstated, and subprocessors unnamed.
3 — An EU data region offered while the contracting entity and parent are non-EU without a stated safeguard, or the subprocessor list is absent.
5 — EU hosting as standard or selectable and an EU contracting entity, but the parent company or parts of the chain (support, analytics, email, client distribution) are non-EU.
8 — EU hosting on named infrastructure, EU contracting entity, subprocessor list published with locations, a DPA covering vault metadata and logs, and a self-hosted option that removes the vendor from the data path.
10 — Sovereign end to end and evidenced: European ownership, entity, hosting and every subprocessor, certifications published (ISO 27001, BSI C5 or equivalent), and source code or builds verifiable so the client update channel is not a blind trust in the vendor.
The CISO
The captured pages place data on Microsoft Azure across the European Economic Area and the United States, while a Delaware incorporation is recorded in the vendor's terms. Subprocessors are referenced generically and we found no published subprocessor list with locations, no data processing agreement for vault metadata and logs, and no European contracting entity; self-hosting exists but the rest of the chain sits with a US company on US-linked infrastructure. 3 4 6 13
The Identity Engineer
The contracting entity is a Delaware-incorporated US company, cloud data runs on Microsoft Azure with storage stated for the EEA and the United States, and we found no public information on a subprocessor list with locations. Self-hosting can take the vendor out of the data path entirely, but for the cloud estate the metadata, logs and the client update channel remain with a US vendor. 3 6 13
The Compliance Auditor
Data is processed in Microsoft Azure with storage described as primarily in the European Economic Area and the United States, and self-hosting can remove the vendor from the data path while open-source builds keep the client update channel reviewable. The contracting entity is not confirmed on the captured pages, ownership and the parent are unstated, and we found no public information on a published subprocessor list with locations or on certifications such as ISO 27001. 3 6 13
The SME Owner
Storage is stated for the EEA and the United States on Microsoft Azure, but the captured pages do not confirm the contracting entity's jurisdiction, and we found no public information on a subprocessor list, a data-processing agreement, or certifications. The documented self-hosted option that can take the vendor out of the data path is what lifts this above the bottom. 3 6 13
The DevOps Engineer
The contracting entity is a Delaware-incorporated company, all cloud data sits on Microsoft Azure stored across the EEA and the United States, and the privacy policy refers to subprocessors and vendors without naming them. The self-hosted deployment is the redeeming piece for me: on my own network the vendor leaves the data path, and the open source makes the client update channel inspectable. We found no public information on a published subprocessor list with locations or a DPA covering vault metadata and logs. 3 6 13
The Skeptic
The captured pages state that Bitwarden and its subprocessors store information primarily in the EEA and the United States on Microsoft Azure, while the vendor's own captured pages do not confirm the contracting entity's jurisdiction, ownership, or a subprocessor list with locations; the provenance line records a Delaware incorporation, putting the contracting chain outside the EU. We found no public information on a data-processing agreement covering vault metadata and logs. Open-source code and a self-hosting option that removes the vendor from the data path are the only sovereign pieces; the cloud chain is US-anchored and unverified. 3 6 13
Pricing transparency
Show reasoningHide reasoning
How this is scored
Whether a buyer can compute the real annual cost from public pages alone: price per user and tier, which features (SSO, SCIM, SIEM, self-hosting) sit in which tier, minimum seats, add-ons, and the minimum term.
0 — No public prices at all; every tier is a sales conversation.
3 — A starting price exists, but which business features (SSO, SCIM, audit logs) sit in which tier is unclear — the invoice is unknowable.
5 — Per-user tier prices public with the main features per tier, but at least one commonly needed piece (SSO, SIEM integration, self-hosting, minimum seats) is unpriced or "on request".
8 — Every tier priced publicly with its feature set and seat minimum, add-on prices listed, self-hosted licensing stated, minimum term and VAT treatment given.
10 — Complete price computability: annual invoice derivable for a given number of users, with every add-on, self-hosting licence, support level and renewal condition published.
The CISO
The business pricing page enumerates plan features — free sharing, Send, the MSP program — and a 14-day Enterprise trial is offered for SSO, but we found no public price per user, seat minimum, add-on price, minimum term or VAT treatment in the captures. The annual invoice cannot be computed from what is public. 2 9
The Identity Engineer
The captured pricing page describes tiers and features but contains no price figures, and we found no public information on per-user prices, seat minimums, add-ons or minimum terms. Which features sit where is partly visible from the help pages — account recovery and enterprise policies on Enterprise, event logs from Teams upward — but a buyer cannot compute an annual cost from what is published here. 2 9 11
The Compliance Auditor
The captured pricing pages describe features per plan — event logs on Teams and Enterprise, account recovery on Enterprise, a 14-day Enterprise trial, a free Families plan for Enterprise users — but we found no public pricing figures anywhere: no per-user price, seat minimum, add-on price, self-hosted licence, minimum term or VAT treatment. A buyer cannot begin to compute the annual invoice from what was captured. 2 6 8 9
The SME Owner
The captured pricing page describes tier features but no per-user price figure is given in the captured pages, so I cannot compute what forty people would cost, and the SSO trial and account recovery are tied to the Enterprise plan. We found no public information on seat minimums, add-on prices, minimum terms or VAT treatment. 1 2 9
The DevOps Engineer
The business pricing page lays out tier features, a free tier, a 14-day Enterprise trial and a free Families plan bundled with Enterprise, yet the captured pages give no price figures I could use. We found no public information on per-user prices, seat minimums, the self-hosted licence, minimum term or VAT treatment — the annual invoice is not computable from these pages. 1 2 9
The Skeptic
The captured pricing page lists features — unlimited devices, free sharing with another user, Send, an MSP program — and the help pages place business features in tiers (event logs on Teams and Enterprise, policies and account recovery on Enterprise), but we found no public price figures at all: no per-user cost, no seat minimum, no term, no VAT treatment. Without a single number, a buyer can derive no invoice from these pages; this sits below the level of a stated starting price. 2 6 8 11
European sovereignty — proven facts
0 of 4 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity | Not determined ⚠ unverified | — | uncited Report an error |
|---|---|---|---|
| Ownership | Not determined | — | uncited Report an error |
| Data residency | Not determined ⚠ unverified | — | uncited Report an error |
| Subprocessors | Not determined | — | uncited Report an error |
Questions about Bitwarden
Is Bitwarden European?
No. whats-best.ai classifies Bitwarden as Rest of world.
Where does Bitwarden store data?
Not stated on the vendor’s pages as of 13 Oct 2026.
Does Bitwarden have a free plan?
Not stated on the vendor’s pages as of 13 Oct 2026.
What are the best alternatives to Bitwarden?
As of 21 Oct 2026, the panel rates Password Depot (3.5/5), Keeper (3/5) and Passbolt (3/5) highest among the other 18 Password Management products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is Password Depot (EU-Made). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: Bitwarden alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 1 Oct 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Legal entity, Data residency. Not confirmed on the vendor’s own pages as captured.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
What we left out
A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.
- 20 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 5 data facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 2 legal facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 1 compliance fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 1 integrations fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 1 subprocessors fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 1 support fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 2 sovereignty dimensions could not be confirmed on the vendor’s own pages and are shown as unknown. Know more? Tell us
- 6 of the readings below were written against an earlier fact sheet — a fact has been corrected, added or pulled since. Until the panel next runs on this product you are reading the older judgement. Know more? Tell us
Sources (14)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage bitwarden.com Checked 13 Oct 2026 Details →
- 2 Pricing page bitwarden.com Checked 13 Oct 2026 Details →
- 3 Privacy policy bitwarden.com Checked 13 Oct 2026 Details →
- 4 Terms of service bitwarden.com Checked 13 Oct 2026 Details →
- 5 Encryption model & independent audits — found from sitemap bitwarden.com Checked 13 Oct 2026 Details →
- 6 Encryption model & independent audits — found from sitemap bitwarden.com Checked 13 Oct 2026 Details →
- 7 Sharing, roles & recovery — found from sitemap bitwarden.com Checked 13 Oct 2026 +1 earlier capture: 1 Oct 2026 Details →
- 8 Sharing, roles & recovery — found from sitemap bitwarden.com Checked 13 Oct 2026 Details →
- 9 SSO, directory sync & provisioning — found from sitemap bitwarden.com Checked 13 Oct 2026 Details →
- 10 SSO, directory sync & provisioning — found from sitemap bitwarden.com Checked 13 Oct 2026 Details →
- 11 Audit logs, policies & reporting — found from sitemap bitwarden.com Checked 13 Oct 2026 Details →
- 12 Audit logs, policies & reporting — found from sitemap bitwarden.com Checked 13 Oct 2026 Details →
- 13 Hosting choice, offline access & export — found from sitemap bitwarden.com Checked 13 Oct 2026 Details →
- 14 Hosting choice, offline access & export — found from sitemap bitwarden.com Checked 13 Oct 2026 Details →