Softwr

Cloud · head to head

Dokku vs Sigstore

Dokku logo

Dokku

Cloud

Single-server platform that accepts a git push and runs Heroku buildpacks on Docker

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: Dokku one maintainer accounts for nearly all human commit activity and the project records roughly 10,500 US dollars of annual income on Open Collective, which is not enough to fund a maintainer, so continuity rests on one person continuing to volunteer.; 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: Dokku covers Git push deploy, Sigstore covers Fulcio.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which Dokku and Sigstore actually diverge.

Attributes where Dokku and Sigstore differ
AttributeDokkuSigstore
Pricing modelOpen source, no licence feeOpen source, public instance free to use
PlatformsLinux, Docker, CLI, Self-hostedWeb, Linux, macOS, Windows, Self-hosted
CategoryCloudCybersecurity

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 Dokku

  • Git push deploy
  • Heroku buildpacks
  • Datastore plugins
  • Automatic certificates
  • Zero downtime deploys
  • Pluggable schedulers

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.

Dokku

  • Running a dozen side projects and client applications on one virtual private server with Heroku style deploymentnot Sigstore
  • Moving off a managed platform when the monthly bill has grown faster than the traffic hasnot Sigstore
  • A consultancy that wants buildpack deployments without teaching every client team Kubernetesnot Sigstore
  • Keeping a legacy Procfile application alive on hardware you control after a managed platform deprecates its stacknot Sigstore

Sigstore

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

Where each one falls short

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

Dokku

  • One maintainer accounts for nearly all human commit activity and the project records roughly 10,500 US dollars of annual income on Open Collective, which is not enough to fund a maintainer, so continuity rests on one person continuing to volunteer.
  • Dokku Pro asks 849 US dollars for a lifetime licence from a project with no disclosed legal entity behind the promise and no published refund terms, while the product is still described as in development at early bird pricing.
  • Dokku is single-server by design, and the k3s scheduler that provides multi-node support is missing log retrieval, process inspection and content-based health checks, with a post-run hook the documentation says does not consistently fire.
  • Supported operating systems are limited to Ubuntu 22.04 or 24.04 and Debian 11 or later, so organisations standardised on Red Hat, Rocky or Alma Linux cannot run it on their approved base image.
  • Backups are separate commands per datastore plugin that you schedule yourself, with no unified snapshot, no point-in-time recovery and no tested restore path, so verifying that a restore works is entirely your responsibility.

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

Dokku

Free
  • DokkuFree
    • MIT licensed, no usage limits
    • Command line and SSH only
    • All datastore and certificate plugins
  • Dokku Pro$849/one-time
    • Lifetime licence with free upgrades and no subscription
    • Covers 1 production and 2 pre-production servers
    • Web dashboard and JSON REST API

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

  • You need git push deploy.
  • You want to start without paying.
  • You work on Linux, Docker, CLI, Self-hosted.
  • You also want heroku buildpacks.
Dokku 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 Dokku or Sigstore better?
Neither clearly leads. Dokku 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, Dokku or Sigstore?
Dokku starts at Free and Sigstore at Free.
Does Dokku or Sigstore run on more platforms?
Dokku runs on Linux, Docker, CLI, Self-hosted. Sigstore runs on Web, Linux, macOS, Windows, Self-hosted.
Can I use Dokku for free?
Both have a free tier, so you can try either at no cost before committing.
What is Dokku best used for?
Dokku is most often used for running a dozen side projects and client applications on one virtual private server with heroku style deployment, moving off a managed platform when the monthly bill has grown faster than the traffic has, a consultancy that wants buildpack deployments without teaching every client team kubernetes, keeping a legacy procfile application alive on hardware you control after a managed platform deprecates its stack. Of those, running a dozen side projects and client applications on one virtual private server with heroku style deployment and moving off a managed platform when the monthly bill has grown faster than the traffic has are not what Sigstore is typically brought in for.
What can Dokku do that Sigstore cannot?
Dokku covers Git push deploy, Heroku buildpacks, Datastore plugins, Automatic certificates. Sigstore covers Fulcio, Rekor, Keyless signing, Multi-language clients.

Answered from the vendors’ own pages

Dokku: Is Dokku still maintained?

Yes. Version 0.38.27 shipped in August 2026 with roughly six releases in the preceding two months. The caveat is that one maintainer writes nearly all of it.

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.

Dokku: What does Dokku Pro give me over the free edition?

A web dashboard, a JSON REST API, git push over HTTPS, browser log tailing, team management and email support from the maintainers. It costs 849 US dollars once for one production and two pre-production servers.

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.

Dokku: Can Dokku run across multiple servers?

Only through the k3s or Nomad schedulers. The k3s path is missing several commands and health check types, and the older Kubernetes scheduler is deprecated and no longer developed.

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.

Dokku: Will my Heroku application run on it unchanged?

Usually. Dokku runs the same buildpacks and reads a Procfile, so the application layer normally moves across. Add-ons, scaling behaviour and backups are the parts you have to rebuild.

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 Dokku

More on Sigstore

Keep looking

Other head to heads