explaingit

conductor-oss/conductor

Analysis updated 2026-06-20

31,776JavaAudience · developerComplexity · 4/5LicenseSetup · hard

TLDR

Conductor is an open-source workflow engine that reliably coordinates multi-step processes across distributed systems, automatically resuming from the exact point of failure rather than restarting from scratch.

Mindmap

mindmap
  root((conductor))
    What it does
      Orchestrates multi-step workflows
      Resumes from failure point
      Retries and timeouts
    Tech Stack
      Java server
      Python Go JS workers
      JSON workflow definitions
    Use Cases
      Payment pipelines
      User onboarding
      AI agent loops
      ETL pipelines
    Audience
      Backend developers
      Microservice teams
      AI engineers
Click or tap to explore — scroll the page freely

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

What do people build with it?

USE CASE 1

Build a payment processing pipeline that automatically retries failed steps and resumes from the last successful point after a crash.

USE CASE 2

Orchestrate a user onboarding flow across multiple microservices so each step completes reliably even when individual services go down.

USE CASE 3

Create durable AI agent loops where an LLM thinks and acts across multiple steps, surviving failures and requiring human approval at key points.

USE CASE 4

Run ETL pipelines with parallel branches, timeouts, and automatic retries without writing custom failure-recovery logic.

What is it built with?

JavaPythonGoJavaScript

How does it compare?

conductor-oss/conductorapache/kafkabinarywang/wxjava
Stars31,77632,52632,638
LanguageJavaJavaJava
Setup difficultyhardhardmoderate
Complexity4/54/53/5
Audiencedeveloperdeveloperdeveloper

Figures from each repo's GitHub metadata at analysis time.

How do you get it running?

Difficulty · hard Time to first run · 1h+

Requires Java 21 for the server plus a running datastore (e.g. Redis/Elasticsearch), workers can be in any language but the server setup takes real infra config.

Apache 2.0, use freely for any purpose including commercial, modify and redistribute with attribution.

In plain English

Conductor is an open-source workflow engine that coordinates multi-step processes across distributed systems, making sure every step completes reliably even when servers crash, networks fail, or individual services are temporarily unavailable. The core problem it solves is that real-world processes, like processing a payment, onboarding a user, or running an AI agent loop, involve many steps across many services, and without a coordinator, a failure halfway through leaves things in an inconsistent state with no clear way to resume. Conductor works by representing workflows as JSON definitions made up of tasks. Each task is executed by a worker, which is a small piece of code you write in any language: Java, Python, Go, JavaScript, or others. Workers poll Conductor for work, execute their logic, and report results back. Conductor handles all the orchestration logic, including retries on failure, timeouts, conditional branches, parallel forks, and sub-workflow calls. Every step is persisted, so if a workflow fails at step seven of twenty, it resumes from step seven rather than starting over. For AI use cases, Conductor natively supports LLM task types that call language model providers, MCP tool calling, human-in-the-loop approval steps, and vector database lookups. This makes it possible to build autonomous AI agents where Conductor manages the think-act loop durably. You would use Conductor when building microservice orchestration, long-running business processes, ETL pipelines, or AI agent systems that need to survive failures and be observable, auditable, and replayable. The server is written in Java and requires Java 21, while workers can be written in any supported language. It was originally built at Netflix and is now maintained as an open-source project under the Apache 2.0 license.

Copy-paste prompts

Prompt 1
I'm using conductor-oss/conductor. Write a JSON workflow definition that processes a payment: charge the card, update inventory, send a confirmation email, and roll back if any step fails.
Prompt 2
Using conductor-oss/conductor with Python workers, show me how to write a worker that polls for tasks, executes business logic, and reports results back to Conductor.
Prompt 3
I want to build an AI agent loop with conductor-oss/conductor where an LLM decides the next action and a human approves before execution. Show me the workflow JSON and the worker code.
Prompt 4
Help me set up conductor-oss/conductor locally with Docker. Show the steps to start the server, register a simple workflow, and run a test worker in Java.
Prompt 5
Using conductor-oss/conductor, how do I define a workflow with parallel forks that merge back and then call a sub-workflow for the final step?

Frequently asked questions

What is conductor?

Conductor is an open-source workflow engine that reliably coordinates multi-step processes across distributed systems, automatically resuming from the exact point of failure rather than restarting from scratch.

What language is conductor written in?

Mainly Java. The stack also includes Java, Python, Go.

What license does conductor use?

Apache 2.0, use freely for any purpose including commercial, modify and redistribute with attribution.

How hard is conductor to set up?

Setup difficulty is rated hard, with roughly 1h+ to a first successful run.

Who is conductor for?

Mainly developer.

Open on GitHub → Explain another repo

This repo across BitVibe Labs

Scan in gitsafehub Deploy in gitdeployhub conductor-oss on gitmyhub

Verify against the repo before relying on details.