How "locked in" are we to upstream? #3518

Closed
opened 2026-04-06 04:57:05 +02:00 by MrUnknownDE · 0 comments
Owner

Originally created by @pdarcos on 3/5/2019

My question may seem silly but I don't find a clear answer anywhere.

The whole point of bitwarden_rs is to have our own self-hosted option that's not too heavy nor dependent on the official bitwarden.

I see lots of parts in the code that still reference bitwarden, which is fine until Kyle changes something upstream or blocks access to some api or service that bitwarden_rs is consuming from bitwarden.

So my question is how dependent are we to changes upstream? If bitwarden were to shutdown or otherwise block access how would we cope? Ideally we'd have everything on our backend and wouldn't be impacted if something happens to bitwarden, but I'm not sure we're there yet.

Can someone enlighten me on this question?

Thanks and keep up the awesome work

*Originally created by @pdarcos on 3/5/2019* My question may seem silly but I don't find a clear answer anywhere. The whole point of bitwarden_rs is to have our own self-hosted option that's not too heavy nor dependent on the official bitwarden. I see lots of parts in the code that still reference bitwarden, which is fine until Kyle changes something upstream or blocks access to some api or service that bitwarden_rs is consuming from bitwarden. So my question is how dependent are we to changes upstream? If bitwarden were to shutdown or otherwise block access how would we cope? Ideally we'd have everything on our backend and wouldn't be impacted if something happens to bitwarden, but I'm not sure we're there yet. Can someone enlighten me on this question? Thanks and keep up the awesome work
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github/vaultwarden#3518