HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
bitwarden
server
C#2016–2026
bitwarden / server

server

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

62Distinct people
73Mentions
0Explicit recommenders
20.6KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

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

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 11:00:58 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year73 dated mentions

Observed mentions: 2016-10-10 18:44:00 UTC to 2026-05-19 01:57:27 UTC.

0510152016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments20162017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 9 mentions; 0 submissions, 9 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 7 mentions; 1 submissions, 6 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 8 mentions; 0 submissions, 8 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 12 mentions; 0 submissions, 12 comments20212022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 16 mentions; 0 submissions, 16 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 10 mentions; 0 submissions, 10 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 5 mentions; 2 submissions, 3 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC303
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC101
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC909
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC716
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC808
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC12012
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC16016
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC10010
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC523
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC101
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC101

What Hacker News says

3 sources
It's written against .NET Core which is cross-platform, however a handfull of the project's libraries haven't been ported to Core from the Full framework yet. See: https://github.com/bitwarden/core/issues/3 Additionally the DB Backend is MSSQL which "is" linux compatible (kind of), but if the author addresses this as well: https://github.com/bitwarden/core/issues/10 Then it should be runnable pretty easily on linux. So it isn't cross-platform yet but it seems that's part of the plan.
In Bitwarden – Free and Open Source Password Manager
While that is true (and I agree in principle), I'm actually fairly sure that a promise "the current license is GPLv3" is as legally binding as actually putting the license file in the repo -- since it's a statement by the copyright holder of the licensing. The wording wasn't "we might license it under X", or "I'm considering licensing it under X". The exact wording is: > I'll have a license added tonight at some point. It will be GNU GPLv3. Which to me reads as "I'll have a license [file] added tonight...". But meh, that's for courts to decide not random people on the internet cosplaying as lawyers. EDIT: This is all moot anyway because the author did end up using GPLv3[1]. [1]: https://github.com/bitwarden/core/blob/master/LICENSE.txt
In Bitwarden – Free and Open Source Password Manager
This is an ASP.NET Core application, however, it references the full .NET Framework currently (instead of .NET Core which is full cross platform). I am working to make it run on .NET Core but it requires some third party library dependencies to be addressed first. This is being tracked here https://github.com/bitwarden/core/issues/3 . I anticipate this to run on .NET Core in the near future and therefore be truly cross platform for Windows, Mac, and Linux.
In Bitwarden – Free and Open Source Password Manager

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.