PassZit

A self-hosted 1Password alternative for teams

For teams that use a hosted password manager today and want their passwords on their own server: what changes when you run the server yourself, how vaults, groups and roles work in PassZit, how to bring people on board, how IT staff open RDP and SSH connections without seeing passwords, what the audit log shows — 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. This guide describes PassZit only — it does not compare features or prices of other products — so you can decide whether it fits your team.

From a hosted service to your own server

With PassZit the vaults live on a server you run — the server stores only ciphertext and never receives a master password or a key it could use. That also means the jobs a hosting provider does become yours:

JobHow PassZit helps
Run the serverA ready VM image (OVA, QCOW2, VHDX) or ISO, or one install command on Debian, Ubuntu, AlmaLinux or Rocky Linux; 2 vCPU, 2 GB RAM, 16 GB disk
CertificateSettings → Certificate: Let's Encrypt (also through a Cloudflare DNS record for servers inside your network) or your own certificate
ReachabilityThe console answers only to private networks until you allow more under Settings → Network and access; people outside the office need a VPN or an allowed network
BackupsSettings → Console backup: daily, always encrypted, with a copy to SFTP
UpdatesSettings → Updates and server: signed releases, automatic rollback, optional automatic installation
E-mailSettings → E-mail with your SMTP server for invitations and notices

The installation itself is in Install a self-hosted password manager. Plan for one more thing: nobody, not even an administrator, can reset a forgotten master password. Each user's recovery key is the only way back.

Vaults, folders and rights

Every user has My vault. Shared vaults are listed under Team vaults; whoever makes one manages it, and the gear next to its name opens Members and settings. Rights are given per person or per group with four check boxes, each including the ones before it:

  • Connect and fill — open connections, fill and copy logins without seeing passwords, notes or files;
  • See passwords — see everything in the vault;
  • Add and change — also add, change and delete items;
  • Manage — also members, groups, the name and the vault itself.

Access can have an end date. Folders belong to a vault and have kinds — Customer, Site, Branch office, Department, Data center, Network, Project — and can be nested. A vault always keeps at least one permanent manager: removing the last one is refused, and since 0.9.6 so is taking managers out of a group, or deleting the group, when a vault would be left without one. All steps, with fingerprints and new vault keys when people leave, are in Share passwords with your team.

Roles: administrators, managers, members

PassZit has two account roles, User and Administrator. Administrators invite and manage users, make groups, read the audit log and change the settings — but, like everyone else, they cannot read vaults they are not a member of. Who may do what inside a shared vault is decided by its rights, not by the account role.

  • Settings → Vault policy → Sharing and export can allow only administrators to make shared vaults and can switch exports off.
  • The same policy sets the lock time, clipboard clearing, the minimum master password length (12 by default), the trash period, file limits and the Argon2id settings.
  • Nobody can change their own access in a vault; another manager does it.

There are no finer administrator roles (for example a read-only auditor); instead, the four-eyes principle can make sensitive administrator actions wait for a second administrator.

Bring the team on board

  1. Invite. Accounts come only by invitation: Users → Invite a user with the e-mail address and the role. The link works once and for 7 days by default; with SMTP set up, Also send the invitation by e-mail sends it.
  2. First sign-in. Each person chooses a master password and sets up the mandatory second factor with an authenticator app; security keys and device passkeys can be added later.
  3. Recovery key. Ask everyone to use Make a recovery key under My account on the first day. The user list shows who has one.
  4. Browser extension. Browser extensions in the web vault shows Install in one click for the store of the browser in use (Chrome Web Store, Firefox Add-ons, Microsoft Edge Add-ons). The extension connects through the web vault, so nobody types a password into it.
  5. Groups and company sign-in. Make groups under Groups and give them rights in the team vaults. With Settings → Company sign-in, single sign-on (OpenID Connect or SAML 2.0) and Active Directory / LDAP can decide who may sign in and keep PassZit groups in step with company groups of the same name — invitations are still needed.

The console and its e-mails are in 14 languages, chosen per user; the built-in user guide is in English and Serbian. MaxZit's onboarding packages help with the rollout (in English).

Move the passwords

