How To Self-Host Bitwarden On Any Platform Using Docker

Self-host Vaultwarden — a lightweight, Bitwarden-compatible password manager — on Granite.so in about 7 minutes: Docker image → persistent volume → environment variables → custom domain. We use a fork of the official image that adds scheduled, age-encrypted backups to any S3-compatible storage (AWS S3, Cloudflare R2, MinIO), so your vault is never one disk failure away from gone. No terminal on the server, no Kubernetes YAML, no reverse proxy config. One resource, $5/month. 🔗 Links Granite (managed PaaS) → https://granite.so Image used in the video → https://github.com/mazanax/vaultwarden Pull it → ghcr.io/mazanax/vaultwarden Vaultwarden Repository → https://github.com/dani-garcia/vaultw... ⏱ Chapters 0:00 Intro 0:08 What is Vaultwarden (and why not Bitwarden Cloud) 0:24 The upstream image 0:33 The fork: encrypted S3 backups explained 1:20 Create the app on Granite from a Docker image 1:53 Resource settings: size, persistent volume, HTTP port 2:20 Environment variables: DOMAIN and SIGNUPS_ALLOWED 2:46 Review & first deployment 3:10 Overview, endpoints, logs, settings 3:41 Fixing the DOMAIN mistake (read the logs!) 4:13 Cancelling a stuck deployment 4:45 It's live — first login 5:28 Locking down registration 6:05 Upgrading: switching image tags 6:24 Custom domain via CNAME 6:44 Shell into the container 7:04 CPU / memory / disk insights 7:08 Enabling backups & wrap-up ⚙️ Environment variables used DOMAIN=https://your-host SIGNUPS_ALLOWED=true (set to false after creating your account) Backups switch on when these are set: BACKUP_AGE_KEY, BACKUP_S3_ENDPOINT, BACKUP_S3_BUCKET, BACKUP_S3_ACCESS_KEY_ID, BACKUP_S3_SECRET_ACCESS_KEY Full reference, cron schedule options and provider examples (AWS, MinIO, R2) are in the README. 🙋 Questions, or want a specific self-hosting guide next (Nextcloud? n8n? Uptime Kuma?) — tell me in the comments. #vaultwarden #selfhosting #docker #passwordmanager #bitwarden #devops #homelab