Does Vaultwarden work with the official Bitwarden apps?
Yes. That is the whole point of the project: it implements the same protocol, and you use the Bitwarden browser extensions and mobile apps pointed at your own server.
Password manager
One-click Vaultwarden hosting on a French VPS
Vaultwarden is a Bitwarden-compatible server: your passwords stay with you and your whole team keeps using the official Bitwarden apps. Tick it when you order your VPS.
- Works with the official Bitwarden clients
- Organisations and collections with no per-seat subscription
- Automatic HTTPS, which those clients require
- Daily backups kept for 7 days
512 MB
of RAM required by the application
€0
per additional user
7 days
of backups retained
France
hosting and data
Your vault, on your server
Vaultwarden is a lightweight reimplementation of the Bitwarden server, written in Rust. It speaks the same protocol: you install the usual Bitwarden extensions and apps, point them at your server, and everything works as before — except the vault is yours.
The appeal is twofold. Sensitive data never leaves your infrastructure, and the features billed per user on hosted plans — organisations, shared collections, reports — are available without a per-seat subscription.
One thing to know before you start: Bitwarden clients refuse to connect to a server that is not on HTTPS. That is a classic stumbling block of a manual install, and precisely what one-click deployment settles from the outset.
Official Bitwarden clientsOrganisations and collectionsTwo-factor authenticationEnd-to-end encryptionWritten in Rust
From order to first vault
Three steps, no command line.
1
Order a VPS and tick Vaultwarden
A Debian or Ubuntu image and a size of at least 2 vCPU, 2 GB of RAM and 30 GB of disk is more than enough for this application.
2
The deployment runs itself
The application is installed and published on a valid HTTPS address, which is the condition for Bitwarden clients to agree to connect to it.
3
Create your account and invite your team
Attach your domain name from the console, create the first account, then set up your organisations and shared collections.
Manual install versus one click
What you would have done by hand on a bare server, and what is left for you here.
| By hand | One click | |
|---|---|---|
| Going live | SSH session, Docker to install and configure | One box ticked at order time |
| HTTPS | Mandatory for Bitwarden clients, and entirely on you | Issued and renewed automatically |
| Vault persistence | Volume to create and mount correctly | Provisioned with the application |
| Updates | Image to pull again and container to recreate | Flagged in the console, applied in one click |
| Backups | Script and remote storage to set up | Daily, 7-day retention, one-click restore |
What size of VPS for Vaultwarden
The application asks for 512 MB of RAM and stays frugal even with several dozen users. The platform minimum of 2 GB is comfortable.
| Use case | Configuration | What it covers |
|---|---|---|
| Family or personal use | 2 vCPU · 2 GB RAM · 30 GB NVMe | A handful of accounts, shared collections, light attachments. |
| Small team | 2 vCPU · 4 GB RAM · 60 GB NVMe | Ten to fifty users, several organisations, other applications alongside. |
| Company | 4 vCPU · 8 GB RAM · 120 GB NVMe | Heavy use, long history, sitting next to your other internal services. |
The vault is small but critical. Server size matters less than how regularly you back it up and whether you have tested a restore.
What we do, what you do
Worth stating plainly: we deliver and run the server, the application stays yours.
On us
The VPS, the network, DDoS protection, the hypervisor, and the deployment platform that installs the application, issues the certificate and triggers the backups.
On you
Vaultwarden itself: its accounts, its configuration, its updates, its data. Our support does not step into the application and provides neither maintenance nor monitoring for it.
Worth doing
Turn on two-factor authentication, export a copy of your vault off the server, and test a restore before you need one. Nobody can decrypt your vault for you, us included.
Frequently asked questions about hosting Vaultwarden
What people ask us most before getting started.
Is HTTPS really mandatory?
Yes. Bitwarden clients refuse to connect to a plain HTTP server. One-click deployment publishes the application over HTTPS from the start and renews the certificate automatically.
Can you read my passwords?
No. Encryption happens in the client before anything is sent, with a key derived from your master password. We run the server, not the contents of the vault — and nobody can recover it if you lose that master password.
Does the deployment cost anything on top of the VPS?
No. One Click Apps is included with every OnetSolutions VPS from 2 vCPU, 2 GB of RAM and 30 GB of disk, with no surcharge and no per-user subscription.
Do I keep SSH access to the server?
Yes. The VPS remains a full VPS with root access. One-click deployment saves you from needing SSH, it does not take it away.
Your vault live in minutes
Order a Debian or Ubuntu VPS, tick Vaultwarden, and point your Bitwarden clients at a server you own.