Passwords
A team vault on your own instance
Deploy Vaultwarden with managed Postgres and a public HTTPS URL. Bitwarden apps talk to your hostname. You pay for compute — not per seat.
TemplatesVaultwarden
What you get
A private vault, packaged to ship
Logins and shared collections on your instance — Postgres, a data volume, and the public URL are wired at deploy.
Bitwarden apps
Point the browser extension and the mobile apps at this hostname. They speak the Bitwarden API to your instance.
First account on the URL
Open the hostname and create the account. There is no pre-seeded password.
Public HTTPS URL
The https://…stackblaze.app hostname is the server URL you paste into Bitwarden clients.
Managed Postgres
The vault database lives in CloudNativePG. Attachments persist on the /data volume.
Organizations when you need them
Share collections with the team from inside the vault. Invitations stay on this instance.
Dedicated instance
Secrets stay on this instance — not in a shared vendor account.
See Vaultwarden in action
Deploy in seconds
One click. Postgres pre-wired.
Pick the Vaultwarden template. StackBlaze creates the server and Postgres and gives you a hostname.
This stack
Web
Vaultwarden server
PostgreSQL
managed database · TCP:5432
Tenant
managed other
platform SMTP when the pipeline has mail
- Stack
- Vaultwarden + PostgreSQL
- First login
- Create an account on the public URL
- Clients
- Bitwarden apps use this hostname as the server
After you deploy
- 1
Open the public URL
The hostname is on the app page after deploy. Create the first account there.
- 2
Point Bitwarden clients at it
In the extension or mobile app, set the server URL to this hostname before you log in.
- 3
Invite the team
Create an organization inside the vault when more than one person needs shared logins.
Running Vaultwarden on StackBlaze
How the instance is wired
Vaultwarden and Postgres ship together. The public hostname is the only server URL clients need.
Postgres holds the vault
Accounts and ciphers live in the attached database. Restart the server and the vault is still there.
Attachments sit on /data
Files and icon cache persist on the volume. The database is not a file store.
Clients use the hostname
Browser and mobile apps must use this HTTPS URL as their self-hosted server. A custom domain replaces it when you attach one.
Back up the database
If the vault matters, back up Postgres. Losing the database loses the ciphers.
Compare
Vaultwarden on StackBlaze vs a hosted password manager
| Feature | Vaultwarden on StackBlaze | Hosted password manager |
|---|---|---|
| Data location | The vault lives on your StackBlaze instance. | Secrets live in vendor-operated infrastructure. |
| Install model | One-click template. First account on the public URL. | Create a vendor account and use their shared platform. |
| Clients | Bitwarden browser and mobile apps, with your server URL. | The vendor’s apps against their cloud. |
| Operations | You control updates, scale, backups, and the instance lifecycle. | The vendor operates the platform and the limits. |
| Billing | Compute, storage, and bandwidth. No per-seat fee. | Usually priced per seat or per plan. |
This template is a Bitwarden-compatible server plus Postgres. Clients are the Bitwarden apps, pointed at your hostname.
FAQ
Common questions
Open the public URL and create an account. In the Bitwarden extension or mobile app, set the self-hosted server URL to that same hostname, then sign in.
Ready to deploy Vaultwarden?
One click. Dependencies pre-wired. No infrastructure to manage.