Why self-host with OpenVireo
The server can't read your passwords
Each database is one encrypted KeePass file. The server checks the file signature and nothing else: it never parses your entries. Your master password and keys never leave your devices.
Your files work without it
Every device keeps a full KDBX file that OpenVireo, KeePassXC or any other KeePass app can open. If you stop running the server, you still have your passwords in a standard format.
One binary, nothing else to install
Signed builds for Linux (x64 and arm64), macOS and Windows, or a Docker image. SQLite by default, Postgres and S3 when you want them. It runs happily on a Raspberry Pi or a small VPS.
Free and open source
The sync server is GPLv3 and free with no limits on users, devices or databases. Release binaries are notarized for macOS, signed for Windows and GPG-signed. See Verifying signatures.
Apps on every device you use
Desktop apps for Windows, macOS and Linux, an iPhone and iPad app with AutoFill, OpenVireo Web, browser extensions for Firefox, Chrome and Edge, and a CLI.
A hosted option when you want one
If you'd rather not run a server, the same apps sign in to a hosted OpenVireo account with sharing and organizations. You can switch either way.
How sync works
- A device downloads the server's copy of the database, still encrypted.
- It decrypts and merges that copy into its own database locally, the same way KeePass merges two files, and saves it.
- It uploads the merged file. If another device uploaded in the meantime, the server refuses the upload and the device merges again, so two devices can never overwrite each other.
- The server keeps previous versions and tells your other devices about the new one straight away.
The details, including the API, are in the sync server docs.
Set up a server
On Linux, download a release, add yourself and a first device, and start it:
v=VERSION a=x64 # the release without the v, e.g. 0.2.0; a: x64 or arm64
curl -fLO "https://github.com/OpenVireo/openvireo-sync-server/releases/download/v$v/openvireo-sync-server-$v-linux-$a.tar.gz"
tar -xzf "openvireo-sync-server-$v-linux-$a.tar.gz" && cd "openvireo-sync-server-$v"
./openvireo-sync-server users add alice laptop # prints the laptop's access token, once
./openvireo-sync-server # http://127.0.0.1:8787, data in ./dataThen in OpenVireo, open your database, go to Database › Database Settings › Remote Sync, choose OpenVireo Sync Server and enter the server URL, a database ID and the token. Add more devices with a pairing code; see Users and devices.
Installing and deploying covers macOS and Windows, Docker, systemd and HTTPS with Caddy or nginx.
What a self-hosted server doesn't do
- Sharing between people. Each user on your server has their own databases. Shared vaults and organizations need a hosted account.
- Android. There's no OpenVireo app for Android yet. KeePass apps on Android can still open your KDBX files.
- A self-hosted web app. OpenVireo Web is a hosted app. It can pair with your server, but you can't run it yourself.
- An audit. OpenVireo hasn't had a published third-party audit yet; one is planned.
Other self-hosted password managers
Vaultwarden is a lightweight, unofficial server for Bitwarden's apps, with sharing between users on your own server. OpenVireo vs Vaultwarden goes through the differences.
KeePassXC with Syncthing, Nextcloud or a shared folder copies one file between devices, but if two devices change it before it syncs you get a conflict copy to merge by hand. OpenVireo vs KeePassXC covers what OpenVireo adds on top of it.