Security
Self-host Bitwarden CLI (self-host) on a VPS
The official Bitwarden CLI against your own server.
Manage your vault, secrets and automation from the command line, pointed at your self-hosted server.
Why self-host Bitwarden CLI (self-host)?
Pairing the official CLI with a self-hosted server keeps secrets scriptable but still on your infrastructure.
How to install Bitwarden CLI (self-host)
- 1
Provision a VPS
Choose a plan with room for your data as well as the app.
- 2
Install the stack
Install Node.js CLI.
- 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 CLI (self-host) its own database user with rights only on its own schema.
- Reverse-proxy Bitwarden CLI (self-host) 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 CLI (self-host) patched — most self-hosting incidents are unpatched software.
Frequently asked questions
- How much RAM does Bitwarden CLI (self-host) need?
- Plan on 256 MB for typical use; add headroom if you expect many concurrent users.
- What stack does Bitwarden CLI (self-host) run on?
- Node.js CLI.
- Can I run other things on the same VPS?
- Yes — size the plan so Bitwarden CLI (self-host) plus your other workloads fit in RAM with room to spare.
Looking for something else? Popular alternatives include Vaultwarden, pass (unix), gopass — browse all app guides.