Tool profilesBased on official documentation, not tested by us

Bitwarden: an open-source password manager your team can self-host, free and paid options

Bitwarden is an open-source password manager with a hosted service and a self-hostable server. Based on the official server README and Bitwarden's audit page, not tested by us: what it is, how it is licensed, what its audits say, its limits and what we could not confirm.

Type

Password manager (hosted service and self-hostable server)

License and cost

Server code under AGPL-3.0 and a separate Bitwarden License; we did not read the pricing, so we cannot say what is free

Reviewed

3 Nov 2026

Version

Not shown on the pages we read

Best for

Founders and small teams who share logins and keys over chat or notes today and want one managed, encrypted place for them.

Watch out for

Self-hosting makes you responsible for updates and backups. We did not read the pricing, so check which features are free.

← All tool profilesNo. 8 / 11

In one sentence

Bitwarden is a password managerPassword manager An app that creates, stores and fills in a different strong password for every account, so you only remember one. Tap again to open the glossary: a place to keep logins, keys and notes encrypted behind one master password, instead of in chat, notes or the repository. It is open source, and you can use Bitwarden's hosted service or run the server yourself.

Who it is for

Founders, indie makers and small teams who today share passwords and API keys in a chat or a shared note, and want a managed place for them. We read nothing on the features for teams, so we do not describe them.

What the documentation says

Everything below comes from the server's README and Bitwarden's own audit page, read on 2 November 2026.

  • What the server repository is: the backend for Bitwarden's apps, with the APIs, the database and other core infrastructure. It is written in C# on .NET, with the database code in T-SQL for SQL Server.
  • Licences: the repository lists AGPL-3.0, and also contains a separate Bitwarden License file and a licence FAQ. The README does not explain which licence covers which part of the code. Bitwarden's audit page says the source code is licensed under the GNU AGPL v3.0 or the Bitwarden License v1.0.
  • Self-hosting: Bitwarden can be deployed with Docker containers, with install scripts for PowerShell and Bash. The README lists two requirements, Docker and Docker Compose, and sends you to the help centre for the full guide.
  • Where the code lives: Bitwarden says its entire codebase is on GitHub.
  • Audits: Bitwarden says it runs annual third-party audits that include source-code assessments and penetration testingPenetration test (pentest) A permitted, planned attempt to break into your own systems, done by specialists, to find weaknesses before a real attacker does. Tap again to open the glossary. Its page lists them by year. For 2025 it names Cure53 (browser extension, core application, desktop app, web vault and Rust cryptography libraries), the Applied Cryptography Group at ETH Zurich (core cryptography), Unit 42 by Palo Alto Networks (mobile apps) and Fracture Labs (web app and network components). Earlier years name other firms, among them IOActive, Mandiant, and Insight Risk Consulting.
  • Certifications it claims: ISO 27001, SOC 2 Type 2 and SOC 3, GDPR and CCPA compliance, and HIPAA compliance with a yearly third-party audit. These are Bitwarden's own statements; the page gives no dates for the certifications.
  • Reporting a flaw: the README asks for sensitive reports by private email or through Bitwarden's HackerOne bug bounty, which its audit page describes as private.

The good

  • Open source, so anyone can read the code, and a version you can run yourself.
  • A long list of named third-party audits, published by Bitwarden itself.
  • A clear path to report a security flaw.
  • It replaces passwords in chat and notes with one managed, encrypted place.

The limits it admits

  • The README does not explain how the two licences divide the code, so check the licence FAQ before you rely on a feature.
  • The audit list and the certifications are Bitwarden's own claims. We did not read the audit reports themselves.
  • Self-hosting means you run the server: the README gives the install steps but no guidance on running it safely over time.

When not to use it

  • If nobody on your team will look after a self-hosted server. Then use the hosted service, or another tool.
  • If you think a password manager is a secretSecret (API key, token, password) Any piece of text that proves to a service that you are allowed in, such as an API key, a database password or an access token. Tap again to open the glossary store for your servers and pipelines. It is built for people's logins. For deploy keys, check what your hosting and pipeline tools offer. That is our advice, not Bitwarden's.
  • If you need an exact price before deciding: we did not read the pricing page.

What it costs you

We did not read the pricing, so we cannot say what is free and what is paid. The time cost is real in either case: moving every shared password into it, getting the team to use it, and protecting the master password, because losing it can lock you out. We did not read what Bitwarden offers for recovery, so check before you rely on it. If you self-host, add updates and backupsBackup A copy of your data kept apart from the original, so you can recover it if something is lost, broken or locked. Tap again to open the glossary of the server.

Typical setup mistakes

  • A weak or reused master password. It guards everything else.
  • Not turning on a second step for the account itself. A password manager without it has one weak point. Check what Bitwarden offers.
  • Self-hosting without a backup plan. If the server's data is lost, so are the passwords.
  • Leaving old shared passwords in chat after moving them. Delete the old copies and change what was exposed.
  • Putting everything in one shared vault with no thought to who needs what. Share only what each person needs. This is our advice.

How to check that it works

Official documentation and our approach, not something we ran: create a test account with a throwaway email, store a fake login, sign in on a second device and check that it appears. Never use a real password for the test.

Where to start

We did not test the tool, so we do not offer a tutorial. Follow Bitwarden's own help centre and the server README: httpsHTTPS The secure version of the web address protocol: it encrypts what travels between a visitor and your site and checks that the site is the real one. Tap again to open the glossary://github.com/bitwarden/server

What we could not confirm

We did not install or run Bitwarden. We read the server's README and the audit page, not the pricing, the apps' features, the audit reports, the licence FAQ or the self-hosting guide. We do not know which features are free, how recovery of a lost master password works, or how hard self-hosting is in practice. The certifications and audit claims come from Bitwarden's page and we did not check them with the auditors. We have not compared Bitwarden with other password managers.

Glossary: password manager, MFAMFA (multi-factor authentication) A second proof that it is really you, on top of your password, such as a code from an app or a security key. Tap again to open the glossary, secret. Runbook 04, account lockdown.

More free tools

Other profiles in this section.

Sources

Follow us

New profiles and security news: YouTube (@safet2ship) and Instagram (@safet2ship).

YouTube channel · Instagram

Get the free runbooks

One-page security checklists for founders who build with AI. You get a confirmation email first, then the runbooks.

Send me the runbooks