Bitwarden
Password manager for businesses with shared vaults; self-hosting possible.
Building on it: what may you do?
Short answers based on the licence, for the version in the catalog.
- B1 Change the code for internal use in your company Yes, with conditions Yes, but if staff or others reach it over a network they must be able to get your modified source.
- B2 Build your own product or service on top and offer it to customers as SaaS Yes, with conditions Yes, but you must share your changes with the users (AGPL).
- B3 Make a closed-source derivative and sell or distribute it No No. The derivative must carry the same licence and the source must be offered.
- B4 Use the project's name and trademark No No, not without permission. The licence covers the code, not the name or logo.
Keep in mind
- Open core: parts of the project (often an ee/ or enterprise folder) are under a separate commercial licence and may not be changed or used freely.
- There is a licence note for this product (e.g. parts under another licence or version-specific terms): read it and check the licence of the exact version you use.
This is guidance, not legal advice. Check with a lawyer before deciding.
Verify with a lawyer. Not verified: check the following in the product's own documentation before deciding: clients-licence, licence-edition-boundary.
The licence in brief
GNU AGPL 3.0 (AGPL-3.0)
Network copyleft. Free to run. If you modify it and users reach it over a network, you must offer them your modified source.
The server is AGPL-3.0 except the bitwarden_license/ directory, which is under the Bitwarden License v1.0 (commercial, incl. enterprise features). The clients live in a separate repo with their own licence split.
This is guidance, not legal advice (inte juridisk rådgivning). Check with a lawyer before deciding.
Facts
- Licence
- AGPL-3.0
- Licence type
- Network copyleft (AGPL)
- Maturity
- Mature
- Open core
- Yes – some features need a paid edition
- GitHub stars
- 20.2k
- Latest activity
- Deployment
- Docker
- Login/SSO
- SSO in paid plans
- API
- Unknown
- Multi-tenant
- Organisations
- EU vendor
- Unknown
- Source code
- github.com/bitwarden/server
- Source
- GitHub API, fetched 2026-10-03
Licence analysis per use case
Sign in to see what the licence means for eight use cases – from internal self-hosting to offering the tool as a service.
Sign in