A · leads
dokku
99.1
32,230 stars · MIT
DevOps
dokku leads by 5.0 · narrow
A · leads
99.1
32,230 stars · MIT
B
94.1
12,622 stars · Apache-2.0
dokku versus infracost is a DevOps comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. dokku is written mainly in Shell; infracost is written mainly in Go. The composite score is 99.1 for dokku and 94.1 for infracost.
dokku has 32,230 GitHub stars to infracost's 12,622, a gap of 19,608 (2.55×). Forks are 2,095 for dokku and 702 for infracost. On the log scale used inside this pair, adoption is 100 versus 91, and the fork community is 100 versus 86.
Push history: dokku was last pushed on 17 November 2026 (0 days ago), and infracost was last pushed on 16 November 2026 (1 day ago). Open issues stand at 39 for dokku (0.001 per star) and 4 for infracost (0.000 per star). Issue-health scores are 96 and 96; activity scores are 100 and 100.
dokku is listed as MIT, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. infracost is listed as Apache-2.0, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. License scores in this pair are 96 for dokku and 96 for infracost. This is a procurement signal, not legal advice.
In DevOps, both dokku (32,230 stars) and infracost (12,622 stars) are marked self-hostable. Deploy scores are 100 and 100. Running either one means you own upgrades, backups, and the license duties that follow a modified copy. Pricing labels on file: dokku is open source, infracost is open source.
dokku is ahead on every scored dimension that is not level. Level dimensions: recent activity, issue health, license flexibility, self-hosting. The widest gap is fork community at 14 points (100 vs 86), and the tightest is self-hosting at 0 points (100 vs 100).
dokku finishes ahead at 99.1 against infracost at 94.1, a 5.0 point narrow margin under the published weights.
Scores are computed inside this pair only. Method and weights.
Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.
| Signal | dokku | infracost |
|---|---|---|
| GitHub stars | 32,230 | 12,622 |
| Forks | 2,095 | 702 |
| Open issues | 39 | 4 |
| Adoption | 100 | 91 |
| Activity | 100 | 100 |
| Community | 100 | 86 |
| Issue health | 96 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 99.1 | 94.1 |
A docker-powered PaaS that helps you build and manage the lifecycle of applications
Cloud cost intelligence for engineers, AI coding agents, and CI/CD 💰📉 Shift FinOps Left!
dokku has more GitHub stars: 32,230 versus 12,622 for infracost. The gap is 19,608 stars.
dokku was pushed more recently: 17 November 2026 versus 16 November 2026 for infracost. That is 1 days apart.
Yes. This catalog marks both dokku and infracost as self-hostable. Confirm each project's deploy docs before you plan a migration.
dokku is listed as MIT, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. infracost is listed as Apache-2.0, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
dokku scores 99.1 and infracost scores 94.1. This page calls that a narrow lead for dokku.