Skip to content
DevUtils Online

DevOps

dokploy vs infracost

infracost leads by 4.3 · narrow

A

dokploy

88.6

38,560 stars · license n/a

B · leads

infracost

92.9

12,622 stars · Apache-2.0

dokploy versus infracost is a DevOps comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. dokploy is written mainly in TypeScript; infracost is written mainly in Go. The composite score is 88.6 for dokploy and 92.9 for infracost.

dokploy has 38,560 GitHub stars to infracost's 12,622, a gap of 25,938 (3.05×). Forks are 3,180 for dokploy and 702 for infracost. On the log scale used inside this pair, adoption is 100 versus 89, and the fork community is 100 versus 81.

Push history: dokploy 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 833 for dokploy (0.022 per star) and 4 for infracost (0.000 per star). Issue-health scores are 70 and 96; activity scores are 100 and 100.

dokploy is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. 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 30 for dokploy and 96 for infracost. This is a procurement signal, not legal advice.

In DevOps, both dokploy (38,560 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: dokploy is unpriced in this catalog, infracost is open source.

The lead is split. dokploy is furthest ahead on fork community (100 to 81), while infracost is furthest ahead on license flexibility (96 to 30). Choose the dimension a rollout cannot compromise on.

infracost finishes ahead at 92.9 against dokploy at 88.6, a 4.3 point narrow margin under the published weights.

Scores are computed inside this pair only. Method and weights.

Where they separate

The numbers

Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.

dokploy versus infracost metrics
Signal dokploy infracost
GitHub stars 38,560 12,622
Forks 3,180 702
Open issues 833 4
Adoption 100 89
Activity 100 100
Community 100 81
Issue health 70 96
License 30 96
Self-hosting 100 100
Composite 88.6 92.9

Questions this page answers

Which has more GitHub stars, dokploy or infracost?

dokploy has more GitHub stars: 38,560 versus 12,622 for infracost. The gap is 25,938 stars.

Which was updated more recently, dokploy or infracost?

dokploy was pushed more recently: 17 November 2026 versus 16 November 2026 for infracost. That is 1 days apart.

Can I self-host both dokploy and infracost?

Yes. This catalog marks both dokploy and infracost as self-hostable. Confirm each project's deploy docs before you plan a migration.

Which license is easier to embed in a commercial product, dokploy or infracost?

dokploy is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. 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.

Who wins the dokploy vs infracost score?

infracost scores 92.9 and dokploy scores 88.6. This page calls that a narrow lead for infracost.

Related comparisons