Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: 2 of 6 dimensions proven

0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.

by KL Bits GmbH · padloc.app

Report an error on this page Is this your product? →

Link to this page

Padloc: AI-assisted analysis on whats-best.ai Padloc: AI-assisted analysis on whats-best.ai (dark)

Add ?theme=dark to the image address for dark backgrounds. The badge shows the category and the month of the latest evaluation, and EU-Made where that is the product’s provenance. It never shows a score.

Padloc at a glance

Vendor
KL Bits GmbH
Headquarters
Not stated on the vendor’s pages as of 17 Nov 2026
Data hosting
Not stated on the vendor’s pages as of 17 Nov 2026
Free plan
Not stated on the vendor’s pages as of 17 Nov 2026
Panel verdict
The AI panel rates Padloc 2/5, the mean of 6 judges. Padloc is an open-source password manager licensed under the AGPL, whose captured pages name a German entity, MaKleSoft UG in Ansbach and Munich, though the vendor listing names KL Bits GmbH. how scores are made
As of
Vendor pages captured 17 Nov 2026; evaluated by the panel 18 Nov 2026. all sources

Padloc alternatives, European ones first →

Read this page as one judge. Each weighs the same scores by what they care about.

The DevOps Engineer

Weighted verdict

Would rather run the vault in the company's own data centre than trust another SaaS with root credentials. Wants a documented self-hosted deployment with backup and high availability, open-source code to read, a CLI and API for pipelines, and an export that loses nothing.

Same scores as the panel view — this lens weights them the way this judge cares.

Scored by The DevOps Engineer

Panel median The DevOps Engineer This judge’s scores over the panel median. Each label opens its reasoning below.
Scores per criterion, in stars out of 5
Criterion Panel median The DevOps Engineer
Encryption model & independent audits 3 of 5 3 of 5
Sharing, roles & recovery 2 of 5 2 of 5
SSO, directory sync & provisioning 2 of 5 2 of 5
Audit logs, policies & reporting 1 of 5 1 of 5
Hosting choice, offline access & export 3 of 5 3 of 5
European sovereignty 2 of 5 2 of 5
Pricing transparency 0.5 of 5 0.5 of 5

Encryption model & independent audits

How this is scored

What the vendor can prove about its security design: end-to-end encryption with named algorithms and key derivation, which fields are encrypted on the device and which are not, independent audits and penetration tests with published results, a bug bounty, and incident history disclosed.

0 — Vault contents are readable by the vendor by its own description: server-side encryption with keys the vendor holds, or no encryption of stored credentials.

3 — Client-side or end-to-end encryption described with the algorithms named; key derivation, audits and the scope of what is encrypted are basic or not described.

5 — A published security whitepaper or security page naming algorithms, key derivation and the client-side encryption model, and an independent audit, penetration test or certification (ISO 27001, SOC 2) named.

8 — A stated list of which fields are and are not encrypted (including URLs and metadata), recurring independent penetration tests or code audits with dates and reports or summaries published, a public bug bounty or vulnerability disclosure policy, past security incidents documented with their impact, and open-source clients or cryptography that can be reviewed.

10 — The design is verifiable end to end: full source or cryptographic design public, every field encrypted client-side including metadata, audits by named firms repeated yearly with full reports, a threat model that states what a compromise of the vendor's servers would expose, and incident post-mortems published.

Report an error

The DevOps Engineer

The security documentation names every algorithm — AES-GCM at 256 bits, PBKDF2 with SHA-256 and a 128-bit salt, RSA-OAEP and RSA-PSS — describes end-to-end encryption performed offline on the device with keys derived from the master password, and backs it with an independent Cure53 penetration test from April 2016 whose full report is downloadable and AGPL-licensed source I can review myself. That single audit is ten years old by the capture date, and we found no public information on which fields stay unencrypted, a bug bounty, recurring audits or incident history, so I stop just above the whitepaper-plus-audit level. 6 5 4 3

Report an error

Sharing, roles & recovery

How this is scored

How credentials are shared and governed across a company: shared vaults or collections, role-based permissions, view-only and time-limited access, admin account recovery, emergency access, and what happens to shared items when an employee leaves.

0 — A personal password manager by the vendor's own description: no sharing between users is offered.

3 — Shared folders or vaults between users of one account; permission levels, admin recovery and offboarding are basic or not described.

5 — Shared vaults or collections with permission levels (for example read, edit, manage), groups and admin roles, and an admin account recovery or offboarding that keeps a leaver's shared items with the company.

8 — Recovery and offboarding documented with their key model, granular permissions down to hiding the password while allowing autofill, time-limited and one-time sharing with external parties, emergency access with a waiting period, delegated administration per team or location, and approval workflows for sensitive items.

10 — Access is governed and provable: least-privilege defaults, recovery and emergency access designed so the vendor never holds a key and stated so, periodic access reviews supported in the product, and every grant, change and revocation attributable to a person.

Report an error

The DevOps Engineer

