Softwr

Cybersecurity · head to head

Passbolt vs Sigstore

Passbolt logo

Passbolt

Cybersecurity

Open-source password manager for teams with self-hosted or cloud deployment

From
Free
Rated
-
Sigstore logo

Sigstore

Cybersecurity

Free public signing and transparency infrastructure for open source artifacts

From
Free
Rated
-

The short version

  • Each has a real cost: Passbolt pro Edition requires a minimum of 10 users, making it costlier for very small teams.; Sigstore the security model depends on somebody watching the log. The documentation states that compromise of an identity provider or of Fulcio itself is detectable only if third parties monitor the transparency log, the monitoring tool is a community-tier rather than core project, and almost no consumer runs one.
  • They diverge on capability: Passbolt covers Password sharing and folders, Sigstore covers Fulcio.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which Passbolt and Sigstore actually diverge.

Attributes where Passbolt and Sigstore differ
AttributePassboltSigstore
Pricing modelopen-sourceOpen source, public instance free to use
Platformsweb, windows, mac, linux, apiWeb, Linux, macOS, Windows, Self-hosted

Identical on both: starting price (Free), free tier (Yes), user rating (Not yet rated), category (Cybersecurity).

What each one covers

Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.

Only in Passbolt

  • Password sharing and folders
  • Groups and role-based access
  • Browser extensions and CLI
  • Open API
  • LDAP provisioning and SSO
  • Activity audit log

Only in Sigstore

  • Fulcio
  • Rekor
  • Keyless signing
  • Multi-language clients
  • Timestamp authority
  • Neutral governance

What people use each for

The jobs each tool is most often brought in to do.

Passbolt

  • Self-hosting a team password manager for data sovereigntynot Sigstore
  • Provisioning vault access from an existing LDAP/AD directorynot Sigstore
  • Sharing credentials across engineering or IT teams via folders and groupsnot Sigstore
  • Automating credential retrieval through the CLI or open APInot Sigstore

Sigstore

  • Open source projects signing releases without running a certificate authoritynot Passbolt
  • Organisations meeting a signed-artifact requirement without buying a signing productnot Passbolt
  • Publishing provenance that a consumer can verify independently of younot Passbolt
  • Self-hosting the same components where a public log is unacceptablenot Passbolt

Where each one falls short

Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

Passbolt

  • Pro Edition requires a minimum of 10 users, making it costlier for very small teams.
  • Community Edition lacks SSO and LDAP provisioning, which many organizations need for onboarding at scale.
  • Self-hosting the Community Edition requires infrastructure and maintenance effort compared to fully managed competitors.
  • Enterprise-tier support and HA consulting require custom, quote-based pricing rather than transparent rates.

Sigstore

  • The security model depends on somebody watching the log. The documentation states that compromise of an identity provider or of Fulcio itself is detectable only if third parties monitor the transparency log, the monitoring tool is a community-tier rather than core project, and almost no consumer runs one.
  • It is a 99.5 percent objective with no service level agreement, which permits several hours of downtime a month and offers no remedy. A pipeline that signs on every build has taken a hard dependency on a free service with no contract behind it.
  • Log scale is a live engineering problem rather than a theoretical one. The active shard holds billions of entries, the log has already been sharded twice, and sharding version 1 requires stopping traffic, which is why a replacement was built.
  • Ten-minute certificates make trust depend on log availability. Verifying an older signature relies on the log entry proving it was made inside that window, so a lost or unreachable entry can render a valid artifact unverifiable.
  • Migration debt is substantial and ongoing. Version 2 of the log is generally available but not the public default, the signing client has an announced breaking release ahead, some official clients lag the new log format, and a post-quantum migration is named as the next break after that.

Pricing, plan by plan

Passbolt

Free
  • Community EditionFree
    • Unlimited users
    • Password sharing and folders
    • Role-based access control
  • Pro Edition$4.9/month
    • Minimum 10 users, billed annually
    • LDAP/AD provisioning
    • Single sign-on
  • Enterprise Edition$undefined/month
    • High availability and disaster recovery consulting
    • White-glove migration
    • Custom feature development

Sigstore

Free
  • Public good instanceFree
    • Free to everyone with no contract
    • 99.5 percent availability objective, not an agreement
    • 100KB cap per attestation upload
  • Self-hostedFree
    • Apache-2.0
    • Run your own Fulcio and Rekor
    • Rekor v2 available for self-hosters

Which should you pick?

Choose Passbolt if

  • You need password sharing and folders.
  • You want to start without paying.
  • You work on web, windows, mac, linux, api.
  • You also want groups and role-based access.

Choose Sigstore if

  • You need fulcio.
  • You want to start without paying.
  • You work on Web, Linux, macOS, Windows, Self-hosted.
  • You also want rekor.

Questions people ask

Is Passbolt or Sigstore better?
Neither clearly leads. Passbolt starts at Free and Sigstore at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Passbolt or Sigstore?
Passbolt starts at Free and Sigstore at Free.
Does Passbolt or Sigstore run on more platforms?
Passbolt runs on web, windows, mac, linux, api. Sigstore runs on Web, Linux, macOS, Windows, Self-hosted.
Can I use Passbolt for free?
Both have a free tier, so you can try either at no cost before committing.
What is Passbolt best used for?
Passbolt is most often used for self-hosting a team password manager for data sovereignty, provisioning vault access from an existing ldap/ad directory, sharing credentials across engineering or it teams via folders and groups, automating credential retrieval through the cli or open api. Of those, self-hosting a team password manager for data sovereignty and provisioning vault access from an existing ldap/ad directory are not what Sigstore is typically brought in for.
What can Passbolt do that Sigstore cannot?
Passbolt covers Password sharing and folders, Groups and role-based access, Browser extensions and CLI, Open API. Sigstore covers Fulcio, Rekor, Keyless signing, Multi-language clients.

Answered from the vendors’ own pages

Passbolt: Is Passbolt free to use?

Yes. The Community Edition is free forever with unlimited users, including password sharing, folders, groups, role-based access, browser extensions, a CLI, and an open API.

Source
Sigstore: Is the public instance really free?

Yes, with no contract and no paid tier. That is also the weakness: a 99.5 percent objective with no agreement, no remedy and support through Slack.

Passbolt: What does the Pro Edition cost and add?

Pro Edition costs $4.90 per user per month billed annually, with a 10-user minimum, and adds LDAP/AD provisioning, single sign-on, account recovery escrow, activity audit logs, and next-business-day support.

Source
Sigstore: Has the public log moved to Rekor v2?

No. Version 2 reached general availability in October 2025 and self-hosters can use it, but the public instance still defaults to version 1 and the project has said it will for the foreseeable future.

Passbolt: What license is Passbolt distributed under?

All Passbolt editions, including Pro and Enterprise, are distributed under the AGPL v3 open-source license.

Source
Sigstore: Does Sigstore make my dependencies safe?

No, and this is a category error worth avoiding. It tells you who published something. It has no knowledge of what the artifact contains or whether it is vulnerable.

Sigstore: What are the rate limits?

Not published. Only the 100KB cap per attestation upload is documented, so do not design a high-volume pipeline around assumed throughput.

Sigstore: Should we self-host it?

If a public record of every signature is unacceptable, or if a free service with no agreement cannot sit in your build path, then yes. Otherwise the public instance is what most projects use.

Share

Related pages

Other head to heads