Cloud · head to head
Dokku vs Kong Gateway

Dokku
Cloud
Single-server platform that accepts a git push and runs Heroku buildpacks on Docker
- From
- Free
- Rated
- -

Kong Gateway
APIs
Open-source and cloud API gateway for managing microservices traffic
- 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.; Kong Gateway the free open-source gateway lacks the analytics, portals, and support of the paid Konnect tiers.
- They diverge on capability: Dokku covers Git push deploy, Kong Gateway covers API request routing.
- Prices and features above were last checked on 31 August 2026.
Where they differ
Only the attributes on which Dokku and Kong Gateway actually diverge.
| Attribute | Dokku | Kong Gateway |
|---|---|---|
| Pricing model | Open source, no licence fee | freemium |
| Platforms | Linux, Docker, CLI, Self-hosted | web, linux, api |
| Category | Cloud | APIs |
| Founded | Unknown | 2017 |
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 Kong Gateway
- API request routing
- Plugin ecosystem
- Developer portals
- AI Gateway
- Analytics and observability
- SSO and audit logs
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 Kong Gateway
- Moving off a managed platform when the monthly bill has grown faster than the traffic hasnot Kong Gateway
- A consultancy that wants buildpack deployments without teaching every client team Kubernetesnot Kong Gateway
- Keeping a legacy Procfile application alive on hardware you control after a managed platform deprecates its stacknot Kong Gateway
Kong Gateway
- Routing and securing traffic across microservicesnot Dokku
- Publishing internal or external developer portalsnot Dokku
- Managing rate limits and authentication at the API edgenot Dokku
- Gateway-level routing to multiple LLM providersnot 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.
Kong Gateway
- The free open-source gateway lacks the analytics, portals, and support of the paid Konnect tiers.
- Plus tier caps API requests at 1M/month before incurring per-million overage charges.
- Enterprise pricing is custom and not published, making budgeting harder without sales contact.
- Configuration and plugin management can require significant operational expertise to run at scale.
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
Kong Gateway
Free- Free TrialFree
- 30-day enterprise functionality trial
- Unlimited gateways
- 30-day analytics retention
- Plus$undefined/month
- Up to 5 serverless, 2 hybrid, 2 dedicated cloud gateways
- 1M API requests/month included
- Up to 2 developer portals
- Enterprise$undefined/month
- Unlimited hybrid and dedicated cloud gateways
- Unlimited developer portals
- SSO and audit logs
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 Kong Gateway if
- You need api request routing.
- You want to start without paying.
- You work on web, linux, api.
- You also want plugin ecosystem.
Questions people ask
- Is Dokku or Kong Gateway better?
- Neither clearly leads. Dokku starts at Free and Kong Gateway at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, Dokku or Kong Gateway?
- Dokku starts at Free and Kong Gateway at Free.
- Does Dokku or Kong Gateway run on more platforms?
- Dokku runs on Linux, Docker, CLI, Self-hosted. Kong Gateway runs on web, linux, api.
- 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 Kong Gateway is typically brought in for.
- What can Dokku do that Kong Gateway cannot?
- Dokku covers Git push deploy, Heroku buildpacks, Datastore plugins, Automatic certificates. Kong Gateway covers API request routing, Plugin ecosystem, Developer portals, AI Gateway.
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.
Kong Gateway: Is Kong Gateway free?
Kong's core gateway is open source and free to self-host. Kong Konnect, the managed cloud platform, offers a 30-day free trial before moving to paid Plus or custom Enterprise pricing.
SourceDokku: 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.
Kong Gateway: How is usage metered on the Plus plan?
The Plus plan includes 1M API requests per month, with additional usage billed at $200 per extra 1 million requests up to a 10M/month cap, plus per-gateway and per-LLM-model charges.
SourceDokku: 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.
Kong Gateway: What support is included?
Plus includes email support with a 2-business-day SLA, while Enterprise adds dedicated success managers and professional services.
SourceDokku: 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.
Related pages
More on Kong Gateway
Other head to heads
- Dokku vs Fly.io
- Dokku vs Render
- Dokku vs Heroku
- Dokku vs Coolify
- Dokku vs CapRover
- Dokku vs Qovery
- Dokku vs Porter
- Dokku vs Railway
- Dokku vs Northflank
- Dokku vs Podman
- Dokku vs Portworx
- Dokku vs minikube
- Dokku vs Scaleway
- Dokku vs SST
- Dokku vs Tencent Cloud
- Dokku vs Terragrunt
- Dokku vs Skopeo
- Dokku vs Tyk
- Dokku vs Moesif
- Dokku vs Treblle
- Dokku vs Convoy
- Dokku vs Janus Gateway
- Dokku vs Spring Cloud Gateway
- Dokku vs Gravitee
- Dokku vs Strapi
- Dokku vs WSO2 API Manager
- Dokku vs AWS API Gateway
- Dokku vs GraphQL Apollo
- Dokku vs Appwrite
- Dokku vs Payload CMS
- Dokku vs Portkey
- Dokku vs Prisma
- Dokku vs RapidAPI
- Dokku vs REST Client VSCode
- Dokku vs Rutter
- Kong Gateway vs Fly.io
- Kong Gateway vs Render
- Kong Gateway vs Heroku
- Kong Gateway vs Coolify
- Kong Gateway vs CapRover
- Kong Gateway vs Qovery
- Kong Gateway vs Porter
- Kong Gateway vs Railway
- Kong Gateway vs Northflank
- Kong Gateway vs Podman
- Kong Gateway vs Portworx
- Kong Gateway vs minikube
- Kong Gateway vs Scaleway
- Kong Gateway vs SST
- Kong Gateway vs Tencent Cloud
- Kong Gateway vs Terragrunt
- Kong Gateway vs Skopeo
- Kong Gateway vs Tyk
- Kong Gateway vs Moesif
- Kong Gateway vs Treblle
- Kong Gateway vs Convoy
- Kong Gateway vs Janus Gateway
- Kong Gateway vs Spring Cloud Gateway
- Kong Gateway vs Gravitee
- Kong Gateway vs Strapi
- Kong Gateway vs WSO2 API Manager
- Kong Gateway vs AWS API Gateway
- Kong Gateway vs GraphQL Apollo
- Kong Gateway vs Appwrite
- Kong Gateway vs Payload CMS
- Kong Gateway vs Portkey
- Kong Gateway vs Prisma
- Kong Gateway vs RapidAPI
- Kong Gateway vs REST Client VSCode
- Kong Gateway vs Rutter
