head to head · open source
conductor vs libfork
conductor has 32,401 GitHub stars, 1,051 forks, 253 open issues and last shipped yesterday. libfork has 901 stars, 46 forks, 10 open issues and last shipped 5 months ago. conductor leads on adoption by 3,496% (32,401 vs 901 stars). conductor is written in Java under Apache-2.0; libfork is written in C++ under MPL-2.0. conductor has attracted 3% as many forks as stars, libfork 5%. 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.
← all 20902 open source comparisons
Side by side
| conductor | libfork | |
|---|---|---|
| GitHub stars | ★ 32K | ★ 901 |
| License | Apache-2.0 | MPL-2.0 |
| Written in | Java | C++ |
| Last push | 2026-11-02 | 2026-05-25 |
| Forks | ⑂ 1.1K | ⑂ 46 |
| 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
pick libfork if
- You want the libfork feature set and don't need the biggest community
- You prefer the MPL-2.0 license terms
- Your stack matches C++
- You evaluated both and libfork fits your workflow better
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 libfork
Welcome to libfork 🍴 A bleeding edge, lock free, wait free, continuation stealing coroutine tasking library. Now supplying 🌵! Libfork is primarily an abstraction for fully portable, strict, fork join parallelism. This is made possible without the use of any macros/inline assembly using C++20's coroutines. Ultra fine grained parallelism (the ability to spawn tasks with very low overhead) is enabled by an innovative implementation of an (almost) non allocating cactus stack utilizing segmented stacks . Libfork presents a cross platform API that decouples scheduling tasks (a customization point) from writing…
read the full libfork 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 libfork more popular?
conductor has 32,401 GitHub stars and libfork has 901. conductor has the larger community by that measure.
Are conductor and libfork free?
Both are open source. conductor is licensed under Apache-2.0 and libfork under MPL-2.0. Neither carries a licence fee.
What is the difference between conductor and libfork?
conductor is written in Java and libfork in C++. 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 libfork?
Choose conductor if you want the larger community (32,401 stars) or its Apache-2.0 licence terms. Choose libfork if its feature set, stack or MPL-2.0 licence fits better. Both are self-hostable.