When you trust a password manager with your most sensitive information, you should be able to verify how it protects it. That's why we're taking Passwork towards open source.

Our first steps are planned for the end of 2026, with the transition to an open source model expected in the first half of 2027.

Why we're moving towards open source

Companies are paying closer attention to how their software vendors handle security. Growing regulatory requirements are driving this shift. Vendor transparency becomes an increasingly important part of security assessments.

Moving towards open source reflects our commitment to meeting evolving customer expectations and building a product that businesses can rely on in the long term.

Opening our code will also bring greater accountability. It encourages us to maintain high engineering standards and creates opportunities for feedback from the security community.

“A password manager asks you to trust it with your most sensitive data. That trust should rest on what you can check. Open source lets customers verify our security claims directly.” – Alex Muntyan, CEO at Passwork

What this means for our customers

Customer deployments, data and commercial relationships with Passwork remain unchanged. Passwork's on-premises, zero-knowledge architecture stays as it is: encryption and decryption happen on the customer's side, and Passwork has no access to customer passwords, vaults or infrastructure.

We're working towards an open source model in which the source code will be publicly available, with additional features for business customers offered commercially.

Our first steps: Source-available code and independent penetration testing

Moving towards open source requires preparation. We're working on the codebase and supporting documentation to make the first release useful for customers and security researchers.

Our first milestone is making the source code available to interested parties through the Passwork client portal.

From that point, any customer, independent researcher or security lab will be able to:

  • obtain the full source code available from our customer portal;
  • build Passwork independently and compare the result with the distribution customers receive;
  • audit the code, architecture and build process.

In parallel, we're preparing an independent penetration test and are currently selecting a security testing partner.

Together, these steps will help us prepare for the next stage of the transition.

Our roadmap

Milestone Timeline
Source code and build instructions become available to customers By the end of 2026
Independent penetration test begins By the end of 2026
Passwork transitions to an open source model with paid business features H1 2027

What's next

There is still technical work ahead, and we'll share more details as we reach each milestone.

We see open source as an important part of Passwork's future, helping us strengthen the product and meet the changing expectations of security-conscious businesses.

Passwork wins Top Performer Fall 2026 on SourceForge
For the third consecutive quarter, Passwork has earned SourceForge's Top Performer badge — this time for Fall 2026. Here's what verified reviewers are saying, and the numbers behind the award.
NIS2 access management: What five experts would fix first
From policy to practice: who had access to what, with whose approval, for how long, and can you prove it? Five cybersecurity leaders on the access controls that are hardest to operationalize, and the evidence organizations need to demonstrate that they work.
Supply chain security guide: Vendor risks, regulations, and access control in 2026
48% of breaches now involve a third party. This guide covers the attack patterns behind SolarWinds, MOVEit, and XZ Utils — and the access controls, credential management practices, and regulatory requirements that actually stop them.