head to head · open source

conductor vs jido

conductor has 32,401 GitHub stars, 1,051 forks, 253 open issues and last shipped yesterday. jido has 1,902 stars, 121 forks, 1 open issues and last shipped 4 days ago. conductor leads on adoption by 1,604% (32,401 vs 1,902 stars). conductor is written in Java under Apache-2.0; jido is written in Elixir under Apache-2.0. conductor has attracted 3% as many forks as stars, jido 6%. conductor was the more recently maintained of the two, and both are self-hostable with no licence fee.

Two open source projects, one decision. Both are free and self-hostable — the differences are community size, license terms, language stack and release pace.

conductor ★ 32K jido ★ 1.9K category Infrastructure & Operations

← all 20902 open source comparisons

Side by side

conductor jido
GitHub stars ★ 32K ★ 1.9K
License Apache-2.0 Apache-2.0
Written in Java Elixir
Last push 2026-11-02 2026-10-30
Forks ⑂ 1.1K ⑂ 121
Self-hosting Yes Yes
Data ownership Your server Your server

pick conductor if

  • You weight community size — 32K 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

full conductor profile →

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

full jido profile →

About conductor

Conductor Durable Execution for Workflows and Agents Build agents that adapt. Run graphs that endure. Conductor is an open source durable execution platform for microservices, AI agents, and adaptive workflow graphs. It turns runtime choices—loops, branching, fan out, tool calls, approvals, retries, and cancellation—into durable, inspectable execution. It originated at Netflix and is actively maintained by Orkes and the community. Get Running in 60 Seconds Prerequisites: Node.js v16+ and Java 21+ must be installed. Open — your server is running with the built in ui next UI. Upgrading from a previous version? The…

read the full conductor 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…

read the full jido 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 conductor or jido more popular?

conductor has 32,401 GitHub stars and jido has 1,902. conductor has the larger community by that measure.

Are conductor and jido free?

Both are open source. conductor is licensed under Apache-2.0 and jido under Apache-2.0. Neither carries a licence fee.

What is the difference between conductor and jido?

conductor 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, conductor or jido?

Choose conductor if you want the larger community (32,401 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.