Orchestrating distributed systems means wrestling with failures, retries, and state recovery. Conductor handles all of that so you don't have to.

Conductor is an open-source, durable workflow engine built at Netflix for orchestrating microservices, AI agents, and durable workflows at internet scale. Trusted in production at Netflix, Tesla, LinkedIn, and J.P. Morgan. Actively maintained by Orkes and a growing community.

Get Running in 60 Seconds

npm install -g @conductor-oss/conductor-cli
conductor server start

Open http://localhost:8080 — your server is running with the built-in UI.

Run your first workflow:

# Create a workflow that calls an API and parses the response — no workers needed
curl -s https://raw.githubusercontent.com/conductor-oss/conductor/main/docs/quickstart/workflow.json -o workflow.json
conductor workflow create workflow.json
conductor workflow start -w hello_workflow --sync

See the Quickstart guide for the full walkthrough, including writing workers and replaying workflows.

docker run -p 8080:8080 conductoross/conductor:latest

All CLI commands have equivalent cURL/API calls. See the Quickstart for details.

Why Conductor is the workflow engine of choice for developers

AI-Native Orchestration

Conductor keeps orchestration deterministic by separating it from business logic. Workflows are defined as JSON; workers are plain code in any language and can call any system.

This gives you:

• AI-native orchestration: LLMs can generate and modify JSON workflow definitions directly, and Conductor executes them immediately.
• Deterministic orchestration and safe replay without forcing your business logic into a framework.
• Fast iteration by updating orchestration without redeploying workers.

Conductor scales horizontally to the internet scale by scaling both server and workers scaling independently based on queue depth and throughput. See the production deployment guide and scaling workers guide.

Conductor Skills for AI Agents

Conductor Skills are skills for your AI agent to create, manage and deploy workflows. No code-compile-deploy loop, just describe what you want, add context and have workflows running. You can also use it to build end to end applications that are backed by Conductor workflows.

Claude

# Install Skills for Claude Code
/plugin marketplace add conductor-oss/conductor-skills
/plugin install conductor@conductor-skills

Install for all detected agents

One command to auto-detect every supported agent on your system and install globally where possible. Re-run anytime — it only installs for newly detected agents.

macOS / Linux

curl -sSL https://conductor-oss.github.io/conductor-skills/install.sh | bash -s -- --all

Windows (PowerShell) / (cmd)

# powershell
irm https://conductor-oss.github.io/conductor-skills/install.ps1 -OutFile install.ps1; .\install.ps1 -All

# cmd
powershell -c "irm https://conductor-oss.github.io/conductor-skills/install.ps1 -OutFile install.ps1; .\install.ps1 -All"

SDKs

Documentation & Community

• Documentation — Architecture, guides, API reference, and cookbook recipes.
• Slack — Community discussions and support.
• Community Forum — Ask questions and share patterns.

Backend Configuration

Build From Source

Requirements: Docker Desktop, Java (JDK) 21+, Node 18 (for UI)

git clone https://github.com/conductor-oss/conductor
cd conductor
./gradlew build

# (optional) Build UI
# ./build_ui.sh

# Start local server
cd server
../gradlew bootRun

See the full build guide for details.

FAQ

Yes. Conductor OSS is the continuation of the original Netflix Conductor repository after Netflix contributed the project to the open-source foundation.

Yes. Conductor is a fully open-source workflow engine licensed under Apache 2.0. You can self-host on your own infrastructure with 8+ persistence backends and 6 message brokers.

Yes. Orkes is the primary maintainer and offers an enterprise SaaS platform for Conductor across all major cloud providers.

Yes. Built at Netflix, battle-tested at internet scale. Conductor scales horizontally across multiple server instances to handle billions of workflow executions.

Yes. Conductor pioneered durable execution patterns, ensuring workflows and durable agents complete reliably despite infrastructure failures or crashes. Every step is persisted and recoverable.

Yes. Conductor preserves full execution history indefinitely. You can restart from the beginning, rerun from a specific task, or retry just the failed step — via API or UI.

Yes. Conductor provides native integration with 14+ LLM providers (Anthropic, OpenAI, Gemini, Bedrock, and more), MCP tool calling, function calling, human-in-the-loop approval, and vector database integration for RAG.

Coupling orchestration logic with business logic forces developers to maintain determinism constraints manually — no direct I/O, no system time, no randomness in workflow definitions. Conductor eliminates this entire class of bugs by making the orchestration layer deterministic by construction. Workers are plain code with zero framework constraints — write them in any language, use any library, call any API.

Conductor is an open-source workflow engine with native LLM task types for 14+ providers, built-in MCP integration, durable execution, full replayability, and 7+ language SDKs.

100% compatible. Orkes Conductor is built on top of Conductor OSS with full API and workflow compatibility.

Contributing

We welcome contributions from everyone!

• Report Issues: Open an issue on GitHub.
• Contribute code: Check out our Contribution Guide and good first issues.
• Improve docs: Help keep our documentation great.

Contributors

Roadmap

See the Conductor OSS Roadmap. Want to participate? Reach out.

License

Conductor is licensed under the Apache 2.0 License.