What this guide covers
PassZit is a free, open-source (AGPLv3) password manager that runs on your own server. Every user has an end-to-end encrypted vault for logins, one-time codes, secure notes, cards, SSH keys and files; teams share vaults with rights per person. The server stores only ciphertext. If you are comparing tools because you searched for a self-hosted Bitwarden alternative, this guide shows what installing and rolling out PassZit looks like in practice.
- What you need
- Install the server
- First sign-in and the first administrator
- A certificate the browsers trust
- Invite your team
- Master password and recovery key
- Install the browser extension
- Import passwords from another program
- How the encryption works
- Back up the server
- Updates
- Limits to know
- Next steps
What you need
- A virtual machine on VMware, VirtualBox, Proxmox VE/KVM or Hyper-V, or a physical server, with 2 vCPU, 2 GB RAM and a 16 GB disk — or an existing 64-bit Debian 12+, Ubuntu 22.04+, AlmaLinux or Rocky Linux 9+ server (x86-64 or ARM64).
- Browsers reach the server on TCP 8443. PostgreSQL is set up by the installer and the images.
- For the browser extensions: a DNS name for the server and a certificate the browsers trust (see below).
- Optionally an SMTP server, so PassZit can send invitations and notices by e-mail.
Install the server
There are four ways; all are on the download page and every release is signed.
| Way | Best for |
|---|---|
| VM image: OVA (VMware, VirtualBox), QCOW2 (Proxmox VE, KVM), VHDX (Hyper-V generation 1) | Import, start, sign in — Debian, PostgreSQL and PassZit are ready |
| Appliance ISO | A new VM or a physical server; the unattended installation erases the first disk |
| Install script | An existing Debian, Ubuntu, AlmaLinux or Rocky Linux server |
| Packages (deb, rpm; amd64, arm64) | Your own PostgreSQL and configuration management |
VM image or ISO: start the VM. Its screen shows the console address and the setup token. On the VM's console you can sign in as pzadmin (first password passzit, changed at the first sign-in): a menu sets the network, the server name and the time zone, shows the setup token again and restores backups. Only ports 22 (SSH) and 8443 are open.
Install script: as root on the server:
curl -fsSL https://github.com/Max-Zit/passzit/releases/latest/download/install.sh | sudo sh
The script installs PostgreSQL, downloads the newest release, checks its signature, creates a database with a random password, starts the service and prints the address and the setup token. Options such as --version, --db (an existing PostgreSQL database) or --no-auto-updates are passed with sh -s --.
Packages: install the deb or rpm, set PASSZIT_DB in /etc/passzit/server.env and run systemctl start passzit-server. The setup token is in /var/lib/passzit/setup-token.txt.
First sign-in and the first administrator
- Open
https://<server>:8443. A fresh server uses a self-signed certificate; the browser warns about it once — accept it. - Enter the setup token, your e-mail address and a master password. Your browser now makes your keys; this takes a second. This first account is the administrator.
- Scan the QR code with an authenticator app (Microsoft Authenticator, Google Authenticator, Authy, 2FAS …). Two-factor sign-in is mandatory for every account. Keep the ten recovery codes; each one replaces the app once.
- Make a recovery key (see below) and add your first login with New item.
Later you can add security keys (YubiKey and others) or a passkey of your device under My account as a second factor.
A certificate the browsers trust
The browser extensions refuse self-signed certificates, so give the server a real one before you roll out the extension. Under Settings → Certificate either upload a certificate (from your company CA or bought; PEM with the intermediate certificates and the private key) or choose Let's Encrypt. Let's Encrypt needs a public DNS name and checks it over port 80 of the server or through a DNS record at Cloudflare — the second also works for a server that is reachable only inside your network. The certificate is used at once, without a restart; the DNS of your network must point the name to the server.
Invite your team
Accounts are made only by invitation. Under Users → Invite a user enter the e-mail address and the role (User or Administrator). PassZit shows the invitation link once; send it to the person. The link works once and for 7 days by default. If you set up an SMTP server under Settings → E-mail, tick Also send the invitation by e-mail and PassZit sends it for you.
The invited person chooses a master password and sets up two-factor sign-in, like you did. Administrators can disable users, reset a lost second factor and withdraw open invitations. To share passwords, make a shared vault and give people or groups access to it.
Company accounts can be connected under Settings → Company sign-in: single sign-on with OpenID Connect or SAML 2.0, and Active Directory / LDAP. The master password always stays, because it is the key to the vault.
Master password and recovery key
The master password never leaves the user's browser. That is the point of end-to-end encryption, and it has a consequence: nobody — not the administrator, not MaxZit — can open a vault without the master password or the recovery key. Administrators cannot see or reset master passwords.
- A passphrase of four to six random words is easy to remember and hard to guess. The vault policy sets a minimum length (12 characters by default).
- Under My account, Make a recovery key shows a key of 32 letters and digits, only once. Print it or write it down and keep it offline — not in the vault and not next to your phone.
- With the recovery key and a code of the authenticator app, a user who forgot the master password sets a new one on the sign-in page. Without a recovery key the vault is lost; the administrator can only delete the account and invite the person again with an empty vault. The user list shows who has made a recovery key.
Ask everyone to make a recovery key on the first day.
Install the browser extension
The extension fills logins and one-time codes only on the site they belong to, offers to save new and changed logins, fills cards and addresses into payment and shipping forms and makes passwords. Install it from the store of your browser, which keeps it up to date:
- Chrome Web Store — Chrome, Brave, Opera and Vivaldi
- Firefox Add-ons — Firefox 128 or newer
- Microsoft Edge Add-ons — Microsoft Edge
The links are on the download page. The PassZit server offers the same: Browser extensions in the menu of the web vault shows Install in one click with the store of the browser you use, and the packages of its own version for installation by hand.
- Click the PassZit icon, enter only the address of your server (for example
https://vault.example.com) and click Connect with the web vault. Allow the browser to let PassZit talk to that server. A port in the address, such as:8443, works in every browser, Firefox included. - The web vault opens; sign in there if you are not signed in yet.
- The vault asks whether to connect the extension in this browser — click Connect. No password or code is typed in the extension.
The web vault and the extension share one unlock: unlock one and the other opens too, lock one and both lock.
Import passwords from another program
Each user imports into their own vault. Export from the old program first, then choose Tools → Import in the vault and pick the file. PassZit recognises the format, shows how many items and folders it found and how many are already in the vault, and lets you keep the folders of the file and skip duplicates.
| From | Export there |
|---|---|
| Chrome, Edge, Brave, Opera, Vivaldi | Password manager → Settings → Export passwords (CSV) |
| Firefox | about:logins → … → Export passwords (CSV) |
| Safari | File → Export → Passwords (CSV) |
| Bitwarden | Tools → Export vault → .json or .csv, not the encrypted variant |
| KeePass 2 / KeePassXC | KeePass XML (2.x) / CSV or XML |
| 1Password | File → Export → CSV |
| LastPass | Advanced options → Export (CSV) |
The file is read in the browser; the server receives the items only encrypted. Logins, notes, websites, own fields, folders, favourites and TOTP secrets are taken over (from Bitwarden also cards, identities and SSH keys). Attached files are not part of these export files. Delete the export file afterwards — it holds the passwords unencrypted.
How the encryption works
The browser derives a master key from the master password with Argon2id (64 MiB, 3 passes). From it come two keys: an auth key that is sent at sign-in — the server stores only an argon2id hash of it — and a wrap key that unlocks the user's random account key. Every item, including its name, user name, websites and notes, is encrypted with AES-256-GCM under the key of its vault; shared vaults have their own key, sealed to each member's X25519 key. The server sees ciphertext, ids, sizes and timestamps, never the master password or a key it could use. Details are on the security page and in docs/ARCHITECTURE.md of the repository.
Back up the server
Settings → Console backup writes a backup every day (and on request with Back up now) to /var/lib/passzit/backups: the database with all vaults, the server's secret key and the console certificate — everything a new server needs. A backup is always encrypted with a passphrase you set; keep that passphrase somewhere else. Each backup can also be copied to an SFTP folder on another server. To restore, use the appliance menu, or stop the service and run passzit-server -restore as described in the built-in guide.
Updates
Settings → Updates and server shows the running and the newest version. Install checks the signature again, backs up the database and the program, installs the update and checks that the server comes back — if not, it puts the old version and the database back by itself. Automatic installation at a chosen hour can be switched on there. The Stable channel gets releases; Testing also offers release candidates, for a test server. On a script installation, running the installer again also updates PassZit and keeps all data.
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.
- There is no native mobile app. On phones the web vault can be added to the home screen and opens in its own window, but nothing is stored for offline use — without the server you see an "offline" page.
- A forgotten master password without a recovery key cannot be recovered by anyone.
- The browser extensions need a trusted certificate, and they sign in with the master password and the authenticator code — not with single sign-on.
- As with every web vault, the web vault's JavaScript comes from the server, so a fully compromised server could serve changed code; the extension brings its own code.
- There is no Docker image; install with an image, the script or the packages. The built-in user guide is in English and Serbian.
Next steps
Download PassZit, look at all features — shared vaults, secret links, emergency access, remote connections, the command line — or read the user guide that is built into the console (documentation). How to set up shared vaults for a team is in the guide Share passwords with your team. Questions are welcome in GitHub Discussions; companies can get commercial support from MaxZit.