Organizations have Owner, Admin and Member roles, each user a private vault, shared vaults assignable directly or via groups, and a genuinely documented key model where the vault's shared key is wrapped with each accessor's RSA public key and rotated when accessors change. We found no public information on per-vault permission levels, admin recovery of a locked-out member, emergency access, or offboarding that keeps a leaver's shared items with the company, which keeps this below the full business-sharing level. 6 7 13

Report an error

SSO, directory sync & provisioning

How this is scored

How the vault fits into the company's identity stack: SSO with Entra ID, Okta or Google, and the key model behind an SSO unlock; SCIM or directory sync for joiners and leavers; MFA options including hardware keys; and passkey support for users and the vault itself.

0 — A consumer product by the vendor's own description, with no business administration, SSO or directory connection offered.

3 — Users invited by email or CSV with two-factor authentication; SSO, directory sync and hardware keys are basic or not described.

5 — SSO with named identity providers (Entra ID, Okta, Google), SCIM or directory sync for provisioning and deprovisioning, and MFA including FIDO2 or hardware keys.

8 — The SSO unlock documented with how the vault key is derived or released and designed so the vendor cannot derive it, group sync driving vault permissions, automated suspension on deprovisioning, conditional access or device policies, and passkeys stored and used across platforms.

10 — Identity is integrated without trust shortcuts: the SSO key model published and independently reviewed, deprovisioning that revokes vault access and shared items immediately with a log entry, passwordless vault unlock with passkeys, and support for the customer's own key-management or trusted-device approval.

Report an error

The DevOps Engineer

Directory synchronization genuinely exists in the code, with a module handling user and group created, updated and deleted events — the joiner and leaver plumbing I care about — and MFA methods are managed in the security settings. We found no public information on single sign-on with any named identity provider, SCIM, hardware security keys or passkeys, so the identity stack stops at directory sync and MFA. 8 9 13

Report an error

Audit logs, policies & reporting

How this is scored

What an administrator and an auditor can see and enforce: event logs of access and changes, password health and breach reports, enforceable policies (master password, MFA, sharing, export), SIEM integration, and reports an ISO 27001 or NIS2 audit can use.

0 — No administration by the vendor's own description: a personal tool with no admin console, logs or policies.

3 — An admin console with an activity list and a password health or strength report; exportable logs and enforceable policies are basic or not described.

5 — Event logs covering logins, item access, sharing and admin changes, enforceable policies for master password and MFA, and password health and breach-monitoring reports.

8 — Logs exportable or available through an API with native SIEM integration to named targets (Splunk, Microsoft Sentinel, Elastic or syslog), policies for sharing, export and browser-extension behaviour, log retention stated, and compliance reports aligned to ISO 27001, NIS2 or BSI IT-Grundschutz.

10 — Auditability is complete: every view, copy, autofill and permission change logged with user and device, logs tamper-evident and retained for a configurable period, alerting on anomalous access, and an auditor role that can read logs without access to secrets.

Report an error

The DevOps Engineer

All the captures show on this front is a developer logging module in the core library with a generic event class — nothing an administrator or external auditor could work with. We found no public information on an admin console, event logs of access and changes, password health or breach reports, enforceable policies, SIEM integration or log retention. 10 11

Report an error

Hosting choice, offline access & export

How this is scored

Where and how the vault runs and how the data leaves it: cloud region choice, a self-hosted or on-premises option, offline access during a vendor outage, client coverage across operating systems and browsers, and a complete, documented export and import path.

0 — Vault data cannot leave the product: the vendor states that no export is offered.

3 — Apps for common platforms and browsers and an export of vault items (for example CSV); hosting region, offline access and export completeness are basic or not described.

5 — Clients for Windows, macOS, iOS, Android and the major browsers, offline access to the vault, an EU region or self-hosted option, and export and import of vault data including from named competitors.

8 — Both EU cloud and self-hosted or on-premises deployment documented, Linux clients, a status page with incident history, an encrypted full-fidelity export covering all item types including attachments, and vault access continuing during an outage of the vendor's service.

10 — The customer can run and leave the vault on their own terms: self-hosting with documented high availability and backup, an open or documented export format that preserves structure, permissions and history, and a stated procedure for continued access if the vendor ends the service.

Report an error

The DevOps Engineer

This is where the product earns my trust: self-hosting the server and apps is documented with up-to-date Docker guides, the AGPL licence and open repository let me read and run my own infrastructure, clients cover web, desktop, iOS, Android and a browser extension, and export offers an encrypted, password-protected container bundling all vaults as a zip alongside CSV import. For my own data centre I still miss documented high availability and backup for the self-hosted deployment, and we found no public information on an EU cloud option, a status page, or vault access continuing during a vendor outage. 12 4 13

Report an error

European sovereignty

How this is scored

Who the contracting entity and the parent company are, where vault data and metadata are hosted, and who the subprocessors are. Independently sourced by the sovereignty pipeline; end-to-end encryption narrows what a foreign authority could compel, but metadata, logs and the update channel for the client software remain in the vendor's hands, so the chain still counts.

