Vaultwarden Docker Hosting: Deploy & Host Vaultwarden in One Click
Updated November 3, 2026 · 6 min read
Vaultwarden Docker hosting on xCloud lets you deploy the open-source Bitwarden-compatible password manager from the xCloud app-create flow: Sites → New Site → NGINX server → One Click Apps → Vaultwarden → Demo Site or Go Live → Next. You do not need to write a custom docker-compose.yml for this xCloud flow; xCloud creates the app as a Docker site. xCloud sets up the server and SSL. You can turn on server security updates on the Security Update page. You run backups with Backup Now or turn on Automatic Backup, and you choose when to update Vaultwarden.
For server sizes and prices, see the Vaultwarden hosting page.

Vaultwarden Docker hosting one-click app selected in the xCloud One Click Apps catalog
Table of contents
- Why use xCloud for Vaultwarden hosting?
- Requirements
- One-click deployment steps
- Post-deployment setup
- Close sign-ups
- Store the Admin Token
- Add SMTP
- Run a backup
- Vaultwarden updates
- xCloud vs Railway vs Coolify
- Troubleshooting
Why use xCloud for Vaultwarden hosting?
Vaultwarden stores sensitive password data, so the deployment needs more than a quick container start. The running site also needs HTTPS, persistent storage, backups, SMTP for invites, password hints and email login codes, and a safe update path. xCloud keeps the deployment simple, and you manage your domain, SSL and logs from one dashboard.
| Need | How xCloud handles it |
|---|---|
| Fast app start | Choose Vaultwarden in One Click Apps and create the site from the dashboard. |
| Server choice | Use a server you already have, or buy a Cloud VPS from xCloud, on NGINX. |
| No custom Compose authoring | xCloud writes the Docker setup for you, so you do everything from the New Site screen. |
| Safe production URL | Use Demo Site for testing or Go Live for a real domain with HTTPS. |
| Ongoing operations | Manage your domain, SSL, logs and credentials from the site dashboard. You run backups and choose when to update Vaultwarden. |
Vaultwarden hosting requirements
| Requirement | Recommendation | Why it matters |
|---|---|---|
| Server stack | NGINX | xCloud installs Docker on the NGINX server automatically; OpenLiteSpeed servers cannot run Docker. Vaultwarden is deployed as a Docker-based app in this xCloud flow. |
| Storage | Persistent disk with backups | Vault data, attachments, and generated app files must survive restarts and updates. |
| Domain and SSL | Use Go Live for production | Bitwarden-compatible clients and browser extensions should connect over HTTPS. |
| Email/SMTP | Configure for production teams | Invites, password hints and email login codes depend on working email. |
| Registration policy | Disable open registration unless intentional | Private vaults should not allow public account creation. |
| Admin Token | Created for you. Store it securely | The admin interface can control sensitive Vaultwarden settings. |
Vaultwarden template components
xCloud sets up Vaultwarden as a Docker site for you. These parts affect how you back up, restore and secure your vault.
| Component | Purpose | Operational note |
|---|---|---|
| Vaultwarden application container | Runs the vault you and the Bitwarden apps connect to. | Check the site dashboard after updates and confirm client sync works. |
| Persistent application data | Stores vault records, attachments, and generated files. | Include this storage in backups before inviting users. |
| NGINX routing | Routes the Demo Site or custom domain to the app. | Use Go Live for a stable production password vault URL. |
| SSL certificate | Secures browser and client traffic. | Do not store real vault data until HTTPS is active. |
| SMTP settings | Sends invites, password hints and email login codes. | Verify SMTP before onboarding a team. |
Deploy Vaultwarden in one click on xCloud
1. Open New Site
In xCloud, go to Sites and click New Site. Select the NGINX server that should host Vaultwarden.
Expected result: xCloud opens the create-site screen for the selected server.
2. Choose One Click Apps
Select One Click Apps to open the application catalog instead of a Git deployment or manual upload flow.
Expected result: The app catalog appears with searchable one-click app cards.
3. Select Vaultwarden
Search for Vaultwarden or browse the relevant category, then select the Vaultwarden app card.
Expected result: xCloud opens the Vaultwarden app-create screen for the selected NGINX server.
4. Add site details
Enter a clear Site Title, such as Vaultwarden or Company Password Vault. Add tags if your team uses them for filtering.
Expected result: Your title shows in the Site Title field, and any tags show under Add Tag (optional).
5. Choose Demo Site or Go Live
Choose Demo Site for a quick review deployment, or choose Go Live when your production domain is ready.
Expected result: With Demo Site, a read-only Domain Name field shows the generated demo domain. With Go Live, a Domain Name field appears for you to type your own domain.
6. Click Next
Vaultwarden has no other install fields to fill in. Click Next.
Expected result: xCloud creates the Docker-based Vaultwarden site and shows deployment progress. When it finishes, the Site Overview page shows Web Vault, Admin Panel and Admin Token under Vaultwarden Credentials. Store the token in a secure password manager.
Post-deployment Vaultwarden setup
| Setup area | What to do | Success check |
|---|---|---|
| Domain and SSL | Open the Vaultwarden URL and confirm HTTPS. | The web vault loads without certificate warnings. |
| Admin access | Store the Admin Token securely. See Store the Admin Token. | Only people you trust can open the admin page. |
| Registration | Close sign-ups once your accounts exist. See Close sign-ups. | New users cannot self-register unless allowed. |
| SMTP | Add SMTP for invites. See Add SMTP. | A test invite email is delivered. |
| Bitwarden clients | Point browser/mobile clients to the Vaultwarden URL. | A test item syncs between web vault and client. |
| Backups | Run a backup before real use. See Run a backup. | A recent backup exists and restore steps are known. |
Close sign-ups
Sign-ups start open so you can create your first account. Close them as soon as your team has its accounts.
-
Open your Vaultwarden site in xCloud and click Environment.
-
Change
SIGNUPS_ALLOWED=truetoSIGNUPS_ALLOWED=false. -
Click Save & Redeploy.
-
When the redeploy finishes, open your vault in a private browser window and try to create a test account.
Expected result: xCloud shows Saved — redeploy in progress after step 3. In step 4, Vaultwarden does not create the account. It either shows Registration not allowed or user already exists or does not offer a way to sign up. Vaultwarden’s guide to closing registration explains the setting.
Warning: Vaultwarden says that once settings are saved on the /admin page, the values it stores in config.json override environment settings. If anyone has saved settings there and the test account still goes through, contact support before you store real passwords.
Store the Admin Token
xCloud creates an Admin Token during install, so the admin page at /admin starts on.
- On Site Overview, under Vaultwarden Credentials, copy the Admin Token into a secure password manager.
- Open the Admin Panel address shown there, which ends in
/admin. - Paste the token into the Enter admin token field and click Enter.
Expected result: The Vaultwarden admin page opens on Settings, with Users, Organizations and Diagnostics in the menu. Do not save changes here unless you mean to, because saved settings override the Environment page.
If you do not need the admin page, read Vaultwarden’s guide to turning it off first, or ask support for help.
Add SMTP
Email invites, email login codes and password hints need your own mail provider details. Vaultwarden’s SMTP guide explains each setting.
- Open your Vaultwarden site in xCloud and click Environment.
- Add these lines, using the values from your mail provider:
SMTP_HOST=smtp.example.com
[email protected]
SMTP_PORT=587
SMTP_SECURITY=starttls
SMTP_USERNAME=your-username
SMTP_PASSWORD=your-password
- Click Save & Redeploy.
- When the redeploy finishes, sign in to
/admin, open SMTP Email Settings, enter your own address under Test SMTP and click Send test email.
Expected result: xCloud shows Saved — redeploy in progress after step 3, and the test email reaches your inbox after step 4. If it does not arrive, check the values with your mail provider.
Run a backup
Docker app backups are not on the Free plan. Buying a Cloud VPS moves a Free team to the Starter plan, which includes them. This adds no charge beyond the Cloud VPS price. If you connect your own server on the Free plan, you need to upgrade first. The app stops briefly during each backup and restore, and a restore replaces the current data.
- Under Backup in the site menu, click Previous Backups.
- On the Local Backup tab, click Backup Now.
Expected result: The button changes to Backup running… and a new row shows Running in the Status column. When the backup finishes, that row shows Completed. xCloud’s backup screen says the app stops while its data is read, for seconds on a small app and longer on a large one.
To back up on a schedule:
- Click Backup Settings and turn on Automatic Backup.
- Choose how often it runs and click Save Settings.
Expected result: On Previous Backups, Backup Status Overview shows Automatic Backup: Active.
Vaultwarden updates
Vaultwarden does not update by itself. Your install stays on its version until it is changed, so you decide when to take a new release. Contact support to ask about updating.
Warning: Do not edit only the version number on the Compose page. xCloud sets the image as a version plus an @sha256 value, and the @sha256 value decides which image Docker runs. If you change only the version number, you stay on the old release even though the file looks updated.
- Read the notes on the Vaultwarden releases page.
- Run a backup.
- Contact support to ask about updating, and name the site and the version you want.
After any version change, sign in to your vault at its usual address and check that your items are there.
Security checklist for Vaultwarden hosting
- Use HTTPS before storing real credentials.
- Disable open registration for private teams.
- Keep the admin token out of tickets, docs, and chat.
- Back up persistent data before updates.
- Test restore steps before relying on the vault for critical credentials.
- Limit xCloud dashboard access to trusted team members.
xCloud vs Railway vs Coolify for Vaultwarden
| Platform | Best for | Deployment model | Operational tradeoff |
|---|---|---|---|
| xCloud | Teams that want one-click app creation plus server/site operations in one dashboard. | New Site → NGINX server → One Click Apps → Vaultwarden → Demo Site/Go Live → Next. | You manage the app as an xCloud site. You run backups and choose when to update Vaultwarden. |
| Railway | Users already deploying services on Railway and comfortable with Railway projects. | Template-style deployment on Railway infrastructure. | Review platform storage/runtime settings for a password vault. |
| Coolify | Users who want to run their own self-hosted PaaS layer. | Service/app deployment inside a Coolify instance. | You also maintain the Coolify host and its backups. |
Troubleshooting
| Symptom | Likely cause | Fix |
|---|---|---|
| Vaultwarden page does not load | Deployment unfinished, container stopped, or domain not routed. | Check deployment progress, container health, and domain routing in xCloud. |
| Browser extension cannot sync | Client URL is wrong or HTTPS is not active. | Configure the client with the exact Vaultwarden URL and confirm SSL. |
| Invite, password hint or login code email fails | SMTP is missing or rejected by the mail provider. | Verify SMTP host, sender authentication, and test delivery. |
| Anyone can register | Open registration is still enabled. | Follow Close sign-ups. |
| Data disappears after restart | Persistent storage was not backed up or attached correctly. | Confirm the Vaultwarden data location is persistent and included in backups. |
FAQ
Can I deploy Vaultwarden without writing Docker Compose?
Yes. In xCloud, choose Vaultwarden from One Click Apps and create the site on an NGINX server.
Should I use Demo Site or Go Live?
Use Demo Site for internal validation. Use Go Live for production because a password manager should run on a trusted domain with HTTPS.
What should I back up?
Backup Now and Automatic Backup cover the app’s Docker volumes, where your vault data lives. Also keep your Admin Token and any notes you need to recover the site somewhere off the server.