Bitwarden on your own Vaultwarden, reachable only through Tailscale

My take: My Bitwarden runs on Vaultwarden, reachable only through Tailscale. Really handy, and fairly secure.
- Where
- Your own server, on your tailnet
Vaultwarden is a server you host yourself, and the official Bitwarden apps accept it as if it were Bitwarden's own cloud. My rule on top of it: the server answers on my tailnet (the private network Tailscale builds between your devices) and nowhere else. No port open on the Internet, and the apps on your phone and your computer work as usual, as long as Tailscale is connected.
What you need
- A machine that stays on and runs Docker: at home (a NAS, a mini PC) or rented from a host.
- Tailscale on that machine and on every device that opens the vault. Its Personal plan is free for up to six users, for non-commercial use (pricing, November 16, 2026).
- The official Bitwarden apps, free to download, on your phone and your computer, browser included.
The budget: no software to pay for. Vaultwarden is free and open source; what you pay for is the machine and its electricity.
Vaultwarden in brief
Vaultwarden is an unofficial server compatible with the Bitwarden apps, written in Rust and published under AGPL-3.0: vault, Send, attachments, organizations, two-step login and emergency access. It is not affiliated with Bitwarden, Inc., so problems go to Vaultwarden, never to Bitwarden's support. It had 70,800 stars on GitHub on November 16, 2026, and version 1.37.5 came out on November 1, 2026. Germany's federal cybersecurity office, the BSI, analyzed its version 1.30.3, as its audits page lists.
The steps
1. Start Vaultwarden on the machine only
A compose.yaml, adapted from the project's README:
services:
vaultwarden:
image: vaultwarden/server:latest
container_name: vaultwarden
restart: unless-stopped
environment:
DOMAIN: "https://server.your-tailnet.ts.net"
SIGNUPS_ALLOWED: "true"
volumes:
- ./vw-data/:/data/
ports:
- 127.0.0.1:8000:80
The 127.0.0.1 matters: the port listens on the machine itself, not even on your home network. DOMAIN takes the HTTPS address the server will have on your tailnet, which step 2 gives you.
2. Give it an HTTPS address on the tailnet
The web vault only works over HTTPS, because browsers expose the cryptography it needs in secure contexts only, the README explains. Tailscale gets you a real certificate for your machine's name under ts.net: in the admin console, on the DNS page, turn on MagicDNS, then "Enable HTTPS" under HTTPS Certificates (Tailscale's docs). Machine names end up in a public log of certificates (Certificate Transparency): give yours a neutral one. Then, on the server:
tailscale serve --bg 8000
tailscale serve relays your tailnet's HTTPS requests to the local port, with a certificate it provisions itself, and --bg keeps it running in the background, after a reboot too (docs). Do not confuse it with tailscale funnel, which publishes a service on the Internet.
3. Create your account, then close signups
From a device on your tailnet, open the address, create your account with a long master password, then set SIGNUPS_ALLOWED: "false" and recreate the container (docker compose up -d). By default, anyone who reaches the server can register, says the wiki: here, anyone you have let into your tailnet.
4. Lock the admin page, or leave it off
The /admin page manages users and settings. Without an ADMIN_TOKEN, it stays off. If you want it, do not store the token in clear text: generate an Argon2 hash with docker exec -it vaultwarden /vaultwarden hash and use that as ADMIN_TOKEN (wiki).
5. Point the apps at your server
On the login screen of each Bitwarden app, pick "Self-hosted" under "Logging in on" ("Accessing" in the desktop app), then type your server's https:// address (Bitwarden's help). Tailscale must be connected on that device.
6. Back up every day
Everything lives in the vw-data folder. The SQLite database holds almost all of it: docker exec vaultwarden /vaultwarden backup writes a dated copy of it next to the original, while the server runs (built in since version 1.32.1). Keep the attachments folder too, and ideally config.json and the rsa_key files. Run it every day, send a copy to another machine, encrypted, and test a restore from time to time, as the backup guide recommends.
Day to day
With Tailscale on, the apps sync as with any Bitwarden server. Without it, an unlocked Bitwarden app keeps working offline in read-only mode, including when it cannot reach a self-hosted server, Bitwarden says: you read your passwords, and you save new ones once you are back on the tailnet. That is the price of the rule, and for me it is a fair one: the setup is really handy, and fairly secure.
The mistakes to avoid
- Exposing it to the Internet: a port forward on your router, a public reverse proxy, or
tailscale funnelinstead ofserve. The point is that no scanner ever sees your vault; I never open a port for that reason. - No backup, or a backup on the same disk. Vaultwarden says plainly that it cannot be held liable for lost data, and its wiki advises against counting on VM or filesystem snapshots as your backup.
- Pasting the Argon2 hash into
compose.yamlas is. Docker Compose reads every$as a variable: double each one ($$), or put the token in a.envfile, as the wiki shows.
Drafted with Claude, Anthropic's AI, from my take. Reviewed and owned by me.