AI Governance & Security Vendor Wiki

7 min read

Bitwarden

Primary category: secrets-management.

One-liner — The open-source password manager that has become the default “good, cheap, and self-hostable” choice for teams. It also sells a real machine-secrets product, Bitwarden Secrets Manager, so a single vendor can cover both staff passwords and application/CI secrets.

What it does — Two products on one zero-knowledge, end-to-end-encrypted vault. Password Manager handles human credentials, passkeys and shared vaults through browser extensions, desktop and mobile apps. Secrets Manager handles machine credentials. Secrets live in projects. Machine accounts are non-human identities for applications, pipelines and AI agents, and each one holds a token scoped to specific secrets. Delivery is through a CLI (bws run injects secrets into a process), SDKs in nine languages, and integrations with GitHub Actions, GitLab CI/CD, Jenkins, a Kubernetes Operator and Ansible. The line-up also includes Passwordless.dev, a FIDO2/WebAuthn toolkit for adding passkeys to your own apps, and a free Authenticator app. Of the three password-manager write-ins in this survey (Bitwarden, LastPass, Dashlane), Bitwarden is the only one with a dedicated machine-secrets product.

Naming / provenance — Founded 2016 by Kyle Spearrin, who is now Founder & Chief Innovation Officer. Bitwarden, Inc. is the parent of the original entity, 8bit Solutions LLC. Its own about page now lists Michael Sullivan as CEO. Michael Crandell was CEO at the 2022 round, and this page has not verified when the change happened.

Ownership & viability — independent. The only disclosed outside capital is a $100M minority growth investment led by PSG, with existing investor Battery Ventures participating. It was announced September 2022, and two PSG partners joined the board. No valuation was disclosed and no later round was found. The company claims 80,000+ businesses and 15M+ users, which is vendor-reported. Viability looks sound. The acquisition-risk note: a minority-funded company four years past its last round is a plausible control-transaction candidate. Because the client code is open source and the full server stack can be self-hosted, customers would keep an exit path if an owner changed direction. That is a stronger continuity position than any closed-source competitor offers.

Positioning & differentiators —

  • Open source and fully self-hostable. Clients and server are public, and the whole stack can run on your own infrastructure. Neither 1password nor keeper offers that. For a firm that does not want a third party holding its credential vault at all, Bitwarden is the most credible commercial option. The alternative is running hashicorp-vault, but Vault covers only machine secrets.
  • Price. Published, low per-seat pricing. Secrets Manager Enterprise lists at $12/user/month, and a free tier allows 2 users. That is cheaper than doppler or infisical for small teams that already pay for Bitwarden seats.
  • Human and machine secrets from one vendor, like 1password and keeper. Secrets Manager is simpler than hashicorp-vault: it stores and injects static secrets and has no dynamic, short-lived credential engine. It is closer in shape to doppler or infisical than to Vault.
  • Early agent-credential work. A local-first MCP server shipped in July 2025. An “Agent Access SDK” for just-in-time, human-approved credential release to AI agents followed in October 2025, but Bitwarden itself calls the SDK alpha and not for production data.

Who should choose them / anti-fit — Fits a small-to-mid manager that wants one credential vendor for staff passwords and developer secrets at low cost. It fits even better when the firm wants to self-host its vault for control or data-residency reasons. Anti-fit:

Known weaknesses / gotchas —

  • April 2026 supply-chain incident. For about 90 minutes on 2026-04-22, @bitwarden/cli version 2026.4.0 on npm carried credential-stealing malware. It took npm and GitHub tokens, SSH keys and AWS/Azure/GCP credentials from developer machines and CI runners that installed it. Bitwarden says the vault was never at risk and only the npm channel was affected. Public accounts disagree on the root cause: Bitwarden tied it to the wider Checkmarx campaign, while JFrog and Socket pointed to a compromised GitHub Action. For a hedge fund this matters because the CLI is exactly what gets installed in CI pipelines. Pin versions and verify CLI provenance, and check whether any pipeline pulled that release.
  • Self-hosting moves the security burden to you. Patching, backups and availability of a self-hosted vault become your team’s job.
  • Secrets Manager is less mature than the password manager and than dedicated secrets tools. It stores static secrets, with no secret generation or rotation engine verified here.

Deployment & data handling — Cloud SaaS, with vault data stored in Microsoft Azure in a US or EU region, or fully self-hosted. Self-hosting Secrets Manager requires the Enterprise plan. The vault is end-to-end encrypted: in the cloud, Bitwarden holds ciphertext but not the keys. data_leaves_tenancy: partial because the encrypted vault leaves your tenancy in the cloud model but not when self-hosted. Which metadata (item names, URLs, access logs) is visible to Bitwarden in the cloud model is unverified. Bitwarden says the MCP server runs locally on the user’s machine and recommends a local, self-hosted LLM when using it. That advice matters: piping vault contents to a hosted model defeats the zero-knowledge design.

Integrations & partnerships — SSO (SAML/OIDC), SCIM and Directory Connector on Enterprise; event logs exportable to CSV or SIEM; CI/CD (GitHub Actions, GitLab, Jenkins), Kubernetes Operator, Ansible. MCP: a Bitwarden-published MCP server (mcp_support: server), extended in October 2025 to enterprise administration tasks.

Compliance & FS traction — Bitwarden’s compliance page lists SOC 2 Type II, SOC 3 (public), ISO 27001, HIPAA (annual third-party audit), GDPR, CCPA and the EU-US Data Privacy Framework. It also lists annual third-party source-code audits and penetration tests, plus a HackerOne bug bounty. No FedRAMP (the page says Bitwarden is “pursuing” it). Five survey respondents (Oct 2026) report it in production, the joint-highest write-in count in this category alongside LastPass. No named financial-services customers were confirmed.

Commercial — Per-seat with published prices. Secrets Manager: Free (2 users, 3 projects, 3 machine accounts), Teams $6/user/month (20 machine accounts), Enterprise $12/user/month (50 machine accounts, SSO/SCIM, self-hosting). Extra machine accounts are $1 each, all billed annually in USD as of 2026-10-23. Password Manager business tiers are priced separately and were not re-verified here.

Open questions

  • When Michael Sullivan became CEO, and Michael Crandell’s current role.
  • Whether SOC 2 / ISO 27001 scope covers Secrets Manager and the cloud service only, or anything relevant to self-hosted deployments.
  • What metadata is visible to Bitwarden in the cloud model.
  • A published root-cause post-mortem for the April 2026 npm incident, and what CI/CD hardening followed.
  • Whether Secrets Manager has gained secret rotation or dynamic-credential features.
  • Status of the Agent Access SDK beyond alpha.
  • Named FS customers; FedRAMP progress.

Sources

History

  • [2026-10-23] Page created via wiki-create and researched the same day. Added because 5 respondents to the Oct 2026 CTO survey wrote it in under Secrets Manager, all 5 in production.

Graph View

Backlinks