Softwr

Cybersecurity · head to head

Milestone XProtect vs Sigstore

Milestone XProtect logo

Milestone XProtect

Cybersecurity

Open platform video management software with perpetual per-device licences

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: Milestone XProtect care Plus is presented as optional but is not in practice: without it, perpetual licences stop receiving version upgrades and eventually you cannot add a current camera because your frozen version does not support it.; 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: Milestone XProtect covers Open device support, Sigstore covers Fulcio.
  • Prices and features above were last checked on 1 September 2026.

Where they differ

Only the attributes on which Milestone XProtect and Sigstore actually diverge.

Attributes where Milestone XProtect and Sigstore differ
AttributeMilestone XProtectSigstore
Pricing modelOne-time purchase per device licence, plus annual Care PlusOpen source, public instance free to use
PlatformsWindows, Web, iOS, AndroidWeb, 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 Milestone XProtect

  • Open device support
  • Perpetual device licences
  • Federated architecture
  • Failover recording
  • Evidence export
  • Smart Map
  • Integration platform
  • Video summarisation

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.

Milestone XProtect

  • A city or transport operator running tens of thousands of cameras across federated sitesnot Sigstore
  • An enterprise with mixed legacy camera brands that refuses to standardise on one manufacturernot Sigstore
  • A critical infrastructure site needing failover recording servers and tamper-evident evidence exportnot Sigstore
  • An integrator building a bespoke security application on top of an open VMS platformnot Sigstore

Sigstore

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

Where each one falls short

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

Milestone XProtect

  • Care Plus is presented as optional but is not in practice: without it, perpetual licences stop receiving version upgrades and eventually you cannot add a current camera because your frozen version does not support it.
  • Per-device licensing means multi-sensor and multi-imager cameras consume several licences each, so a headline camera count badly understates the true licence cost of a modern design.
  • It is Windows only for servers and needs a properly designed server and storage architecture, so the software price is a fraction of a project that also needs recording servers, storage and an integrator.
  • Complexity requires trained staff or a certified integrator; organisations that install it without either end up running a large deployment on default settings and never using the features they paid for.
  • Milestone retired Kite from its portfolio in favour of Arcules from January 2025, which stranded buyers who had standardised on Kite and is a reminder that the cloud side of the portfolio has changed direction more than once.

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

Milestone XProtect

Free
  • XProtect Essential+Free
    • Free for up to 8 cameras
    • No recording time limit
    • No vendor support included
  • XProtect Express+$109/one-time
    • Perpetual device licence, distributor list price
    • Single site, single server
    • Care Plus purchased separately per device per year
  • XProtect Professional+$177/one-time
    • Perpetual device licence, distributor list price
    • Multiple recording servers
    • Edge storage retrieval
  • XProtect Expert$282/one-time
    • Perpetual device licence, distributor list price
    • Failover recording servers
    • Advanced video wall and evidence handling

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 Milestone XProtect if

  • You need open device support.
  • You want to start without paying.
  • You work on Windows, Web, iOS, Android.
  • You also want perpetual device licences.

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 Milestone XProtect or Sigstore better?
Neither clearly leads. Milestone XProtect 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, Milestone XProtect or Sigstore?
Milestone XProtect starts at Free and Sigstore at Free.
Does Milestone XProtect or Sigstore run on more platforms?
Milestone XProtect runs on Windows, Web, iOS, Android. Sigstore runs on Web, Linux, macOS, Windows, Self-hosted.
Can I use Milestone XProtect for free?
Both have a free tier, so you can try either at no cost before committing.
What is Milestone XProtect best used for?
Milestone XProtect is most often used for a city or transport operator running tens of thousands of cameras across federated sites, an enterprise with mixed legacy camera brands that refuses to standardise on one manufacturer, a critical infrastructure site needing failover recording servers and tamper-evident evidence export, an integrator building a bespoke security application on top of an open vms platform. Of those, a city or transport operator running tens of thousands of cameras across federated sites and an enterprise with mixed legacy camera brands that refuses to standardise on one manufacturer are not what Sigstore is typically brought in for.
What can Milestone XProtect do that Sigstore cannot?
Milestone XProtect covers Open device support, Perpetual device licences, Federated architecture, Failover recording. Sigstore covers Fulcio, Rekor, Keyless signing, Multi-language clients.

Answered from the vendors’ own pages

Milestone XProtect: Is XProtect really free for small sites?

Essential+ is free for up to eight cameras with no recording time limit, but it comes with no vendor support and no multi-server capability.

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.

Milestone XProtect: Are licences perpetual or annual?

Device licences are perpetual. The annual cost is Care Plus, the support and software update contract, which you need to stay on current versions.

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.

Milestone XProtect: What happens if I do not renew Care Plus?

The system keeps recording, but you stop getting version upgrades, and over a few years that blocks you from adding newer cameras.

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.

Milestone XProtect: Who owns Milestone?

Canon. The portfolio also includes BriefCam analytics and Arcules cloud video, with Arcules replacing Milestone Kite from January 2025.

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