Security
Self-host Bitwarden (self-hosted) on a VPS
The official self-hosted Bitwarden server.
Run the full Bitwarden server for teams and organisations, with the official clients and enterprise policies.
Why self-host Bitwarden (self-hosted)?
If you want official support, SSO and enterprise features in a self-hosted vault, the official server is the fuller option than Vaultwarden.
How to install Bitwarden (self-hosted)
- 1
Provision a VPS
Choose a plan with room for your data as well as the app.
- 2
Install the stack
Install Docker Compose (.NET, SQL Server/Postgres).
- 3
Deploy the application
Follow the project’s official install guide for your distribution.
- 4
Enable HTTPS
Serve it on your own domain behind a reverse proxy with a certificate.
- 5
Back it up
Schedule a database dump plus a copy of any uploaded files to an off-box location.
Practical tips
- Give Bitwarden (self-hosted) its own database user with rights only on its own schema.
- Reverse-proxy Bitwarden (self-hosted) and terminate TLS at the proxy so certificates are managed in one place.
- Take a VPS snapshot before major upgrades so you can roll back cleanly.
- Keep Bitwarden (self-hosted) patched — most self-hosting incidents are unpatched software.
Frequently asked questions
- How much RAM does Bitwarden (self-hosted) need?
- Plan on 4 GB for typical use; add headroom if you expect many concurrent users.
- What stack does Bitwarden (self-hosted) run on?
- Docker Compose (.NET, SQL Server/Postgres).
- Can I run other things on the same VPS?
- Yes — size the plan so Bitwarden (self-hosted) plus your other workloads fit in RAM with room to spare.
Looking for something else? Popular alternatives include Vaultwarden, Passbolt, KeePass + sync — browse all app guides.