Bitwarden official self-host
Official Bitwarden self-hosted server.
Category Password ManagersPlatforms Linux · Docker 26+Privileges Dedicated user + Docker accessChinese docs Official docs in EnglishStars ~750
One-click install command
curl -Lso bitwarden.sh "https://func.bitwarden.com/api/dl/?app=self-host&platform=linux" && chmod 700 bitwarden.shn./bitwarden.sh install
Notes
Prerequisites: a domain, ports 80/443, an install ID and key; official docs recommend a dedicated bitwarden user.
Agent Prompt
Copy the block below and hand it to an AI Agent — replace [bracketed] parts with your own values.
Deploy Bitwarden official self-host (Official Bitwarden self-hosted server) in my environment. Before starting: 1. Run read-only checks first: OS version, CPU architecture, available disk/RAM, port usage, Docker or sudo access — and report the findings. 2. Use the project source https://github.com/bitwarden/self-host as ground truth; verify the current stable version, prerequisites and compatibility. 3. Present an execution plan, the files/services/firewall rules to be changed, and a complete rollback plan; wait for my confirmation before executing. 4. Download remote scripts locally for review first; pin tag / image digest / commit; don't rely on latest or master. 5. Never put secrets (passwords, API keys, tokens, subscription URLs) in the prompt, shell history or logs — use 600-permission env files, Docker secrets or _FILE variables instead. Verified starting command (don't run blindly — download/expand and review first): curl -Lso bitwarden.sh "https://func.bitwarden.com/api/dl/?app=self-host&platform=linux" && chmod 700 bitwarden.shn./bitwarden.sh install Project-specific notes: - Prerequisites: a domain, ports 80/443, an install ID and key; official docs recommend a dedicated bitwarden user. - Permission requirement: Dedicated user + Docker access. Don't escalate privileges; don't run containers as root unnecessarily. After execution, verify and report back: - Installed version, service status and health check results; - Open ports, listen addresses, firewall changes; - Config files, data volumes, log and backup locations; - Access method (for sensitive credentials, only state where they're stored — never print them); - Restart policy, plus verified uninstall / rollback commands.