Historical evidence: the v0.39.7 published compatibility record
records passing Vault phases through backup and restore. The latest
projected lifecycle record, v0.53.10,
grades standalone Vault
unverified, with v0.46.8 as its last verified
release. This is not a runtime validation of the current release v0.54.2.
Owner setup prepares an invitation only. Neither that setup nor the
historical phase record proves Bitwarden client registration, sign-in
or encrypted-entry sync after recovery.vault workload. The initial Basement and Cloud StackSpecs do not select it. Passwords is part of the broader Vault use case, alongside planned service-secret and Bitcoin extensions.
Applications
Vaultwarden
The Bitwarden-compatible server behind Passwords: released contract, owner setup and client enrollment.
Before you start
- Decide who gets an account and which registration policy you want.
- Keep recovery material outside the server.
- Confirm that your backups cover the Vaultwarden data volume, and practice a restore before the vault holds secrets you cannot recreate.
Get the Bitwarden clients
Vaultwarden is compatible with the official Bitwarden clients; you do not need a Vaultwarden-specific app. Install any of the clients from bitwarden.com/download: browser extensions, desktop apps for Windows, macOS and Linux, the iOS app from the App Store, the Android app from Google Play, or the Bitwarden CLI. Point each client at your own server before you sign in:- On the client’s login screen, open the Logging in on menu (desktop app: Accessing) and choose Self-hosted.
- Enter your generated Passwords route as the Server URL.
- Sign in or accept your invitation. Every client you enroll uses the same self-hosted server URL.
