Softwr

Networking · head to head

pfSense vs Sigstore

pfSense logo

pfSense

Networking

Open source firewall software with a free Community Edition and a separate commercial Plus edition sold by Netgate

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: pfSense pfSense CE and pfSense Plus are not simply the same software with a support contract layered on top; Plus is a separately developed edition with its own feature set, and moving between them is a migration, not a toggle; 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: pfSense covers Stateful firewall and NAT, Sigstore covers Fulcio.
  • Prices and features above were last checked on 1 September 2026.

Where they differ

Only the attributes on which pfSense and Sigstore actually diverge.

Attributes where pfSense and Sigstore differ
AttributepfSenseSigstore
Pricing modelOpen source Community Edition, free; commercial Plus edition sold separately by NetgateOpen source, public instance free to use
PlatformsLinuxWeb, Linux, macOS, Windows, Self-hosted
CategoryNetworkingCybersecurity

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 pfSense

  • Stateful firewall and NAT
  • VPN support
  • Traffic shaping and QoS
  • Package ecosystem
  • CE and Plus editions

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.

pfSense

  • A home user or small business wanting a free, fully-featured firewall on commodity hardware with no licence costnot Sigstore
  • A business wanting an integrated firewall appliance with vendor support, typically buying a Netgate appliance bundled with pfSense Plusnot Sigstore
  • A team wanting to evaluate advanced features like real-time threat intelligence before committing to Netgate hardware or a Plus migrationnot Sigstore
  • An organisation replacing an expensive commercial firewall with an open source alternative while retaining the option to add commercial support laternot Sigstore

Sigstore

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

Where each one falls short

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

pfSense

  • pfSense CE and pfSense Plus are not simply the same software with a support contract layered on top; Plus is a separately developed edition with its own feature set, and moving between them is a migration, not a toggle
  • Running Plus on non-Netgate hardware depends on Netgate's current migration terms, which have changed over time, so a buyer planning to use white-box hardware with Plus should verify current eligibility rather than assume it works as it did previously
  • CE has no official vendor support channel; a business relying on it for production firewalling without a support contract is self-supporting on community forums
  • Some newer features and threat intelligence integrations are Plus-only, so CE users do not get feature parity going forward even though both editions remain under active development
  • Netgate's own appliance pricing and the terms of the CE-to-Plus migration path are not always clearly presented in one place, requiring some digging to understand the real total cost of a Plus deployment on non-Netgate hardware
  • As with any self-managed firewall, security depends on the operator applying updates and correctly configuring rules; there is no managed security operations layer included even in Plus

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

pfSense

Free
  • pfSense CEFree
    • Full firewall and routing functionality
    • No vendor lock-in to hardware
    • Community support
  • pfSense Plus (via Netgate appliance)$undefined/one-time
    • Bundled with Netgate hardware appliances from around $189
    • Threat intelligence feeds
    • Certified support tiers

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

  • You need stateful firewall and nat.
  • You want to start without paying.
  • You work on Linux.
  • You also want vpn support.
pfSense 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 pfSense or Sigstore better?
Neither clearly leads. pfSense 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, pfSense or Sigstore?
pfSense starts at Free and Sigstore at Free.
Does pfSense or Sigstore run on more platforms?
pfSense runs on Linux. Sigstore runs on Web, Linux, macOS, Windows, Self-hosted.
Can I use pfSense for free?
Both have a free tier, so you can try either at no cost before committing.
What is pfSense best used for?
pfSense is most often used for a home user or small business wanting a free, fully-featured firewall on commodity hardware with no licence cost, a business wanting an integrated firewall appliance with vendor support, typically buying a netgate appliance bundled with pfsense plus, a team wanting to evaluate advanced features like real-time threat intelligence before committing to netgate hardware or a plus migration, an organisation replacing an expensive commercial firewall with an open source alternative while retaining the option to add commercial support later. Of those, a home user or small business wanting a free, fully-featured firewall on commodity hardware with no licence cost and a business wanting an integrated firewall appliance with vendor support, typically buying a netgate appliance bundled with pfsense plus are not what Sigstore is typically brought in for.
What can pfSense do that Sigstore cannot?
pfSense covers Stateful firewall and NAT, VPN support, Traffic shaping and QoS, Package ecosystem. Sigstore covers Fulcio, Rekor, Keyless signing, Multi-language clients.

Answered from the vendors’ own pages

pfSense: What is the difference between pfSense CE and pfSense Plus?

CE is the free, open source edition installable on any compatible hardware; Plus is a commercial edition from Netgate with additional features and support, typically bundled with Netgate appliances.

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.

pfSense: Can I run pfSense Plus on my own hardware?

It is possible through a migration from a CE installation via Netgate's official channel, but the terms and availability of that path have changed over time and should be confirmed directly with Netgate.

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.

pfSense: Is pfSense CE really free with no catch?

Yes, CE has no licence fee and no hardware lock-in, though it comes with community rather than vendor support.

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 pfSense

More on Sigstore

Keep looking

Other head to heads