Bitwarden Secure Sync

Bitwarden Secure Sync is a local backup tool for Bitwarden users that periodically exports their vault to a local file using the Bitwarden CLI.

  • Backup
  • Security
  • Tools & Utilities
Bitwarden Secure Sync is a local backup tool for Bitwarden users that periodically exports their vault to a local file using the Bitwarden CLI.

Platform availability

Available on 1 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

50/100 Fair

Maintained
59last commit 168 days ago
Popular
2722 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
502 GB minimum RAM
Security check
75no serious findings

Availability: platform listings confirmed today, links checked 38 days ago

GitHub stars
22
Open issues
3
Last commit
2026-06-06
Latest release
1.0.6
License
GPL-3.0
Activity
stale

Checked 10 days ago - source: GitHub (AronMarinelli/bitwarden-secure-sync)

Resources & Compatibility

Minimum requirements: 2 GB RAM. ARM (e.g. Raspberry Pi) is not supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Set your Bitwarden token first Before starting the MCP server, set BW_SESSION (a saved token the server uses to sign in to Bitwarden) to your Bitwarden token. Without it, the server cannot access your vault, so requests and tools will fail. source
  • Use Node.js 22 or newer Install Node.js 22 or newer before setup, because Node.js is the program that runs the server and older versions can cause it to fail to start or misbehave. source
  • Docker Bind both /app/config and /app/data volumes so configuration and export files persist. source

Fetched 38 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Which folders must I bind when running the Docker image?

Bind both the /app/config and /app/data directories to host paths for the container to function properly. On first run the app creates appsettings.json in /app/config.

Should I run the container as root?

The app defaults to running as root, so the docs recommend setting the PUID and PGID environment variables for better security. You can pass them with the Docker run command along with the config and data volumes.

Which Bitwarden credentials do I put in the config?

Use the API ClientId and ClientSecret from the security keys area of your Bitwarden account settings. The config also needs the server URL and your vault password.

Where are exported vault files stored and how long are they kept?

Exports go to the data directory, which can be set with DataDirectory in appsettings.json. FileRetention controls how many days export files are kept, with the example using 7 days.

Can I run this without Docker?

Yes, you can clone the repository and build the .NET console app yourself. You need an appsettings.json file in the working directory or in a config subdirectory.

Answers sourced from github.com

Community

Collected 53 days ago - public community threads