Skip to content
DevUtils Online

DevOps

infracost vs kestra

kestra leads by 3.0 · narrow

A

infracost

93.5

12,622 stars · Apache-2.0

B · leads

kestra

96.5

30,249 stars · Apache-2.0

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

kestra has 30,249 GitHub stars to infracost's 12,622, a gap of 17,627 (2.40×). Forks are 702 for infracost and 3,538 for kestra. On the log scale used inside this pair, adoption is 92 versus 100, and the fork community is 80 versus 100.

Push history: infracost was last pushed on 16 November 2026 (1 day ago), and kestra was last pushed on 17 November 2026 (0 days ago). Open issues stand at 4 for infracost (0.000 per star) and 651 for kestra (0.022 per star). Issue-health scores are 96 and 70; activity scores are 100 and 100.

Both infracost and kestra are listed as Apache-2.0. 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. The license score is therefore level at 96 versus 96, and the decision moves to adoption, activity, and hosting. This is a procurement signal, not legal advice.

In DevOps, both infracost (12,622 stars) and kestra (30,249 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: infracost is open source, kestra is open source.

The lead is split. infracost is furthest ahead on issue health (96 to 70), while kestra is furthest ahead on fork community (100 to 80). Choose the dimension a rollout cannot compromise on.

kestra finishes ahead at 96.5 against infracost at 93.5, a 3.0 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.

infracost versus kestra metrics
Signal infracost kestra
GitHub stars 12,622 30,249
Forks 702 3,538
Open issues 4 651
Adoption 92 100
Activity 100 100
Community 80 100
Issue health 96 70
License 96 96
Self-hosting 100 100
Composite 93.5 96.5

kestra

Orchestrate everything, everywhere. The open-source control plane for workflows across data, infrastructure, business processes and AI agents. Declarative YAML, event-driven, any language, Git-versioned, scalable to millions of executions.

Project site · GitHub · Full profile

Questions this page answers

Which has more GitHub stars, infracost or kestra?

kestra has more GitHub stars: 30,249 versus 12,622 for infracost. The gap is 17,627 stars.

Which was updated more recently, infracost or kestra?

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

Can I self-host both infracost and kestra?

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

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

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. kestra 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 infracost vs kestra score?

kestra scores 96.5 and infracost scores 93.5. This page calls that a narrow lead for kestra.

Related comparisons