Bitwarden on-premise server replication

[cksapp (Kent)]

Hi @paslavskyit

I believe you are correct here that the migration process as detailed in the support articles is typically for moving from host to host, or cloud to host and visa versa.
Really meant more so as a one way move, and not a way to keep the two in “sync”.

@paslavskyit

I’ve tried Migration from host-to-host. That quite ok, but it’s more like moving from one to another, and I’m looking to have them both available in the same time being synchronized.

One thing you may try, as I know there is another post similar where this topic has come up previously. You may check there for some further ideas.
Essentially I believe this would call for a combination of the CLI and API calls with some custom scripts to keep the Organizational items, users & groups, and hopefully the license in sync between your self-hosted instance and Bitwarden’s cloud.

Self-hosted hot standby

Hi thankfully better offline management and access is in the pipeline and should hopefully come out of the works soon (my hope). In the meantime the Bitwarden API might be something too look into if you are familiar with and feel comfortable putting together something that could utilize the API. The Bitwarden CLI will also play into this and scripts can be set up to export organization items for backup, and I’m sure secondary scripts could be used for importing to an on-prem Org as a hotspare. …

Another related posting for the licensing,

Provide API endpoint for license settings modification

My company would like to be able to modify the license count via API, instead of the web interface. Currently there does not seem to be an endpoint for that. Would it be possible to create one? Background: When the license count is increased automatically, an invoice for each new user is created. This is a management overhead for our accounting team. Hence they have requested to increase/decrease the license count once a month so one big invoice is created. We would like to automate this proces…

---

I would also note this would only keep the Org items in sync. I believe your users would still need to set up an account on both instances (the invitation process could be automated with the directory connector), but would not sync their individual personal vault items.

Let me know how you make out,
This is something that has been on my radar to investigate as a fun project but isn’t something we are personally looking into for my company so I haven’t had the time to really give it a whirl.