PassZit

Self-hosted Bitwarden alternative: what PassZit covers and what it does not

For people who already run their own password server and are looking at another one: how PassZit is installed, how its encryption works, what its browser extensions do, how an unencrypted export in the Bitwarden format comes in, how the server is backed up and how company sign-in, passkeys and one-time codes work — each with what PassZit does not do, and how to try it next to the server you have.

What this guide covers

PassZit is a free, open-source (AGPLv3), self-hosted password manager with end-to-end encryption, made by MaxZit. It is one server program with a PostgreSQL database, a web vault, browser extensions and a command line. This guide describes PassZit only — it does not compare features or prices of other products — so you can check it against what your own server does today.

At a glance

AreaIn PassZitNot in PassZit
InstallationVM images (OVA, QCOW2, VHDX), appliance ISO, install script, deb/rpm packages; amd64 and arm64No Docker image
EncryptionArgon2id in the browser, AES-256-GCM per item, X25519 for shared vaultsThe web vault's code comes from the server (the extensions bring their own)
ClientsWeb vault (installable as an app), extensions for Chromium browsers and Firefox, command lineNo native mobile app, no Safari extension, no offline copy
ImportUnencrypted Bitwarden JSON or CSV, plus browsers, KeePass/KeePassXC, 1Password, LastPass, CSVNo encrypted exports of other programs; no attachments, passkeys or password history from the file
Sign-inMandatory second factor, security keys and passkeys, LDAP / Active Directory, OIDC and SAMLExtensions do not use single sign-on
OperationEncrypted daily console backup with SFTP copy, signed self-update with rollback—

Installation

PassZit is one program, passzit-server, with a PostgreSQL database. There are four ways to install it, all on the download page:

  • VM image — OVA (VMware, VirtualBox), QCOW2 (Proxmox VE, KVM) or VHDX (Hyper-V generation 1) with Debian, PostgreSQL and PassZit ready. On the VM's console, the user pzadmin gets a menu for the network, the server name, the time zone, the setup token and restores. Only ports 22 and 8443 are open.
  • Appliance ISO — for a new VM or a physical server; the unattended installation erases the first disk.
  • Install script on Debian 12+, Ubuntu 22.04+, AlmaLinux or Rocky Linux 9+: curl -fsSL https://github.com/Max-Zit/passzit/releases/latest/download/install.sh | sudo sh. It checks the release signature, installs PostgreSQL, creates a database with a random password and prints the address and the setup token. --db uses an existing PostgreSQL database.
  • Packages (deb, rpm) with a hardened systemd service; set PASSZIT_DB in /etc/passzit/server.env and start passzit-server.

The README asks for 2 vCPU, 2 GB RAM and a 16 GB disk. The console listens on HTTPS port 8443 and answers only to private networks until you allow others under Settings → Network and access. There is no Docker image; if you run everything else in containers, use a small VM with the appliance image. The step-by-step version is in Install a self-hosted password manager.

The encryption model

As described in the security page and docs/ARCHITECTURE.md of the repository:

  • The browser derives a master key from the master password with Argon2id (64 MiB, 3 passes by default; the vault policy can change memory, passes and lanes).
  • From it come an auth key, which the server stores only as an argon2id hash, and a wrap key that never leaves the browser and opens the random account key.
  • Every item — name, user name, password, websites, notes, fields, folder and history — is encrypted with AES-256-GCM. Attached files and item documentation are encrypted in the browser too.
  • A shared vault has its own key, sealed to each member's X25519 public key. PassZit shows the key fingerprint the first time you share with someone and warns when a confirmed key changes; a vault gets a new key when someone leaves it.

What PassZit does not protect against, in its own words: the web vault's JavaScript comes from your server, so someone who fully controls the server could serve changed code; people who join a vault through a group get access without a fingerprint confirmation; malware on a user's computer can read what is typed. The browser extensions bring their own code, which the server cannot change. Nobody can reset a forgotten master password — only the user's recovery key opens the vault again.

Browser extensions

