Vaultwarden Hosting

How Vaultwarden works

Vaultwarden implements much of the Bitwarden client API so official Bitwarden browser extensions, desktop clients, mobile apps, and the bundled web vault can connect to a self-hosted server. Users can store vault items, organise collections, share through organisations, attach files, create Sends, and use supported multifactor methods depending on configuration.

Compatibility is not ownership or affiliation. Vaultwarden is not associated with Bitwarden, and official Bitwarden support for non-official servers is limited. A future client or API change can affect compatibility. Vaultwarden also does not implement Bitwarden Secrets Manager, so it should not be sold as a substitute for that separate product.

Key Vaultwarden features

The catalogue sets SIGNUPS_ALLOWED=true, which leaves account registration open while the value remains enabled. Anyone who can reach the public address may create an account during that period. Administrators should create the intended accounts promptly, review registration settings, and avoid publishing the address broadly before the access model is secured.

Application email is disabled. Invitation delivery, email verification, password hints, mail-based multifactor methods, emergency-access messages, and other email workflows cannot send from this hosted installation. Losing the master password can make vault data inaccessible; the hosting service cannot recover a user’s master password or decrypt end-to-end encrypted vault contents.

Vaultwarden vs Bitwarden

Vaultwarden and Bitwarden clients share a familiar vault workflow because Vaultwarden implements compatible APIs. Bitwarden is the official vendor, offers a managed cloud service and official self-hosted products, maintains client and server releases, and provides commercial plans and support paths. Vaultwarden is a separate community server focused on lower resource use and self-hosted compatibility.

Bitwarden may be the stronger choice for organisations requiring official vendor support, documented enterprise deployment, or services not implemented by Vaultwarden. Vaultwarden can suit smaller trusted deployments whose operators understand the compatibility, support, registration, email, backup, and recovery responsibilities.

Who uses Vaultwarden

Individuals keep passwords and secure notes in compatible clients, families share selected collections, and small teams use organisations for limited credential sharing. The server can reduce reliance on a provider-hosted vault, but it also makes the operator responsible for availability, updates, access policy, and recoverable encrypted data.

Vaultwarden should not be used as a reason to share master passwords, store recovery codes only inside the same vault, or expose open registration indefinitely. Highly regulated or enterprise environments should evaluate the official Bitwarden offering and obtain appropriate security, legal, and compliance review.

Self-hosting Vaultwarden: requirements and cost

Vaultwarden resource use grows with users, organisations, vault items, attachments, Sends, synchronisation traffic, web-vault sessions, and client activity. The catalogue provisions no PostgreSQL or MariaDB service and persists /data. The software itself is free to run, but attachment storage and frequent multi-device synchronisation can exceed the needs of a small text-only personal vault.

On AvaHost, Vaultwarden uses Plan 1 at €2. The hosted Vaultwarden package includes one-click deployment, a custom domain with automated HTTPS, automatic application updates, and scheduled backups. Official Bitwarden support, Secrets Manager, client subscriptions, email delivery, master-password recovery, recipient identity verification, compliance certification, security assessment, and external multifactor services are not included. Close or control registration after onboarding, protect the server address, and keep tested encrypted recovery material outside the live instance.