OSS Tanbou
View on GitHub

Bitwarden Server — The C#/.NET backend for vault APIs, identity, notifications, and enterprise integrations

OSS health 93
About these scores

Discovery score is an unbounded weighted, log-compressed index of stars, watchers, forks, and contributors. Growth momentum is its change over the observed period; OSS health is a 0–100 score from available repository recency, Community Health, and release data.

Stars
20,154
Primary language
C#
License
Not determined
Repository last updated
Sep 17, 2026

Overview

Bitwarden Server provides the APIs, database layer, identity, notifications, and other backend infrastructure used by Bitwarden clients. It is implemented in C#/.NET with ASP.NET Core and primarily uses T-SQL/SQL Server, with Docker-based self-hosting. The main server code is AGPL-3.0, while Commercial.Core and SSO integration include source-available Bitwarden-licensed code. The latest release checked on September 17, 2026 is v2026.9.0.

Features and best fit

Based on official documentation; not hands-on tested · Content checked:

Self-host the API, identity, event, and notification infrastructure behind Bitwarden clients

The server repository provides the backend for Bitwarden clients, including API, database, Identity, and notification services. Organization deployments can also include services such as Admin, SSO, and SCIM.

Sources: [2]

Operate the on-prem deployment through official scripts and Docker images

Linux and macOS use the official bitwarden.sh installer while Windows uses the PowerShell equivalent. Production images are split across API, Identity, Notifications, Events, Admin, SSO, SCIM, and related services.

Sources: [2]

For organizations keeping password data on infrastructure they control while using Bitwarden clients

It fits teams that want on-prem credential storage and organizational policy while continuing to use Bitwarden browser, mobile, desktop, and other clients.

Sources: [2]

Treat it as security-critical infrastructure and verify the AGPL versus source-available licensing boundary

The License FAQ states that the main server is AGPL-3.0, while Commercial.Core and SSO integration use the Bitwarden License and require a paid subscription for production use. Self-hosting a credential system also makes database, attachments, secrets, TLS, mail, backup/restore, and upgrade operations your responsibility.

Sources: [3][4]

Official sources

  1. [1]bitwarden/server — GitHub repository metadata(2026-09-17)
  2. [2]Bitwarden Server — README(2026-09-17)
  3. [3]Bitwarden — License Statement and FAQ(2026-09-17)
  4. [4]Bitwarden Server v2026.9.0 release(2026-09-17)
Supplemental curator note

This entry focuses on the backend repository rather than the client UX, especially self-host operations and the AGPL versus Bitwarden License boundary.

Try it in 3 steps

  1. 1

    Get the source

    git clone --depth 1 https://github.com/bitwarden/server.git
  2. 2

    Enter the repository

    cd server
  3. 3

    Check the official steps

    Continue with the commands in the README Installation, Quick Start, or Getting Started section.

    find . -maxdepth 1 -iname 'README*' -exec sed -n '1,220p' {} \; -quit
Check the official README

Growth

Growth trends · Last 30 days

20,154 Stars

Trend data is still being collected.

Development activity

Last 90 days · weekly

Commits (last 30 days)
97
Open PRs
192

Development activity is still being collected.

Built with

Categories and tags

Categories

Tags

GitHub data

GitHub dataView detailed GitHub data
View on GitHub

GitHub Topics

  • aspnetcore
  • aspnet
  • sql-server
  • api
  • sql
  • csharp
  • bitwarden
  • dotnet-core
  • dotnet
  • docker
  • signalr
Stars
20,154
Forks
1,772
Watchers
223
Open issues
36
Primary language
C#
License
Not determined
Repository last updated
Sep 17, 2026
Write a related article

Share a guide or use case for this OSS in Markdown. Articles are published after administrator approval.

Report incorrect information

Tell us if any listing information is incorrect or outdated.