Softwr

Cybersecurity · head to head

IDnow vs Sigstore

IDnow logo

IDnow

Cybersecurity

Identity verification and qualified electronic signature for regulated European markets

From
On request
Rated
-
Full reviewWebsite
Sigstore logo

Sigstore

Cybersecurity

Free public signing and transparency infrastructure for open source artifacts

From
Free
Rated
-
Full reviewWebsite

The short version

  • Only Sigstore has a free tier, so it costs nothing to try first.
  • Each has a real cost: IDnow agent-led video identification costs several times an automated check and depends on agent availability, so peak-time queues push abandonment up at exactly the moment conversion matters.; 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: IDnow covers VideoIdent, Sigstore covers Fulcio.
  • Prices and features above were last checked on 1 September 2026.

Where they differ

Only the attributes on which IDnow and Sigstore actually diverge.

Attributes where IDnow and Sigstore differ
AttributeIDnowSigstore
Starting priceOn requestFree
Pricing modelquoteOpen source, public instance free to use
Free tierNoYes
PlatformsWeb, iOS, Android, APIWeb, Linux, macOS, Windows, Self-hosted

Identical on both: 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 IDnow

  • VideoIdent
  • AutoIdent
  • eSign
  • eID and NFC
  • Bank identification
  • EU data processing

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.

IDnow

  • A German bank opening regulated accounts where BaFin requires a recognised identification methodnot Sigstore
  • An insurer needing a qualified electronic signature that will survive challenge in a European courtnot Sigstore
  • A telecom operator meeting national SIM registration identity rules across several EU statesnot Sigstore
  • A lender wanting automated checks for low-risk applicants and video identification only for high-value casesnot Sigstore

Sigstore

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

Where each one falls short

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

IDnow

  • Agent-led video identification costs several times an automated check and depends on agent availability, so peak-time queues push abandonment up at exactly the moment conversion matters.
  • Pricing is quoted with an annual volume commitment, so the accreditation advantage comes with a floor you pay whether or not you use it.
  • The product is optimised for European regulatory regimes, so buyers verifying users in North America, Asia or Africa will find coverage and cost less competitive than global specialists.
  • Qualified electronic signature is a separate licence from identity verification, which surprises buyers who assumed the accredited identity check made the signature capability included.
  • Integration for the regulated flows is heavier than a simple SDK drop-in because the compliant journey, including consent and recording requirements, constrains the user experience you can build.

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

IDnow

On request
  • IDnow Platform$undefined/year
    • Per-identification pricing that differs sharply between automated and agent-led methods
    • Annual volume commitment typically required
    • Qualified electronic signature licensed separately

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 IDnow if

  • You need videoident.
  • You work on Web, iOS, Android, API.
  • You also want autoident.
IDnow review

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.
Sigstore review

Questions people ask

Is IDnow or Sigstore better?
Neither clearly leads. IDnow starts at On request and Sigstore at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, IDnow or Sigstore?
Sigstore has a free tier; the other does not. Paid plans start at On request for IDnow and Free for Sigstore.
Does IDnow or Sigstore run on more platforms?
IDnow runs on Web, iOS, Android, API. Sigstore runs on Web, Linux, macOS, Windows, Self-hosted.
Can I use Sigstore for free?
Yes. Sigstore has a free tier, so you can try it without paying. IDnow starts at On request.
What is IDnow best used for?
IDnow is most often used for a german bank opening regulated accounts where bafin requires a recognised identification method, an insurer needing a qualified electronic signature that will survive challenge in a european court, a telecom operator meeting national sim registration identity rules across several eu states, a lender wanting automated checks for low-risk applicants and video identification only for high-value cases. Of those, a german bank opening regulated accounts where bafin requires a recognised identification method and an insurer needing a qualified electronic signature that will survive challenge in a european court are not what Sigstore is typically brought in for.
What can IDnow do that Sigstore cannot?
IDnow covers VideoIdent, AutoIdent, eSign, eID and NFC. Sigstore covers Fulcio, Rekor, Keyless signing, Multi-language clients.

Answered from the vendors’ own pages

IDnow: Why choose it over a cheaper automated vendor?

Because in some European regimes the cheaper vendor is not legally permitted for the transaction. This is an eligibility question, not a quality one.

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.

IDnow: Is the electronic signature included?

No. Qualified electronic signature under eIDAS is licensed separately from identity verification.

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.

IDnow: Where is the data processed?

In European data centres, which is a requirement rather than a preference for many of its regulated customers.

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

More on IDnow

More on Sigstore

Keep looking

Other head to heads