Put Passwords in Their Place.Give the Right People the Right Access.

Our Vaultwarden hosting gives your passwords and shared credentials a dedicated home. Connect compatible clients to your workspace address, organise saved items and give selected people access to shared collections.

Use our plan listing for the current resources and service scope. The project overview describes Vaultwarden’s application capabilities.

No. Vaultwarden is an independent community project that implements the Bitwarden client API. It is separate from Bitwarden’s hosted service, subscriptions and support.

Compatible Bitwarden clients can connect to it, but server and client versions need to work together. Test sign-in, sync and sharing with the clients your team uses.

Plan around the number of users, saved items and especially file attachments.

• Estimate the data you will import and expected growth.
• Compare current plan resources and billing terms.
• Confirm backup, update and support responsibilities for the selected plan.

Start with a small team trial before moving every important login.

This offer is prepared for a Vaultwarden workspace. For an environment where you install and administer unrelated server applications, choose our VPS hosting.

1. Open the client’s self-hosted server setting before signing in.
2. Enter your workspace’s HTTPS address and save it.
3. Sign in, then check that a test item appears on another connected device.

Use the client instructions for the location of that setting. Your Vaultwarden account belongs to that server address.

Yes. Use a personal vault for individual items and organisation collections for shared work. Adding someone to your team should not mean giving them every saved login.

• Group shared items by team or responsibility.
• Assign access to the people who need those items.
• Test with an ordinary member account before rollout.

When someone leaves, remove their access and rotate credentials they could have copied or retained.

You can control new registrations. Decide how approved people will join, then test the invitation and account-creation process before closing public sign-ups.

Keep the administrative interface protected separately from user registration. Follow the registration guide for configuration details.

Vaultwarden supports multiple two-step login methods. Choose a method supported by your current server and clients, and keep its recovery information somewhere you can reach if the main device is unavailable.

Test recovery before the team relies on it. A two-factor recovery code is not a replacement for a forgotten master password.

1. Keep a recoverable copy of the original vault.
2. Import a small sample using a supported format.
3. Check usernames, website addresses, notes and shared-item ownership.
4. Move the remaining items once the sample is correct.

Attachments may need separate handling. Unencrypted exports expose their contents, so protect them during migration and remove temporary copies after verification.

The web vault needs HTTPS for the browser cryptography features it uses. Set the final workspace address and a valid certificate before inviting users.

Check both browser access and client connections at that address. See the project’s usage notes.

A recoverable backup includes the database and attachments, with the configuration needed to recreate the service. External database setups need an appropriate database backup as well as the relevant files.

• Keep a protected copy away from the running instance.
• Record retention and who can access backup data.
• Test a restore and check saved items and attachments.

Use the backup guide to define the scope. A synchronised client is not a substitute for this process.

Do not assume hosting support can recover it. A server backup preserves encrypted data; it does not reveal the master password or automatically unlock the vault.

Recovery options depend on features configured beforehand, such as eligible organisation recovery or emergency access. Establish and test a recovery process before storing essential credentials. Without a usable recovery path, the encrypted contents may be inaccessible.

Check our selected plan for the scope of ongoing maintenance. Assign an owner for user access, client compatibility and recovery even when server tasks are managed for you.

Before a significant update, keep a usable backup. Afterwards, test sign-in, a saved login, sync and a shared collection with the clients your team actually uses.