Apache 2.0 Licensed · Originally created at Netflix

Code breaks. Infrastructure fails.
Your workflows don't.

Crash-proof workflows and AI agents that finish what they start — powered by durable execution at Netflix scale.

No SDK restrictions. No non-determinism bugs. No cloud lock-in.

Get Started→ conductor-oss/conductor

$ npm install -g @conductor-oss/conductor-cli

Build with AI Agents

Conductor Skills → Install Conductor Skills for your AI Agent

AI Cookbook → 14+ LLM providers, MCP tool calling, human-in-the-loop, and durable agent execution.

Guaranteed at-least-once

Task Delivery

Any language

Worker Support

Millions

Concurrent Workflows

Billions of workflows

Internet Scale Execution

Trusted by engineering teams at

Netflix Tesla LinkedIn JP Morgan Freshworks American Express Redfin VMware Coupang Swiggy Netflix Tesla LinkedIn JP Morgan Freshworks American Express Redfin VMware Coupang Swiggy

Built for workflows that can't afford to fail.

Core

Durable execution by default

Workflow state is persisted at every step. Survive server restarts, worker crashes, and network failures. Durable execution with at-least-once task delivery, configurable retries, timeouts, and compensation flows. Build durable agents that never lose progress.

Failure semantics →

JSON superpower

JSON native — deterministic by default

JSON definitions separate orchestration from implementation — no side effects, no hidden state, every run is deterministic. Generate workflows at runtime with LLMs, modify per-execution, and use dynamic forks, dynamic tasks, and dynamic sub-workflows for more flexibility than code-based engines. Code via SDKs when you need it.

Why JSON wins →

Primitives

Replay, Restart, Pause, Resume

Pause workflows on time, external signals, webhooks, or human approval. Resume safely after minutes, hours, or days. Replay any workflow from the beginning, from a specific task, or retry just the failed step — even months later. Full execution history is always preserved.

How it works →

AI agent orchestration & LLM orchestration

Orchestrate AI agents with 14+ native LLM providers (Anthropic, OpenAI, Gemini, Bedrock, Mistral, and more), MCP tool calling, function calling, human-in-the-loop approval, and structured output. Built-in vector database support (Pinecone, pgvector, MongoDB Atlas) for RAG pipelines.

AI Cookbook →

Workers

Polyglot workers

Write task workers in any language. Workers poll for tasks, execute your logic, and report results—run them anywhere.

Reliability

Saga pattern & compensation

Model distributed transactions as sagas. When a step fails, Conductor automatically runs undo logic in reverse order—no manual intervention.

Error handling →

Understand the engine.

Durable Execution

What persists, what gets retried, failure matrix, and state transitions.

AI Cookbook

LLM tasks, tool calls, human approval, dynamic workflows, MCP tools.

JSON + Code Native

Runtime generation, versioning, dynamic definitions, API/SDK parity.

System Architecture

Worker-task queues, persistence, polling, distributed consistency.

Frequently asked questions.

How do I run Conductor with Docker?

Run docker run -p 8080:8080 conductoross/conductor:latest to start Conductor with all dependencies included. The server will be available at http://localhost:8080. For production deployments with external persistence, see the Docker deployment guide.

Is Conductor open source?

Yes. Conductor is a fully open source workflow engine, Apache 2.0 licensed. You can self-host it on your own infrastructure with no vendor lock-in. It supports 5 persistence backends, 6 message brokers, and runs anywhere Docker runs.

Is this the same as Netflix Conductor?

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

Is this project actively maintained?

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

Can Conductor scale to handle my workload?

Conductor was built at Netflix to handle massive scale and has been battle-tested in production environments processing millions of workflows. It scales horizontally to meet virtually any demand.

Does Conductor support durable execution?

Yes. Conductor pioneered durable execution patterns, ensuring workflows and durable agents complete reliably even in the face of infrastructure failures, process crashes, or network issues.

Can I replay a workflow after it completes or fails?

Yes. Conductor preserves full execution history indefinitely. You can restart from the beginning, rerun from any specific task, or retry just the failed step — even months later. Use the API (/restart, /rerun, /retry) or the UI.

Are workflows always asynchronous?

No. While Conductor excels at asynchronous orchestration, it also supports synchronous workflow execution when immediate results are required.

Do I need to use a Conductor-specific framework?

No. Conductor is language and framework agnostic. Use your preferred language and framework—SDKs provide native integration for Java, Python, JavaScript, Go, C#, and more.

Isn't JSON too limited for complex workflows?

The opposite. JSON separates orchestration from implementation, making every workflow deterministic by construction — no side effects, no hidden state. Dynamic forks, dynamic tasks, and dynamic sub-workflows let you build workflows that are more flexible than code-based engines. JSON is also AI-native: LLMs can generate and modify workflow definitions at runtime without a compile/deploy cycle. Code-based engines require redeployment for every change.

Is Conductor a low-code/no-code platform?

No. Conductor is designed for developers who write code. While workflows can be defined in JSON, the power comes from building workers and tasks in your preferred programming language.

Can Conductor handle complex workflows?

Conductor was specifically designed for complex orchestration. It supports advanced patterns including nested loops, dynamic branching, sub-workflows, and workflows with thousands of tasks.

Is Netflix Conductor abandoned?

No. The original Netflix repository has transitioned to Conductor OSS, which is the new home for the project. Active development and maintenance continues here.

Is Orkes Conductor compatible with Conductor OSS?

100% compatible. Orkes Conductor is built on top of Conductor OSS, ensuring full compatibility between the open-source version and the enterprise offering.

Can Conductor orchestrate AI agents and LLMs?

Yes. Conductor provides AI agent orchestration and LLM orchestration as native capabilities. 14+ LLM providers (Anthropic, OpenAI, Azure OpenAI, Google Gemini, AWS Bedrock, Mistral, Cohere, HuggingFace, Ollama, and more), MCP tool calling and function calling (LIST_MCP_TOOLS, CALL_MCP_TOOL), vector database integration (Pinecone, pgvector, MongoDB Atlas) for RAG, and content generation (image, audio, video, PDF). All with the same durability guarantees as any other workflow task.

How does Conductor compare to other workflow engines?

Conductor is the only open source workflow engine with native LLM task types for 14+ providers, built-in MCP integration, and vector database support. Combined with durable execution, 7+ language SDKs (Java, Python, Go, JavaScript, C#, Ruby, Rust), 6 message brokers, 5 persistence backends, and battle-tested scale at Netflix, Tesla, LinkedIn, and JP Morgan, Conductor provides the most complete workflow orchestration platform available. Unlike Temporal, Step Functions, or Airflow, Conductor is fully self-hosted, supports both code-first and JSON workflow definitions, and provides native AI agent orchestration out of the box.