0 — Proven non-EU on every dimension the evidence covers: non-EU vendor and contracting entity and non-EU hosting, with no EU or self-hosted option stated.

3 — One European element proven: an EU data region, an EU contracting entity or EU representative, a self-hosted option, or a published DPA, with the rest of the chain unstated.

5 — EU hosting as standard or selectable, or a self-hosted option, and an EU contracting entity or EU representative, with a DPA offered; the parent company or parts of the chain (support, analytics, email, client distribution) are unstated or non-EU.

8 — EU hosting on named infrastructure, EU contracting entity, subprocessor list published with locations, a DPA covering vault metadata and logs, and a self-hosted option that removes the vendor from the data path.

10 — Sovereign end to end and evidenced: European ownership, entity, hosting and every subprocessor, certifications published (ISO 27001, BSI C5 or equivalent), and source code or builds verifiable so the client update channel is not a blind trust in the vendor.

Report an error

The DevOps Engineer

The captured material gives different names for the vendor entity, but the privacy page and terms show a German company (MaKleSoft UG, addresses in Ansbach and Munich), German governing law with Munich courts, GDPR commitments, and Stripe named for payment processing. Hosting location, a data processing agreement and further subprocessors are unknown to me, though the self-hosting option with copyleft source lets me remove the vendor from the data path entirely — which is the part I would use. 3 2 5 12

Report an error

Pricing transparency

How this is scored

Whether a buyer can compute the real annual cost from public pages alone: price per user and tier, which features (SSO, SCIM, SIEM, self-hosting) sit in which tier, minimum seats, add-ons, and the minimum term.

0 — No public prices at all; every tier is a sales conversation.

3 — A public "from" price or one priced tier, per user or flat.

5 — Per-user prices public for the business tiers with the billing period stated and the main features per tier listed.

8 — Every tier priced publicly with its feature set and seat minimum, add-on prices listed, self-hosted licensing stated, minimum term and VAT treatment given.

10 — Complete price computability: annual invoice derivable for a given number of users, with every add-on, self-hosting licence, support level and renewal condition published.

Report an error

The DevOps Engineer

We found no public prices on any captured page — no per-user figures, tiers, seat minimums or billing terms — and the commercial licence for the open-source code is acquired by contacting sales. Nothing here lets me budget a deployment from published pages alone. 4 2

Report an error

European sovereignty — proven facts

2 of 6 dimensions proven

Built only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.

Hosting location Not determined — uncited Report an error
Hosting options Self-hostable 1/1 pts 12 Report an error
Open source Open source (copyleft) unverified
Why unverified?

The repository also offers a commercial license as an alternative, but the AGPL is stated explicitly as the software's licence.

1/1 pts 4 Report an error
Data processing agreement Not determined — uncited Report an error
Transfer impact assessment Not determined — uncited Report an error

Questions about Padloc

Is Padloc European?

Not determined: the vendor’s pages as captured do not say where Padloc is based.

Where does Padloc store data?

Not stated on the vendor’s pages as of 17 Nov 2026.

Does Padloc have a free plan?

Not stated on the vendor’s pages as of 17 Nov 2026.

What are the best alternatives to Padloc?

As of 18 Nov 2026, the panel rates Passbolt (3.5/5), Password Depot (3.5/5) and 1Password (3.5/5) highest among the other 30 Password Management products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is Passbolt (EU-Made, Luxembourg). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: Padloc alternatives.

Where this could be wrong

What we left out

A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.

Sources (13)

The pages every claim on this page was read from — each one checked, dated, and kept verifiable.

  1. 1 Vendor page padloc.app Checked 17 Nov 2026 Details →
  2. 2 Terms of service — found from the homepage padloc.app Checked 17 Nov 2026 Details →
  3. 3 Privacy policy — found from the homepage padloc.app Checked 17 Nov 2026 Details →
  4. 4 Code repository (open-source licence) — found from the homepage github.com Checked 17 Nov 2026 Details →
  5. 5 Encryption model & independent audits — found from sitemap padloc.app Checked 17 Nov 2026 Details →
  6. 6 Encryption model & independent audits — found from sitemap docs.padloc.app Checked 17 Nov 2026 Details →
  7. 7 Sharing, roles & recovery — found from sitemap docs.padloc.app Checked 17 Nov 2026 Details →
  8. 8 SSO, directory sync & provisioning — found from sitemap docs.padloc.app Checked 17 Nov 2026 Details →
  9. 9 SSO, directory sync & provisioning — found from sitemap docs.padloc.app Checked 17 Nov 2026 Details →
  10. 10 Audit logs, policies & reporting — found from sitemap docs.padloc.app Checked 17 Nov 2026 Details →
  11. 11 Audit logs, policies & reporting — found from sitemap docs.padloc.app Checked 17 Nov 2026 Details →
  12. 12 Hosting choice, offline access & export — found from sitemap docs.padloc.app Checked 17 Nov 2026 Details →
  13. 13 Hosting choice, offline access & export — found from sitemap padloc.app Checked 17 Nov 2026 Details →