head to head · open source
Kestra vs jido
Kestra has 30,122 GitHub stars, 3,495 forks, 713 open issues and last shipped yesterday. jido has 1,902 stars, 121 forks, 1 open issues and last shipped 4 days ago. Kestra leads on adoption by 1,484% (30,122 vs 1,902 stars). Kestra is written in Java under Apache-2.0; jido is written in Elixir under Apache-2.0. Kestra has attracted 12% as many forks as stars, jido 6%. Kestra was the more recently maintained of the two, and both are self-hostable with no licence fee. The two share 1 topic tag (ai-agents), 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 20902 open source comparisons
Side by side
| Kestra | jido | |
|---|---|---|
| GitHub stars | ★ 30K | ★ 1.9K |
| License | Apache-2.0 | Apache-2.0 |
| Written in | Java | Elixir |
| Last push | 2026-11-02 | 2026-10-30 |
| Forks | ⑂ 3.5K | ⑂ 121 |
| Self-hosting | Yes | Yes |
| Data ownership | Your server | Your server |
pick Kestra if
- You weight community size — 30K 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 jido if
- You want the jido feature set and don't need the biggest community
- You prefer the Apache-2.0 license terms
- Your stack matches Elixir
- You evaluated both and jido fits your workflow better
About Kestra
Open source orchestration platform for data, AI, and infrastructure workflows Click on the image to learn how to get started with Kestra in 3 minutes. 🌟 What is Kestra? Kestra is an open source, event driven orchestration platform for data, AI, and infrastructure workflows. It unifies scheduled and event driven automation behind a declarative, language agnostic interface. By bringing Infrastructure as Code best practices to your data, process, and microservice pipelines, you can build reliable workflows directly from the UI in just a few lines of YAML, let the built in AI Copilot write them for you, or generate…
read the full Kestra overview →
About jido
Jido Jido is an autonomous agent framework for Elixir, built for workflows and multi agent systems. Define agents, connect them to actions, signals, and directives, and run them with supervision and fault tolerance built in. The name "Jido" (自動) comes from the Japanese word meaning "automatic" or "automated", where 自 (ji) means "self" and 動 (dō) means "movement". Learn more about Jido at jido.run. Overview Jido helps you build agent systems as ordinary Elixir and OTP software. Agents hold state and implement cmd/2 Actions do work and transform that state Signals route events into the system Directives describe…
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 jido more popular?
Kestra has 30,122 GitHub stars and jido has 1,902. Kestra has the larger community by that measure.
Are Kestra and jido free?
Both are open source. Kestra is licensed under Apache-2.0 and jido under Apache-2.0. Neither carries a licence fee.
What is the difference between Kestra and jido?
Kestra is written in Java and jido in Elixir. 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 jido?
Choose Kestra if you want the larger community (30,122 stars) or its Apache-2.0 licence terms. Choose jido if its feature set, stack or Apache-2.0 licence fits better. Both are self-hostable.