The PassZit extension is in the Chrome Web Store (Chrome, Brave, Opera, Vivaldi), Firefox Add-ons (Firefox 128 or newer) and Microsoft Edge Add-ons; links are on the download page. The server also offers it under Browser extensions in the web vault, with Install in one click for the store of the browser in use and its own packages for installation by hand.

  • Connecting: enter only the server address and click Connect with the web vault; you sign in in the web vault and confirm there. The server may run on its own port, such as 8443. It needs a certificate the browser trusts — the extension refuses the self-signed certificate of a fresh server (Settings → Certificate: your own or Let's Encrypt).
  • Filling: a login is offered only on its own website (Public Suffix List), only in visible fields of the top page, never in frames of other sites, and a login saved for HTTPS is not offered on plain HTTP. One-time codes are filled on the page that asks for them.
  • Saving: after you switch on Offer to save new and changed logins, the PassZit icon shows a number; PassZit never shows anything inside the web page.
  • Cards and addresses fill payment and shipping forms — only empty fields, only on HTTPS pages, only in the top page, and for a card after a question.
  • One unlock: the web vault and the extension of the same server unlock and lock together. Windows Hello, Touch ID or a phone's screen lock can unlock the web vault through a passkey (WebAuthn PRF).

Not available: an extension for Safari, single sign-on in the extension (it signs in with the master password and the authenticator code), and filling into payment fields that sit in a payment provider's frame.

Import a Bitwarden-format export

PassZit's importer reads the unencrypted Bitwarden export, as .json or .csv. An encrypted export is refused with a message asking for an unencrypted one. PassZit recognises a file by its content, not by the program that made it: a JSON file with an items list is read as the Bitwarden format.

  1. Make the unencrypted export in your current program.
  2. In the PassZit web vault choose Tools → Import and pick the file. The file is read in the browser; PassZit shows the format, the number of items and folders and how many are already in the vault.
  3. Choose Keep the folders of the file or a new folder, leave Skip items that are already in the vault on, and import.
  4. Delete the export file — it holds every password unencrypted.

From the Bitwarden JSON format PassZit takes logins with their websites, one-time code secrets and own fields (hidden fields stay hidden), secure notes, cards, identities, SSH keys, folders and favourites. Not taken over: attached files (not part of export files — attach them again), passkeys stored in the file (save them again with the extension), the password history of an item, and any grouping other than folders. Each user imports into their own vault; items for a team are moved afterwards with the Vault field of the item editor, one item at a time. Imports and exports are recorded in the audit log, with the number of items but never their contents.

Second factor, passkeys and one-time codes

  • Account sign-in: two-factor sign-in is mandatory for every account — an authenticator app (TOTP) with ten recovery codes. Under My account → Security keys and passkeys a security key (YubiKey, Titan …) or a device passkey can replace the app code in the web vault; the extensions still use the app code. An administrator can reset a lost second factor; the vault is not affected.
  • Website passkeys: with Use PassZit for passkeys on, the extension offers Save in PassZit when a website makes a passkey and keeps it as an encrypted vault item, usable in every browser with the extension. PassZit does not send a "user verified" flag, so a website that requires verification gets the browser's own passkeys.
  • One-time codes for websites: a login can hold the Authenticator key (TOTP), pasted or read from a QR code — in the web vault from a picture, in the extension with Read an authenticator QR code on this page. Whoever opens the vault then has both factors; for the most important accounts PassZit's guide suggests a separate authenticator app.

Backups and updates of the server

Settings → Console backup writes a backup every day and on request (Back up now) to /var/lib/passzit/backups: the database with all vaults, the server's secret key and the console certificate. Backups are always encrypted with a passphrase you set, and each can be copied to an SFTP folder on another server. Restore with the appliance menu or passzit-server -restore; the restore replaces the whole database in one step. If you back up yourself instead, take the database and secret.key — the server's own secrets, such as second factors, need it.

Settings → Updates and server installs only signed releases: it backs up the database and the program, installs the update and puts the old version back by itself if the server does not come back. Automatic installation at a chosen hour and a Testing channel for release candidates can be set there.

Users can also keep a copy of their own vault: Tools → Export → Encrypted PassZit file (recommended), protected with a password of their choice.

LDAP and single sign-on

Settings → Company sign-in adds who may sign in; the master password always stays, because it is the key to the vault, and accounts still come only by invitation.

  • Single sign-on with OpenID Connect (Microsoft Entra ID, Google, Okta, Keycloak …) or SAML 2.0 (ADFS, Entra ID, Okta …) for the web vault.
  • Active Directory / LDAP: at every sign-in, also of extensions and the command line, PassZit looks the address up with a service account; missing or disabled accounts cannot sign in. Look up tests the settings.
  • Both can keep PassZit groups in step with company groups of the same name, so access to shared vaults follows the directory.

There is no SCIM provisioning and no sign-up without an invitation. How shared vaults, groups and rights work is in Share passwords with your team.

Test PassZit next to your current server

  1. Keep your current server running. Import the PassZit appliance as a small VM with its own DNS name and give it a trusted certificate before you try the extension.
  2. Use test accounts first. Invite two or three people, make a shared vault and a group, and try the rights, the fingerprint check and removing someone from the vault.
  3. Import a copy, not everything. Make an unencrypted export of a test account, import it, compare item counts and check a few cards, identities, SSH keys and one-time codes. Delete the export file.
  4. Install both extensions only where you test. PassZit's offer to save logins is off until you switch it on, and Use PassZit for passkeys too, so the two extensions do not both ask while you compare.
  5. Test the server's backup. Run Back up now, restore the backup onto a second test VM and sign in there.
  6. Go through the limits below with the people who will use it, especially mobile use and the extension's sign-in.

Limits to know

  • PassZit is under active development: the first public release was 0.9.0 in November 2026, and new versions come out often.
  • No native mobile app and no Safari extension (both planned). The web vault can be added to a phone's home screen but stores nothing for offline use.
  • No Docker image; install with an image, the script or the packages.
  • The importer reads unencrypted export files only; attachments, passkeys and password history in the file are not taken over.
  • Extensions need a trusted certificate and sign in with the master password and the authenticator code, not with single sign-on.
  • A forgotten master password without a recovery key cannot be recovered by anyone.
  • The interface is in 14 languages; the built-in user guide is in English and Serbian.

Next steps

Download PassZit, read about all features and the security model, or start with the guides Install a self-hosted password manager and Share passwords with your team. Teams moving from a hosted service will find more in A self-hosted 1Password alternative for teams. Questions are welcome in GitHub Discussions (English only); companies can get commercial support from MaxZit (in English).

Bitwarden is a trademark of its owner; Vaultwarden is the name of an independent project. PassZit and MaxZit are not affiliated with, endorsed by or connected to either. The names are used here only to describe what people search for and which export format PassZit can import.