Softwr

Government · head to head

CKAN vs Cosign

CKAN logo

CKAN

Government

Open Source Data Portal Platform

From
Free
Free plan
Yes
Full reviewWebsite
Cosign logo

Cosign

Cybersecurity

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

From
Free
Free plan
Yes
Full reviewWebsite

The short version

  • Each has a real cost: CKAN the package install path requires Ubuntu 20.04 or 22.04 64-bit specifically; other operating systems must use the source install; 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.
  • They diverge on capability: CKAN covers Dataset Management, Cosign covers Keyless signing.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which CKAN and Cosign actually diverge.

Attributes where CKAN and Cosign differ
AttributeCKANCosign
Pricing modelfreeOpen source, no licence fee
PlatformsWebmacOS, Linux, Windows, Docker
CategoryGovernmentCybersecurity
Founded2006Unknown

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 CKAN

  • Dataset Management
  • Data Harvesting
  • API Access
  • Visualization
  • Extensions
  • DataPusher
  • Harvester
  • Third-party Tools

Only in Cosign

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

What people use each for

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

CKAN

  • Publishing open government datasets in a searchable public data portalnot Cosign
  • Self-hosting a data catalogue with harvesting and an APInot Cosign

Cosign

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

Where each one falls short

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

CKAN

  • The package install path requires Ubuntu 20.04 or 22.04 64-bit specifically; other operating systems must use the source install
  • Only Solr 9 and Solr 8 are supported, and from CKAN 2.10 they are the only Solr versions supported at all
  • A working deployment requires PostgreSQL, Solr, Redis, nginx, supervisor and uWSGI to be installed and maintained separately
  • Python 3.10 or later is required

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.

Pricing, plan by plan

CKAN

Free
  • Open SourceFree
    • Data Management
    • API Access
    • Visualization

Cosign

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

Which should you pick?

Choose CKAN if

  • You need dataset management.
  • You want to start without paying.
  • You also want data harvesting.
CKAN review

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

Questions people ask

Is CKAN or Cosign better?
Neither clearly leads. CKAN starts at Free and Cosign at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, CKAN or Cosign?
CKAN starts at Free and Cosign at Free.
Does CKAN or Cosign run on more platforms?
CKAN runs on Web. Cosign runs on macOS, Linux, Windows, Docker.
Can I use CKAN for free?
Both have a free tier, so you can try either at no cost before committing.
What is CKAN best used for?
CKAN is most often used for publishing open government datasets in a searchable public data portal, self-hosting a data catalogue with harvesting and an api. Of those, publishing open government datasets in a searchable public data portal and self-hosting a data catalogue with harvesting and an api are not what Cosign is typically brought in for.
What can CKAN do that Cosign cannot?
CKAN covers Dataset Management, Data Harvesting, API Access, Visualization. Cosign covers Keyless signing, Key and KMS signing, Registry-native storage, In-toto attestations.

Answered from the vendors’ own pages

CKAN: Is CKAN open-source and what license is it available under?

Yes, CKAN is an open-source data management system built on Python and available on GitHub. The license terms are available on their GitHub repository.

Source
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.

CKAN: Does CKAN offer commercial support for organizations?

Yes, CKAN offers commercial support through certified providers including Link Digital and Datopian. Support includes advisory services, application development, integration, managed hosting, and web development.

Source
Cosign: Is signing alone enough?

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

CKAN: Who is responsible for hosting costs when running CKAN?

Organizations deploying CKAN are responsible for their own hosting infrastructure. Commercial providers like Datopian and Link Digital offer managed hosting services if organizations prefer not to self-host.

Source
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.

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.

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 CKAN

More on Cosign

Keep looking

Other head to heads