Softwr

Cloud · head to head

Dokku vs Jitsu

Dokku logo

Dokku

Cloud

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

From
Free
Rated
-
Jitsu logo

Jitsu

Developer Tools

Open source event pipeline that streams behavioural data to your own warehouse

From
Free
Rated
-

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.; Jitsu jitsu is a pipeline, not a customer data platform, so identity resolution, audience building and reverse ETL are absent and a marketing team expecting Segment parity will be disappointed.
  • They diverge on capability: Dokku covers Git push deploy, Jitsu covers Event collection.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which Dokku and Jitsu actually diverge.

Attributes where Dokku and Jitsu differ
AttributeDokkuJitsu
Pricing modelOpen source, no licence feePer month by event volume
PlatformsLinux, Docker, CLI, Self-hostedWeb, Linux, Docker, Kubernetes, iOS, Android
CategoryCloudDeveloper Tools

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 Jitsu

  • Event collection
  • Warehouse destinations
  • Connector syncs
  • Transformations
  • Bundled ClickHouse
  • Event debugger
  • Self-hosting
  • Custom domains

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 Jitsu
  • Moving off a managed platform when the monthly bill has grown faster than the traffic hasnot Jitsu
  • A consultancy that wants buildpack deployments without teaching every client team Kubernetesnot Jitsu
  • Keeping a legacy Procfile application alive on hardware you control after a managed platform deprecates its stacknot Jitsu

Jitsu

  • A team paying five figures a year to a customer data platform when all it actually does is send events to Snowflakenot Dokku
  • An engineering group that needs event collection running inside its own VPC for data residency or security review reasonsnot Dokku
  • A product analytics setup that wants raw events in the warehouse as the source of truth rather than trapped in a vendor toolnot Dokku
  • A startup that needs first-party event collection on its own domain to reduce loss from tracker blocking without paying CDP pricesnot 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.

Jitsu

  • Jitsu is a pipeline, not a customer data platform, so identity resolution, audience building and reverse ETL are absent and a marketing team expecting Segment parity will be disappointed.
  • Connector sync frequency is deliberately tiered, with the free plan limited to manual runs and one daily sync, so anything approaching operational freshness requires the paid plan or self-hosting.
  • Self-hosting means you own the reliability of a system that drops data silently when misconfigured, and event loss is uniquely hard to notice because nothing errors, the numbers are just quietly lower.
  • The connector catalogue is far smaller than Fivetran or Airbyte, so if your requirement is pulling from many SaaS sources rather than pushing events, Jitsu is the wrong half of the problem.
  • It is a small company with a small commercial team, so enterprise procurement processes around security review, contractual SLAs and support escalation take longer than with an incumbent vendor.

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

Jitsu

Free
  • Open SourceFree
    • MIT licence
    • Self-host on any cloud
    • No usage limits
  • Cloud FreeFree
    • Unlimited captured events
    • 200,000 active events per month
    • Manual connector runs only
  • Business$99/month
    • 2,000,000 active events per month
    • $40 per additional million events
    • Hourly connector sync frequency
  • Enterprise$undefined/year
    • Custom event volume
    • One minute sync frequency
    • Unlimited active syncs

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.

Choose Jitsu if

  • You need event collection.
  • You want to start without paying.
  • You work on Web, Linux, Docker, Kubernetes, iOS, Android.
  • You also want warehouse destinations.

Questions people ask

Is Dokku or Jitsu better?
Neither clearly leads. Dokku starts at Free and Jitsu at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Dokku or Jitsu?
Dokku starts at Free and Jitsu at Free.
Does Dokku or Jitsu run on more platforms?
Dokku runs on Linux, Docker, CLI, Self-hosted. Jitsu runs on Web, Linux, Docker, Kubernetes, iOS, Android.
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 Jitsu is typically brought in for.
What can Dokku do that Jitsu cannot?
Dokku covers Git push deploy, Heroku buildpacks, Datastore plugins, Automatic certificates. Jitsu covers Event collection, Warehouse destinations, Connector syncs, Transformations.

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.

Jitsu: Is Jitsu the same as Jitsi?

No. Jitsu is an open source event data pipeline. Jitsi is an unrelated video conferencing project.

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.

Jitsu: Can I self-host for free?

Yes. The project is MIT licensed with no usage limits when self-hosted.

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.

Jitsu: How does the cost compare with Segment?

The Business plan is 99 US dollars a month for two million active events, where a per-tracked-user CDP typically costs orders of magnitude more at comparable volume.

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.

Jitsu: Does Jitsu do identity resolution?

No. It transports and transforms events; identity stitching and audiences are not part of the product.

Share

Related pages

Other head to heads