server

bitwarden/server

Bitwarden infrastructure/backend (API, database, Docker, etc).

Ship status

Still shipping

Pushed in the last 30 days.

Last push
Oct 11, 2026
today
Ship score
95/100
How it is calculated →
Stars, last 7 weeks
Stars, weekly: 20,219 → 20,242 (Sep 29 – Oct 6, 2026)
History starts 2026-09-29, the first weekly sample after this repo joined the directory.

Shipping: pushed in the last 30 days · slowed: quiet for 31–120 days · silent: no push in over 120 days.

Repo facts

What GitHub reports.

Stars
20.3K
Forks
1.8K
Open issues
266
Watchers
223
Primary language
C#
License
Other
Created
Nov 23, 2015
Owner
bitwarden · Organization

Open issues are the issues and pull requests GitHub reports as open; watchers are the accounts subscribed to the repository. License unknown — GitHub’s own license field, not legal advice. 12 startups in the directory ship primarily in C#.

Topics

#api#aspnet#aspnetcore#bitwarden#csharp#docker#dotnet#dotnet-core#signalr#sql#sql-server

How it got here

What the classifier decided, and when.

Classified as an open-source startup by Jev, TypeSafe’s classifier, on Sep 22, 2026 — os_startup 98%, self-hostable 85%, hosted offering 92%. The classifier reads only the repository’s name, description and homepage; it can be wrong, and a probability under 0.5 puts a listing in the review queue rather than out of the directory.

Joined the directory 2026-09-22, added by hand. Answered by jev-1.13.0. How the classification works →

Embed your status

Put this badge on your README.

OSSEAN ship status: shipping — last push 2026-10-11This is the badge for bitwarden/server, as served from the URL below.
[![OSSEAN: shipping](https://ossean.com/badge/bitwarden/server.svg)](https://ossean.com/bitwarden/server)

Updates daily, from the last push GitHub saw.

Honest caveat: GitHub proxies README images through Camo and rewrites the anchor with rel=“nofollow”, so a README embed sends you referral traffic and brand, not link equity. The link is dofollow wherever you control the markup — your docs, your landing page, your blog. The snippet uses your frozen OSSEAN slug, so it survives a repo rename.