Four dollars per user per month. That is what Bitwarden’s Teams plan costs on annual billing, with Enterprise at six. Those two numbers are the most concrete things I can tell you about Bitwarden right now, which is awkward, because the thing people are actually arguing about is its dual license model — and the sources circulating on that topic contain almost nothing.
I went looking. There is a Hacker News thread titled “Bitwarden Dual License Model” that, in the version I can see, consists mostly of YC application boilerplate and navigation links. No definitive detail on what the model is, what changed, or when. So rather than guess at license terms and hand you a confident-sounding fabrication, let me do the more useful thing: explain why this question matters for anyone picking a password manager for a team, and what I can verify.
What dual licensing actually means for you
A dual license model means the same codebase ships under two different sets of terms. Typically one is an open source license for the community, and one is a commercial license for paying customers or for specific components. Companies do this for reasonable business reasons — it funds development while keeping the code auditable.
The practical consequences land in three places:
- Self-hosting rights. Can you run it on your own hardware, and under which terms? For teams with compliance requirements, this is the whole ballgame.
- Which features live on which side. Enterprise features behind a commercial license are standard practice, but the dividing line determines whether the open source build is genuinely usable or just a demo.
- Fork viability. Dual licensing is often where community forks get complicated. If you care about having an exit path, the license text is the exit path.
None of those answers are in the material I have. If someone tells you with certainty what Bitwarden’s license split means for your deployment, ask them to show you the license file.
What I can verify
Here is the part that holds up. Bitwarden is the open source option in the password manager comparison set. Its codebase is publicly auditable. It offers a genuinely unlimited free tier — unlimited passwords, unlimited devices, one user. That last detail is the one most people get wrong when they recommend it; the free tier is generous but single-seat.
Paid pricing sits at $4 per user per month for Teams and $6 for Enterprise on annual billing. Against competitors in the same comparison, that is the low end.
The release cadence is fast. Version 2026.9.0 shipped on September 17, 2026, and the September release notes list work including SDK pin unlock support, a data layer for Identity Autofill, and user notification plumbing. In August 2026, Bitwarden added direct import from Keeper Password Manager — items move from Keeper into the Bitwarden vault without requiring an export file first. That is a small feature with an outsized effect on migration friction, which is usually the single biggest reason teams stay on a password manager they dislike.
One date worth putting on your calendar if you run Bitwarden Business with SSO: Bitwarden is dropping support for RSAES-PKCS1 v1.5, an outdated and insecure SSO encryption scheme. Automated reminder emails start October 13. Deprecating weak crypto is the right call, but it is the kind of change that quietly breaks a login flow for someone on a Monday morning.
My read as a reviewer
The license conversation and the product conversation are getting tangled, and I think readers deserve to see them separated.
On the product side, the signals are good. Frequent releases, active work on autofill and unlock mechanics, import paths from competing tools, and deprecation of weak authentication schemes all describe a tool being maintained seriously rather than coasting. Low pricing with an auditable codebase remains a strong combination.
On the license side, I have nothing solid, and I would rather say so than pad this piece with speculation dressed as reporting. Licensing shifts at open source companies have a pattern — community concern spikes, details get misquoted, and the actual terms turn out narrower or broader than the first round of commentary suggested. We are in the first-round-commentary stage.
So my advice is boring and useful. If you are evaluating Bitwarden this week, evaluate it on price, audit access, release velocity, and migration support, because those are measurable today. If licensing terms are load-bearing for your decision — self-hosting, forking, redistribution — go read the repository’s license files directly and check them against your own requirements. Do not outsource that to a blog post, including this one.
When real detail on the dual license model surfaces, I will cover it. Until then, the $4 and $6 figures are the facts, and the rest is still an open question.
🕒 Published: