Softwr

APIs · head to head

Formance vs Sigstore

Formance logo

Formance

APIs

Open source double-entry ledger and payment orchestration for money-moving software

From
Free
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

  • Each has a real cost: Formance formance holds no money and provides no regulatory cover, so it must be paired with a payments provider or bank, and buyers occasionally mistake a ledger for a treasury system and discover the gap late.; 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: Formance covers Double-entry ledger, Sigstore covers Fulcio.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which Formance and Sigstore actually diverge.

Attributes where Formance and Sigstore differ
AttributeFormanceSigstore
Pricing modelOpen source, no licence feeOpen source, public instance free to use
PlatformsLinux, Docker, Kubernetes, Web, APIWeb, Linux, macOS, Windows, Self-hosted
CategoryAPIsCybersecurity

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

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 Formance

  • Double-entry ledger
  • Numscript transaction DSL
  • Multi-currency
  • Payments connectivity
  • Reconciliation
  • Self-hosted deployment
  • Cloud offering
  • API and SDKs

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.

Formance

  • A marketplace splitting a single customer payment between seller, platform fee and tax that needs the split to be atomic and auditablenot Sigstore
  • A fintech whose homegrown balances table produced numbers finance could not reconcile and now needs proper double-entry before an auditnot Sigstore
  • A payments team that wants one normalised model across several PSPs so reconciliation is not written separately for eachnot Sigstore
  • A company that wants its ledger under a licence it can keep running even if the vendor disappearsnot Sigstore

Sigstore

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

Where each one falls short

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

Formance

  • Formance holds no money and provides no regulatory cover, so it must be paired with a payments provider or bank, and buyers occasionally mistake a ledger for a treasury system and discover the gap late.
  • Numscript is a domain-specific language your team must learn, and while it makes complex splits expressible it also means transaction logic sits outside the languages your engineers already debug well.
  • Self-hosting a ledger that must never lose or duplicate a transaction is a serious operational commitment covering backups, upgrades and Postgres tuning, which is real cost the zero licence fee hides.
  • Enterprise pricing is not published, so the difference between the free path and the supported path cannot be evaluated without a sales conversation.
  • The company is much smaller than the incumbent alternatives, and while the MIT licence protects the code it does not protect the roadmap, so features on the hosted side may arrive slowly or change direction.

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

Formance

Free
  • Open SourceFree
    • MIT licensed core ledger
    • Numscript transaction DSL
    • Multi-currency tracking
  • Enterprise$undefined/year
    • Managed or private deployment
    • Payments connectivity and reconciliation
    • Support with response commitments

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

  • You need double-entry ledger.
  • You want to start without paying.
  • You work on Linux, Docker, Kubernetes, Web, API.
  • You also want numscript transaction dsl.
Formance 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 Formance or Sigstore better?
Neither clearly leads. Formance 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, Formance or Sigstore?
Formance starts at Free and Sigstore at Free.
Does Formance or Sigstore run on more platforms?
Formance runs on Linux, Docker, Kubernetes, Web, API. Sigstore runs on Web, Linux, macOS, Windows, Self-hosted.
Can I use Formance for free?
Both have a free tier, so you can try either at no cost before committing.
What is Formance best used for?
Formance is most often used for a marketplace splitting a single customer payment between seller, platform fee and tax that needs the split to be atomic and auditable, a fintech whose homegrown balances table produced numbers finance could not reconcile and now needs proper double-entry before an audit, a payments team that wants one normalised model across several psps so reconciliation is not written separately for each, a company that wants its ledger under a licence it can keep running even if the vendor disappears. Of those, a marketplace splitting a single customer payment between seller, platform fee and tax that needs the split to be atomic and auditable and a fintech whose homegrown balances table produced numbers finance could not reconcile and now needs proper double-entry before an audit are not what Sigstore is typically brought in for.
What can Formance do that Sigstore cannot?
Formance covers Double-entry ledger, Numscript transaction DSL, Multi-currency, Payments connectivity. Sigstore covers Fulcio, Rekor, Keyless signing, Multi-language clients.

Answered from the vendors’ own pages

Formance: Is Formance really open source?

Yes. The core ledger is MIT licensed with full source access and no deployment restrictions.

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.

Formance: Does Formance move money?

No. It records and orchestrates movements; the actual payments happen at a PSP or bank you connect.

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.

Formance: What does the enterprise version cost?

Not published. It is an annual subscription quoted per customer.

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.

Formance: Do I have to use Numscript?

Yes for anything beyond the simplest transfers. It is how multi-party transactions are expressed atomically.

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 Formance

More on Sigstore

Keep looking

Other head to heads