Softwr

Cybersecurity · head to head

Cosign vs MyRec.com

Cosign logo

Cosign

Cybersecurity

Signs and verifies container images and artifacts, with or without managing keys

From
Free
Free plan
Yes
Full reviewWebsite
MyRec.com logo

MyRec.com

Government

Recreation management for small parks departments, priced on your annual revenue with no contract

From
On request
Free plan
No
Full reviewWebsite

The short version

  • Only Cosign has a free tier, so it costs nothing to try first.
  • Each has a real cost: Cosign keyless signing inherits every weakness of the identity provider behind it. Sigstore’s own threat model states that if an identity provider is compromised, Sigstore will issue certificates to those identities, so a compromised account produces perfectly valid signatures.; MyRec.com the annual fee scales with department revenue, so a successful department pays more for the same software as its programme income grows.
  • They diverge on capability: Cosign covers Keyless signing, MyRec.com covers Revenue-based annual fee.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which Cosign and MyRec.com actually diverge.

Attributes where Cosign and MyRec.com differ
AttributeCosignMyRec.com
Starting priceFreeOn request
Pricing modelOpen source, no licence feePer year by department annual revenue
Free tierYesNo
PlatformsmacOS, Linux, Windows, DockerWeb
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 Cosign

  • Keyless signing
  • Key and KMS signing
  • Registry-native storage
  • In-toto attestations
  • Offline verification
  • Trusted root and signing config

Only in MyRec.com

  • Revenue-based annual fee
  • Programme registration
  • Facility reservations
  • Point of sale
  • League scheduling
  • Everything included

What people use each for

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

Cosign

  • Signing container images in a build pipeline without managing long-lived private keysnot MyRec.com
  • Attaching a signed bill of materials to a release so consumers can verify its provenancenot MyRec.com
  • Meeting a customer or regulatory requirement for signed artifactsnot MyRec.com
  • Verifying third-party images before they enter an internal registrynot MyRec.com

MyRec.com

  • A town recreation department of one or two staff moving off paper registration forms and a shared spreadsheetnot Cosign
  • A department that wants to choose its own payment processor rather than accept the software vendor ratenot Cosign
  • Replacing a system that charges per module, where every new programme type triggered an upsellnot Cosign
  • A department needing field permits and league scheduling without buying a facilities management suitenot Cosign

Where each one falls short

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

Cosign

  • Keyless signing inherits every weakness of the identity provider behind it. Sigstore’s own threat model states that if an identity provider is compromised, Sigstore will issue certificates to those identities, so a compromised account produces perfectly valid signatures.
  • A signature proves who signed, never whether they should have. The documentation is explicit that Sigstore cannot determine authorisation, so every consumer must write and maintain their own identity and issuer policy or verification means nothing.
  • Nothing is enforced without an admission controller. Signing changes what you can prove, not what runs, and the official policy controller has a small maintainer base for a component sitting in a cluster admission path.
  • Upgrades break pipelines. Version 3 changed defaults, version 4 is announced as removing legacy functionality and roughly half the command line flags, and two official client libraries still lacked support for the new log format as of mid 2026.
  • Signatures do not expire. An artifact signed before a maintainer account was compromised and one signed after are indistinguishable unless somebody is actively monitoring the transparency log, and almost nobody is.

MyRec.com

  • The annual fee scales with department revenue, so a successful department pays more for the same software as its programme income grows.
  • It is built for small and mid-sized departments and lacks the permitting, aquatics and multi-facility depth a large city requires.
  • Credit card processing is explicitly excluded from the fee, so the total cost depends on a merchant agreement the department must source and negotiate itself.
  • Integration surface is thin, with no meaningful connection to municipal ERP or finance systems, meaning revenue reconciliation is a manual export.
  • The vendor is small, so there is limited third-party consulting capacity and a narrow bench for support during peak registration periods.

Pricing, plan by plan

Cosign

Free
  • CosignFree
    • Apache-2.0
    • Public Sigstore infrastructure free to use
    • No usage limits published

MyRec.com

On request
  • MyRec.com$undefined/year
    • Single annual fee calculated from department annual revenue
    • Third parties report entry around 2,850 to 3,445 USD per year
    • Site build, onboarding and training included

Which should you pick?

Choose Cosign if

  • You need keyless signing.
  • You want to start without paying.
  • You work on macOS, Linux, Windows, Docker.
  • You also want key and kms signing.
Cosign review

Choose MyRec.com if

  • You need revenue-based annual fee.
  • You also want programme registration.
MyRec.com review

Questions people ask

Is Cosign or MyRec.com better?
Neither clearly leads. Cosign starts at Free and MyRec.com at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Cosign or MyRec.com?
Cosign has a free tier; the other does not. Paid plans start at Free for Cosign and On request for MyRec.com.
Does Cosign or MyRec.com run on more platforms?
Cosign runs on macOS, Linux, Windows, Docker. MyRec.com runs on Web.
Can I use Cosign for free?
Yes. Cosign has a free tier, so you can try it without paying. MyRec.com starts at On request.
What is Cosign best used for?
Cosign is most often used for signing container images in a build pipeline without managing long-lived private keys, attaching a signed bill of materials to a release so consumers can verify its provenance, meeting a customer or regulatory requirement for signed artifacts, verifying third-party images before they enter an internal registry. Of those, signing container images in a build pipeline without managing long-lived private keys and attaching a signed bill of materials to a release so consumers can verify its provenance are not what MyRec.com is typically brought in for.
What can Cosign do that MyRec.com cannot?
Cosign covers Keyless signing, Key and KMS signing, Registry-native storage, In-toto attestations. MyRec.com covers Revenue-based annual fee, Programme registration, Facility reservations, Point of sale.

Answered from the vendors’ own pages

Cosign: Does Cosign tell me if an image is vulnerable?

No. It has no vulnerability knowledge whatsoever. It can carry an SBOM as a signed attestation but never reads it. Pair it with a scanner.

MyRec.com: How is MyRec priced?

A single annual fee calculated from your department annual revenue, using a calculator on the MyRec site. Third parties report entry around 2,850 to 3,445 USD a year.

Cosign: Is signing alone enough?

No. Verification is a command somebody runs. Without an admission controller enforcing it, an unsigned image still runs.

MyRec.com: Is there a setup fee?

No. Site build, onboarding and training are included in the annual fee.

Cosign: What does a bare cosign verify actually prove?

Very little. Without a pinned certificate identity and OIDC issuer, it accepts a valid signature from any identity at all.

MyRec.com: Are card fees included?

No. Credit card processing is separate and you arrange your own merchant account.

Cosign: What is the risk of keyless signing?

Your OIDC provider becomes the root of trust. Compromise of that account yields genuine, verifiable signatures, so account security is the control that matters.

MyRec.com: Is there a contract?

No long-term contract is required, which is unusual in municipal software.

Cosign: Should we expect breaking changes?

Yes. Version 4 is announced to remove roughly half the flags, and a post-quantum migration is named as a further breaking change after that.

Share

Related pages

More on Cosign

More on MyRec.com

Keep looking

Other head to heads