PassZit

KeePass for teams: from a shared .kdbx file to a password server

For teams that share one KeePass or KeePassXC database file today and want something built for several people: what changes when the passwords move to a PassZit server, how accounts, groups and rights work, how a KeePass export comes in, what happens without the server, how backups work — and what PassZit does not do.

What this guide covers

PassZit is a free, open-source (AGPLv3) password manager for people and teams that runs on your own server, with end-to-end encrypted vaults. It is free with no user limits; MaxZit, the company that makes it, offers optional paid support and onboarding. KeePass and KeePassXC are independent open-source projects that many teams use with a shared file; people who search for "KeePass for teams" often look for a server instead. This guide describes PassZit only — it makes no statements about the other programs — so you can decide whether it fits your team.

What changes with a server

TopicIn PassZit
Where the passwords areOn one PassZit server you run (VM image, ISO, install script or deb/rpm packages); clients get changes from the server
Who can open whatEvery person has their own account and master password; team vaults decide who sees which passwords
Someone leavesDisable the account at once; when they are removed from a vault or the account is deleted, the vault gets a new key
Who did whatAudit log for the server and Who used this item for items of team vaults
What you have to runThe server itself: certificate, reachability, updates and backups (Settings in the console)

The installation is in Install a self-hosted password manager: the README asks for 2 vCPU, 2 GB RAM and a 16 GB disk; there is no Docker image.

One account per person

  • By invitation only: an administrator uses Users → Invite a user; the link works once and for 7 days by default.
  • Own master password and a mandatory second factor (authenticator app, plus security keys or device passkeys if wanted). No administrator can see or reset a master password.
  • Recovery key: each person makes one under My account; it is the only way back after a forgotten master password. The user list shows who has one.
  • Company sign-in (Settings → Company sign-in): Active Directory / LDAP and single sign-on (OpenID Connect, SAML 2.0) decide who may sign in and can keep PassZit groups in step with company groups. The master password always stays.
  • Two account roles: User and Administrator. Administrators manage users and settings but, like everyone else, cannot read vaults they are not a member of.

Vaults, groups and rights

Every user has My vault; shared vaults are under Team vaults. Instead of one file for everything, make one team vault per real use — network devices, a customer, accounting — and give people or groups one of four rights, each including the ones before it: Connect and fill, See passwords, Add and change, Manage.

  • Folders belong to a vault, can be nested and have kinds such as Customer, Site or Data center.
  • Access can have an end date; Tools → Access requests gives more rights for 1 hour to 30 days after a manager approves.
  • Groups are made under Groups; a vault always keeps at least one permanent manager.

The steps, including the key fingerprint check, are in Share passwords with your team.

End-to-end encryption

As described on the security page: the browser derives keys from the master password with Argon2id, encrypts every item — name, user name, password, websites, notes, files — with AES-256-GCM and sends only ciphertext. The server stores an argon2id hash of a separate auth key and never receives the master password. Each shared vault has its own key, sealed to each member's X25519 public key.

PassZit's own limits: the web vault's JavaScript comes from your server, so someone who fully controls the server could serve changed code (the browser extensions bring their own code); malware on a user's computer can read what is typed.

Import a KeePass or KeePassXC export

PassZit does not open .kdbx files. It reads an unencrypted export: its user guide names File → Export → KeePass XML (2.x) for KeePass 2 and Database → Export → CSV file (or XML) for KeePassXC (menus can differ between versions).

  1. Make the export on a trusted computer.
  2. In the web vault choose Tools → Import and pick the file. It is read in the browser; PassZit shows how many items and folders it found and how many are already in the vault.
  3. Choose Keep the folders of the file or Put everything into 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 XML format PassZit takes the title, user name, password, URL and notes, nested groups as nested folders, other fields as own fields (protected ones stay hidden) and one-time code secrets stored in a field named otp or TOTP Seed; entries with only notes become secure notes, and the recycle bin is left out. From CSV it takes the columns it recognises, such as title, user name, password, URL, notes, group and TOTP. Not taken over: attached files (attach them again), the former versions of an entry, and anything else outside these fields.

The import goes into My vault of the person who imports. To fill a team vault, one person imports and then moves items with the Vault field of the item editor, one at a time — plan for that with large files. Imports are recorded in the audit log with the number of items, never their contents.

Browser extensions and daily use

  • Extensions for Chrome, Edge, Firefox (128 or newer), Opera, Brave and Vivaldi, from the Chrome Web Store, Firefox Add-ons and Microsoft Edge Add-ons or from the server's Browser extensions page. They fill logins and one-time codes only on the matching site, offer to save new logins when you switch that on, and fill cards and addresses.
  • Web vault in any modern browser, installable as an app; one unlock for the web vault and the extension.
  • Remote connections: RDP, SSH, WinSCP, WinBox, VNC and Telnet items open through the extension with the MaxZit Launcher on Windows or passzit-helper on Linux — see server and device credentials.
  • Command line: passzit reads logins and one-time codes in scripts on Linux, Windows and macOS.

There are no native mobile apps and no Safari extension yet (both planned).

Without the server

PassZit has no offline mode. The web vault stores nothing for offline use — without the server it shows a short "offline" page — and the extension keeps no copy of the vault on disk. People outside the office need to reach the server: the console answers only to private networks until you allow more under Settings → Network and access, so a VPN is the usual way. If your team needs passwords while the server is down, plan for it: a second server restored from the backup, or each user's own encrypted export kept in a safe place.

Backups

  • Settings → Console backup: a backup of the whole server every day and on request, always encrypted with a passphrase you set, with an optional copy to an SFTP folder on another server. Restore with the appliance menu or passzit-server -restore.
  • Tools → Export → Encrypted PassZit file (recommended): each user can keep an encrypted copy of what they can export, protected with a password of their choice; it can be imported into PassZit again.
  • Settings → Updates and server installs only signed releases and puts the old version back by itself if the server does not come back.

Test a restore onto a second VM before you rely on it.

Test it next to your current file

  1. Keep the current file in use during the test.
  2. Set up a small server from the appliance image, with a DNS name, a trusted certificate (Settings → Certificate; the extension refuses a self-signed one), SMTP and the console backup.
  3. Import a copy of the database as XML into a test account, compare the item and folder counts and check a few entries with own fields and one-time codes. Delete the export file.
  4. Build the team vaults you would really use, invite two or three colleagues with different rights and try the extension in their browsers.
  5. Practise the hard days: a forgotten master password with the recovery key, a lost phone, someone leaving, and a restore of the backup onto a test VM.
  6. Switch over vault by vault, then retire the shared file and its copies.

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.
  • It needs a running server; there is no offline mode and no file you can carry on a USB stick.
  • No .kdbx import: only unencrypted XML or CSV exports; attachments and former entry versions are not taken over.
  • Imports go into the personal vault; items are moved into team vaults one at a time.
  • Exports are an encrypted PassZit file or an unencrypted CSV file.
  • No native mobile apps and no Safari extension (both planned); browser extensions do not use single sign-on.
  • A forgotten master password without a recovery key cannot be recovered by anyone.
  • Paid support from MaxZit is in English.

Next steps

Download PassZit, see all features and the security model, and follow Install a self-hosted password manager and Share passwords with your team. If you compare self-hosted servers, Self-hosted Bitwarden alternative covers installation and encryption in more detail. Questions are welcome in GitHub Discussions (English only); support plans and onboarding are available from MaxZit.

KeePass and KeePassXC are the names of independent open-source projects and belong to their owners. PassZit and MaxZit are not affiliated with, endorsed by or connected to them. The names are used here only to describe what people search for and which exports PassZit's user guide lists for import.