Vaultwarden
Deploy Vaultwarden on Polyer to run a self-hosted, Bitwarden-compatible password manager server. This template runs one vaultwarden/server:latest service with SQLite, keeping vault data on a /data volume and DOMAIN set to the generated HTTPS domain. Review the open signups and admin token before storing passwords.
What you can use it for
- Store and share passwords for a household or small team with the Bitwarden apps and browser extensions.
- Sync a personal password vault across your devices through a server you operate.
What this template creates
vaultwarden/server:latestConfiguration to review
These inputs are exposed by the template. The deployment form identifies required values and validates them before creating services.
| Input | Environment key |
|---|---|
| Push service id | PUSH_SERVICE_ID |
| Push service key | PUSH_SERVICE_KEY |
How to deploy
- Select Configure deployment and sign in or create an account.
- Choose a new or existing project and select an available region.
- Review services, required inputs, storage and compatibility warnings. Submit the deployment only when the configuration is ready.
- Inspect deployment logs, complete the application's setup and test its endpoints before production use.
Operating this application
- Use only the generated HTTPS domain, which the web vault and Bitwarden clients need. This template lets anyone who reaches the page register, so set SIGNUPS_ALLOWED to false once your accounts exist.
- Keep the generated ADMIN_TOKEN private because it opens the admin page, and note that settings saved there are written to the data volume and take precedence over environment variables.
- Back up the whole data volume and test a restore before relying on it. The latest tag can move to a new release, so take a fresh backup before each update.
Hosting costs
CPU, memory, storage and network usage contribute to your bill. The selected region affects resource prices. A multi-service template incurs usage for each service; external APIs and software licenses are separate.
Review prices and estimate resource costsSource and validation
This deployment configuration comes from Coolify's Apache-2.0 licensed open template collection and is adapted through Polyer's compose importer.
Static compatibility analysis is not a live application verification. Test your chosen configuration and recovery workflow before using it for production.
Editorial content reviewed: 2026-10-10