conductor
Conductor is an open-source durable execution platform for microservices, AI agents and adaptive workflow graphs. Workflows are defined as graphs (JSON definitions) whose runtime choices, such as loops, branching, fan-out, tool calls, approvals, retries and cancellation, are executed durably by the Conductor server. It began at Netflix; the original Netflix/conductor repository is now archived, and conductor-oss is the actively developed open-source line.
It suits teams orchestrating many services and, increasingly, AI agents. Conductor has native LLM tasks, MCP tool calling, human approval steps and vector workflows for RAG, and its documentation shows an autonomous think-act agent loop that discovers tools via MCP, reasons with an LLM and repeats until done. It can be self-hosted with several persistence backends and message brokers, and a UI shows workflow executions.
Getting started: with Node.js 16+ and Java 21+, run `npm install -g @conductor-oss/conductor-cli` and `conductor server start`, then open http://localhost:8080. A Docker image is also available. Create your first workflow from the quickstart JSON with `conductor workflow create`.
Features
Why choose it
Trade-offs
Maintenance check
- Last commit
- 2026-10-23
- Commits, last 90 days
- 100+
- Releases, last 90 days
- 19
- Latest release
- v3.33.0-rc13 (2026-10-14)
- Open issues
- 279
- Recent issues with at least one comment
- 7/23
Oldest week on the left; the latest four weeks are orange. Source: GitHub commit activity.
Status rule: archived on GitHub = Archived; last commit within 90 days = Active; 91 to 365 days = Slowing; older = Stale. All figures come from the GitHub API on the date shown.
Most discussed open issues
- #1081 [FEATURE]: Add periodic batch job to clean up old terminal workflow history10 comments · 2026-05-12
- #588 PostgresLockDAO does not support recursive locks, causing stuck workflows10 comments · 2025-09-24
- #1280 Spring Boot 4 compatibility: server artifacts hard-reference Boot-3-only FQCNs (Jackson2ObjectMapperBuilderCustomizer, DataSourceAutoConfigu9 comments · 2026-07-13
- #1528 Epic: CVE remediation for Conductor-OSS 3.32.x8 comments · 2026-08-12
- #630 [Bug] Http Task executed twice after COMPLETED status [read thread for workaround]8 comments · 2025-10-30
Issue titles are quoted from GitHub. Open the link to check whether a problem still applies to the version you use.
Who it fits
- You want an Apache-2.0 durable workflow engine where workflows are defined as JSON graphs and workers can be written in any language.
- You want built-in LLM task types, MCP tool calling, human approval steps, and vector workflows on top of a microservice orchestrator.
- You prefer writing workflows purely as code rather than JSON graph definitions; Temporal or AutoKitteh fit better.
- You want a lightweight embedded rule engine inside a single Go binary with zero external middleware; RuleGo is designed for that.
How it differs
Conductor orchestrates JSON workflow graphs and includes native LLM and MCP task nodes; Temporal executes workflows written as native code in Python, Go, TypeScript, or Java.
Conductor is an Apache-2.0 distributed microservice and agent orchestration engine; n8n is a fair-code visual automation platform focused on 1,500+ SaaS integrations.
Compatibility
Quick start
Use cases
Alternatives
Featured in these lists
Comments
No comments yet. Be the first!