PassZit's user guide lists 1Password among the programs it imports from, through a CSV export (it names File → Export → CSV; menus can differ between versions of the other program). The import works the same for every format:

  1. Each person exports their own items and imports them with Tools → Import into My vault. The file is read in the browser; the server gets only encrypted items.
  2. PassZit shows how many items and folders it found and how many are already there; Skip items that are already in the vault avoids duplicates.
  3. Shared items are imported by one person and moved into the team vault with the Vault field of the item editor, one item at a time.
  4. Delete the export file afterwards — it holds the passwords unencrypted.

From CSV files PassZit takes the name, websites, user name, password, notes, one-time code secret, folder and favourite flag when the file has such columns. Attached files are not part of export files — attach them again. Passkeys are not imported; save them again with the extension's Use PassZit for passkeys. Check a few items after a test import before everyone moves.

RDP, SSH and WinBox without seeing the password

For IT teams, a login can be a remote connection: Remote Desktop (RDP), SSH with a password or a key, WinSCP (SFTP), WinBox (MikroTik), VNC or Telnet. The small MaxZit Launcher for Windows — downloaded under Launcher in the web vault, installed for the Windows user without administrator rights and paired with Pair this browser — opens the connection with the stored login. On Linux, passzit-helper does the same.

In a team vault every member has Connect and fill, so a technician can connect to a server without being shown its password, and each connection is recorded under Who used this item. For scripts, the passzit command line reads logins and one-time codes, and passzit rotate changes device passwords over SSH (Linux, MikroTik RouterOS, Windows with OpenSSH) and saves the new ones.

Limits: WinBox takes the password only on its command line, where other programs of the same Windows user can read it while WinBox runs (PassZit warns before). Connect and fill is a convenience, not a lock: whoever can fill a password can find it out with some effort.

Sharing outside the team

  • Secret links (under Tools) give a text or a file of up to 8 MB to someone without an account, for 1 hour to 30 days and 1–100 openings; the key is the part of the link after #, which browsers do not send to the server. Recipients must be able to reach the server.
  • Access requests let people ask for more rights or for a vault for 1 hour to 30 days; the access ends by itself.
  • Emergency access under My account names up to five people who may read a user's personal vault after a waiting time the user can stop.

Audit log and approvals

  • Audit log (administrators): sign-ins, failed attempts, blocks, invitations, user and settings changes, imports and exports, requests and approvals. Every entry contains a hash of the previous one, and the page shows whether the chain is intact. It never contains passwords or item contents.
  • Who used this item (vault managers): in team vaults, who showed, copied or filled a password, opened a connection, or changed or restored a password — with time, client, device and IP address. These reports come from the clients; someone who changes their software can avoid them.
  • Four-eyes principle (Settings → Vault policy): deleting a user, resetting a second factor, making an administrator and changing security settings wait under Approvals for a second administrator.
  • With SMTP set up, administrators get e-mail about certificates, failed backups and waiting approvals.

Run a pilot next to your current service

  1. Keep the current service. Import the appliance as a small VM, give it a DNS name and a trusted certificate, set up SMTP and the console backup.
  2. Pick a small group — for example the IT team — and invite them. Make one team vault per real use (network devices, a customer, marketing accounts) and give groups the rights they need.
  3. Import test copies and check the items. Try the extension in the browsers your team uses, the Launcher on a Windows PC, and a secret link to an outside address.
  4. Practise the hard days: a lost phone (an administrator resets the second factor), a forgotten master password with the recovery key, someone leaving (remove them, let the vault get its new key), and a restore of the console backup onto a test VM.
  5. Then roll out group by group, and switch the old service off only when everyone has moved and the exports are deleted.

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 apps and no Safari extension (both planned). On phones the web vault can be added to the home screen, but it works only while the server is reachable.
  • You run the server: availability, backups and reachability from outside are your responsibility.
  • Two account roles only; finer control comes from vault rights and the four-eyes principle.
  • Browser extensions do not use single sign-on; they sign in with the master password and the authenticator code.
  • Imports read unencrypted export files only and do not take over attachments or passkeys; items are moved into team vaults one at a time.
  • 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 run your own password server already, Self-hosted Bitwarden alternative covers installation, encryption and import in more detail. Questions are welcome in GitHub Discussions (English only); support plans and onboarding are available from MaxZit.

1Password is a trademark of its owner. PassZit and MaxZit are not affiliated with, endorsed by or connected to it. The name is used here only to describe what people search for and which export PassZit's user guide lists for import.