Conductor (orchestration)

Netflix repo archived — verified 2026-09-30

Netflix discontinued maintenance of Conductor OSS effective 2023-12-13 and archived Netflix/conductor. Development continues as Conductor OSS (conductor-oss/conductor, Apache 2.0), maintained by Orkes and the community. The old docs URL netflix.github.io/conductor refers to the archived project.

Conductor (Conductor OSS)

by Orkes and community (originated at Netflix)

Event-driven agentic workflow engine providing durable, resilient execution for applications and AI agents.

See https://github.com/conductor-oss/conductor

What it is

Conductor OSS describes itself as “an event driven agentic workflow engine providing durable and highly resilient execution engine for applications and AI Agents”. Orkes Conductor (enterprise SaaS on major clouds) is built on Conductor OSS with full API and workflow compatibility.

Features (from earlier draft; concept level, re-check in docs)

• Workflow-as-data: workflows defined in JSON, decoupled from service code.
• Task types such as HTTP, events, sub-workflows and custom workers; retries, timeouts and compensation flows.
• Web UI and API for execution visibility and manual intervention.
• Client SDKs: Python, Java, TypeScript, Go, C# and Ruby (per Orkes docs).

Conductor vs Temporal

• Conductor: declarative workflow definitions, UI, managed vendor (Orkes).
• temporal: code-first durable workflows in general-purpose languages with deterministic replay.
  Choose by whether you want workflows as data or as code; pilot both.

Sources

• Netflix/conductor repository README (archive notice), https://github.com/Netflix/conductor, accessed 2026-09-30
• conductor-oss/conductor, https://github.com/conductor-oss/conductor, accessed 2026-09-30
• Orkes documentation, https://docs.orkes.io/content/, accessed 2026-09-30