Softwr

Cybersecurity · head to head

Sigstore vs VUEWorks

Sigstore logo

Sigstore

Cybersecurity

Free public signing and transparency infrastructure for open source artifacts

From
Free
Free plan
Yes
Full reviewWebsite
VUEWorks logo

VUEWorks

Government

GIS-centred enterprise asset management for public agencies, built around Esri ArcGIS

From
On request
Free plan
No
Full reviewWebsite

The short version

  • Only Sigstore has a free tier, so it costs nothing to try first.
  • Each has a real cost: 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.; VUEWorks the product assumes a maintained enterprise ArcGIS geodatabase; agencies without one face a spatial data cleanup project before VUEWorks does anything useful, and that project is usually quoted by the same consultancy selling the software.
  • They diverge on capability: Sigstore covers Fulcio, VUEWorks covers Native Esri integration.
  • Prices and features above were last checked on 1 September 2026.

Where they differ

Only the attributes on which Sigstore and VUEWorks actually diverge.

Attributes where Sigstore and VUEWorks differ
AttributeSigstoreVUEWorks
Starting priceFreeOn request
Pricing modelOpen source, public instance free to usequote
Free tierYesNo
PlatformsWeb, Linux, macOS, Windows, Self-hostedWeb, iOS, Android
CategoryCybersecurityGovernment

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

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

Only in VUEWorks

  • Native Esri integration
  • Work orders and requests
  • Inspections
  • Condition and risk
  • Capital planning
  • Pavement management
  • Mobile field access
  • Dashboards

What people use each for

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

Sigstore

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

VUEWorks

  • A county public works department that already runs Esri and wants work orders raised directly against map featuresnot Sigstore
  • A stormwater utility recording CCTV sewer inspection results against pipe segments for regulatory reportingnot Sigstore
  • A transport agency modelling pavement treatment strategies to defend a road resurfacing budgetnot Sigstore
  • A city consolidating sign, signal and streetlight inventories that currently live in separate spreadsheetsnot Sigstore

Where each one falls short

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

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.

VUEWorks

  • The product assumes a maintained enterprise ArcGIS geodatabase; agencies without one face a spatial data cleanup project before VUEWorks does anything useful, and that project is usually quoted by the same consultancy selling the software.
  • No pricing is published and deals are typically bundled with consulting services, which makes it hard to separate the software cost from the data work when comparing bids.
  • The interface is functional rather than modern, and field crews accustomed to consumer mobile apps often resist it, which undermines the data quality the capital planning depends on.
  • The Esri dependency is also an Esri cost: agencies need current ArcGIS Enterprise or ArcGIS Online licensing, and that sits outside the VUEWorks quote entirely.
  • It is a small vendor with a limited partner network and a mainly North American footprint, so support and implementation capacity outside that region is thin.

Pricing, plan by plan

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

VUEWorks

On request
  • VUEWorks Enterprise$undefined/year
    • Quoted per agency by user count and modules
    • Hosted or on-premise deployment options
    • GIS integration, data migration and configuration quoted separately

Which should you pick?

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

Choose VUEWorks if

  • You need native esri integration.
  • You work on Web, iOS, Android.
  • You also want work orders and requests.
VUEWorks review

Questions people ask

Is Sigstore or VUEWorks better?
Neither clearly leads. Sigstore starts at Free and VUEWorks at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Sigstore or VUEWorks?
Sigstore has a free tier; the other does not. Paid plans start at Free for Sigstore and On request for VUEWorks.
Does Sigstore or VUEWorks run on more platforms?
Sigstore runs on Web, Linux, macOS, Windows, Self-hosted. VUEWorks runs on Web, iOS, Android.
Can I use Sigstore for free?
Yes. Sigstore has a free tier, so you can try it without paying. VUEWorks starts at On request.
What is Sigstore best used for?
Sigstore is most often used for open source projects signing releases without running a certificate authority, organisations meeting a signed-artifact requirement without buying a signing product, publishing provenance that a consumer can verify independently of you, self-hosting the same components where a public log is unacceptable. Of those, open source projects signing releases without running a certificate authority and organisations meeting a signed-artifact requirement without buying a signing product are not what VUEWorks is typically brought in for.
What can Sigstore do that VUEWorks cannot?
Sigstore covers Fulcio, Rekor, Keyless signing, Multi-language clients. VUEWorks covers Native Esri integration, Work orders and requests, Inspections, Condition and risk.

Answered from the vendors’ own pages

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.

VUEWorks: Do we need Esri ArcGIS?

Effectively yes. The asset register is the GIS, and the ArcGIS licensing sits outside the VUEWorks quote.

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.

VUEWorks: Is pricing published?

No. VUEWorks is quoted per agency by users and modules, often bundled with data collection services.

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.

VUEWorks: Can it replace Cityworks?

It occupies the same GIS-centric municipal asset management space, so yes in principle, but migration means remapping workflows and history.

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.

VUEWorks: Is there a cloud option?

Yes, VUEWorks is offered hosted as well as on-premise.

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 Sigstore

More on VUEWorks

Keep looking

Other head to heads