head to head · open source

conductor vs workflow

conductor has 32,401 GitHub stars, 1,051 forks, 253 open issues and last shipped yesterday. workflow has 2,487 stars, 387 forks, 360 open issues and last shipped yesterday. conductor leads on adoption by 1,203% (32,401 vs 2,487 stars). conductor is written in Java under Apache-2.0; workflow is written in TypeScript under Apache-2.0. conductor has attracted 3% as many forks as stars, workflow 16%. workflow was the more recently maintained of the two, and both are self-hostable with no licence fee. The two share 2 topic tags (durable-execution, workflow-engine), 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.

conductor ★ 32K workflow ★ 2.5K category Infrastructure & Operations

← all 20902 open source comparisons

Side by side

conductor workflow
GitHub stars ★ 32K ★ 2.5K
License Apache-2.0 Apache-2.0
Written in Java TypeScript
Last push 2026-11-02 2026-11-02
Forks ⑂ 1.1K ⑂ 387
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 workflow if

  • You want the workflow 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 workflow fits your workflow better

full workflow 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 workflow

Workflow SDK Workflow SDK makes TypeScript and JavaScript functions durable. It persists workflow progress, retries failed steps, and provides built in observability. Workflows can suspend without using compute while they wait. Quick start Install the SDK in an existing project: Configure the integration for your framework. For example, with Next.js: Then start a workflow from an API route, Server Action, or other server side code: Run your app, then open the local observability UI in another terminal: Choose your framework in the getting started guides. [!NOTE] The workflow package includes its full…

read the full workflow 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 workflow more popular?

conductor has 32,401 GitHub stars and workflow has 2,487. conductor has the larger community by that measure.

Are conductor and workflow free?

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

What is the difference between conductor and workflow?

conductor is written in Java and workflow 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, conductor or workflow?

Choose conductor if you want the larger community (32,401 stars) or its Apache-2.0 licence terms. Choose workflow if its feature set, stack or Apache-2.0 licence fits better. Both are self-hostable.