head to head · open source
Kestra vs devopness
Kestra has 28,148 GitHub stars, 2,999 forks, 713 open issues and last shipped yesterday. devopness has 558 stars, 175 forks, 14 open issues and last shipped yesterday. Kestra leads on adoption by 4,944% (28,148 vs 558 stars). Kestra is written in Java under Apache-2.0; devopness is written in TypeScript under Apache-2.0. Kestra has attracted 11% as many forks as stars, devopness 31%. Kestra was the more recently maintained of the two, and both are self-hostable with no licence fee. The two share 1 topic tag (devops), so they are genuine substitutes rather than adjacent tools.
Two open source projects, one decision. Both are free and self-hostable — the differences are community size, license terms, language stack and release pace.
← all 8884 open source comparisons
Side by side
| Kestra | devopness | |
|---|---|---|
| GitHub stars | ★ 28K | ★ 558 |
| License | Apache-2.0 | Apache-2.0 |
| Written in | Java | TypeScript |
| Last push | 2026-09-17 | 2026-09-17 |
| Forks | ⑂ 3.0K | ⑂ 175 |
| Self-hosting | Yes | Yes |
| Data ownership | Your server | Your server |
pick Kestra if
- You weight community size — 28K stars and counting
- You want the Apache-2.0 license terms
- Your stack matches Java
- You value the larger contributor base for long-term maintenance
pick devopness if
- You want the devopness feature set and don't need the biggest community
- You prefer the Apache-2.0 license terms
- Your stack matches TypeScript
- You evaluated both and devopness fits your workflow better
About Kestra
Kestra is an open source, event driven orchestration platform for data, AI, and infrastructure workflows. It operates in the Java based ecosystem and is licensed under Apache 2.0. The project provides a unified interface for both scheduled and real time automation, supporting declarative workflow definitions in YAML while also offering visual and AI assisted authoring.
read the full Kestra overview →
About devopness
Stop managing DevOps. Ship more, stress less. DevOps Happiness for AI agents and humans. One platform · Any cloud · Any stack · Free plan Devopness Deploy apps and provision cloud infrastructure from scratch on AWS, Azure, GCP, DigitalOcean, and Hetzner: in accounts you control. One platform to replace many tools: Terraform + Ansible + Jenkins + PaaS (Vercel, Heroku, etc), and stack specific server panels. Manage apps, Linux servers, and cloud infrastructure from anywhere: web, mobile, API, or natural language in your AI agent through MCP. No SSH or cloud console for routine work. Create free account · Docs · Dis…
read the full devopness overview →
More in Infrastructure & Operations
Related comparisons
More Orchestration & Scheduling projects
Compare either of these against the rest of the Orchestration & Scheduling field.
Frequently asked questions
Is Kestra or devopness more popular?
Kestra has 28,148 GitHub stars and devopness has 558. Kestra has the larger community by that measure.
Are Kestra and devopness free?
Both are open source. Kestra is licensed under Apache-2.0 and devopness under Apache-2.0. Neither carries a licence fee.
What is the difference between Kestra and devopness?
Kestra is written in Java and devopness in TypeScript. The practical differences are community size, licence terms, language stack and release cadence — all compared in the table above.
Which should I choose, Kestra or devopness?
Choose Kestra if you want the larger community (28,148 stars) or its Apache-2.0 licence terms. Choose devopness if its feature set, stack or Apache-2.0 licence fits better. Both are self-hostable.