⚙️

Apache Conductor

Orchestrate resilient workflows for automation & workflow

Free ⭐⭐⭐⭐☆ 4.4/5 ⚙️ Automation & Workflow 🕒 Updated
Visit Apache Conductor ↗ Official website
Quick Verdict

Apache Conductor is an open-source workflow orchestration engine for building event-driven and microservice workflows; ideal for engineering teams needing self-hosted, JSON-defined workflows and operational visibility. It is free to deploy (open-source) with managed hosting available from third parties at commercial rates, making it best for teams able to operate their own infrastructure or buy managed support.

Apache Conductor is an open-source orchestration engine that coordinates microservice-based and event-driven workflows in the Automation & Workflow category. It lets engineers define workflow logic as JSON, execute tasks (HTTP, worker, sub-workflow), and track state with a built-in UI and REST API. The primary capability is long-running, versioned workflows across distributed systems; its key differentiator is a task/worker model with pluggable persistence and queue backends. Conductor serves backend engineers, SREs, and integration teams building automation at scale. The core project is free to self-host; managed hosting is available commercially.

About Apache Conductor

Apache Conductor is an open-source workflow orchestration engine originally developed at Netflix to coordinate microservice-based and long-running business processes. Positioned as a developer-first automation & workflow platform, Conductor exposes a REST API and a UI for defining, running, and monitoring workflows. Its core value proposition is explicit control over task execution and retries across distributed services, enabling complex workflows like saga patterns, batch processing, and event-driven state machines without locking you into a cloud vendor. The project is distributed under an Apache license and is commonly self-hosted inside enterprise cloud or on-prem environments.

Conductor’s feature set targets real-world orchestration needs. Workflow definitions are JSON-based and support common task types such as SIMPLE tasks, HTTP tasks, SUB_WORKFLOW, FORK_JOIN, and WAIT_FOR_EVENT; these enable branching, parallelism, and event-driven pauses. The server exposes a full REST API for starting workflows, polling tasks, and querying history, while a web UI provides visibility into workflow instances, task timelines, and execution metadata. Conductor supports pluggable persistence and queue backends (commonly MySQL/Cassandra/Redis with optional Elasticsearch for visibility) and a worker model where language-specific clients (Java, community Python and Go clients) poll and execute tasks, allowing horizontal scaling of workers. Additional features include retry and timeout policies, task priorities, workflow versioning, and sub-workflow composition.

Pricing for Apache Conductor itself is straightforward: the software is free to download and self-host under the Apache license with no usage caps beyond your infrastructure. There are no paid “tiers” in the core project; commercial fees appear only if you purchase a managed hosting or support plan from third-party vendors (for example, companies that offer Conductor as a service). Managed providers typically charge per-host, throughput, or connection and require a custom quote; expect enterprise support contracts for SLAs, onboarding, and managed upgrades. In short, the core product is free with optional commercial managed options priced individually.

Conductor is used by backend engineers and platform teams to automate durable workflows such as order processing, data pipelines, and cross-service transactions. Example users: Platform Engineer using it to reduce cross-service orchestration bugs by replacing ad-hoc scripts, and SRE using it to implement automated incident remediation workflows that reduce mean time to recovery. Conductor competes with systems like Temporal and Apache Airflow; compared with Temporal it emphasizes a JSON task/worker model and pluggable persistence rather than language-native workflow code execution.

What makes Apache Conductor different

Three capabilities that set Apache Conductor apart from its nearest competitors.

  • JSON-first workflow DSL and task/worker polling model separates orchestration concerns from service code.
  • Pluggable persistence lets teams choose MySQL, Cassandra or Redis backends rather than being tied to a single store.
  • Focus on long-running, event-driven workflows and explicit task types (HTTP, SUB_WORKFLOW, WAIT_FOR_EVENT) differentiates operational visibility.

Is Apache Conductor right for you?

✅ Best for
  • Backend engineers who need durable, versioned microservice workflows
  • Platform teams who want self-hosted control and auditability
  • SREs who automate incident remediation and reduce MTTR
  • Enterprises integrating heterogeneous services across on-prem and cloud
❌ Skip it if
  • Skip if you require a fully managed SaaS without third-party contracts.
  • Skip if you need language-native workflow code with single-host stateful execution (Temporal style).

✅ Pros

  • Open-source Apache license — free to download and run with no vendor lock-in
  • Task/worker model allows language-agnostic workers (Java, Python, Go) and horizontal scaling
  • Built-in UI and REST API provide end-to-end visibility and control of workflow state

❌ Cons

  • Requires self-hosting expertise; setup and scaling need operational effort and infra management
  • No official vendor-hosted tier from the Apache project — managed hosting requires third-party contracts

Apache Conductor Pricing Plans

Current tiers and what you get at each price point. Verified against the vendor's pricing page.

Plan Price What you get Best for
Self-hosted (Open Source) Free No license fees; limits set by your infrastructure and scaling choices Engineering teams who can run their own infrastructure
Managed (third-party) Custom Quota, SLA, and onboarding defined per-contract by provider Companies wanting hosted Conductor with SLA and support

Best Use Cases

  • Platform Engineer using it to reduce orchestration errors by replacing ad-hoc scripts with versioned workflows
  • SRE using it to automate incident remediation and cut mean time to recovery by measurable minutes
  • Data Engineer using it to coordinate ETL pipelines and ensure retryable, auditable job executions

Integrations

Redis Elasticsearch Kafka

How to Use Apache Conductor

  1. 1
    Download and run the Server
    Clone the Conductor repo or download the release and run the server via docker-compose (see docs/docker-compose.yml). Start server and UI, then verify http://localhost:8080 responds to confirm the server and UI are running.
  2. 2
    Import or define a workflow JSON
    Open the Conductor UI, go to 'Metadata' → 'Workflows' → 'Create' or 'Import' and paste a JSON workflow definition. Save; success looks like the workflow appearing in the list with a version number.
  3. 3
    Start a workflow instance via API
    Use the REST endpoint POST /api/workflow to start a workflow (or click 'Start' in UI). Provide input JSON; a returned workflowId and status RUNNING indicates success.
  4. 4
    Run a worker and monitor progress
    Run an example worker (Java/Python client) that polls tasks of your taskType. In the UI check 'Workflow Instances' to see task timelines; completed tasks show status COMPLETED and final workflow status SUCCESS.

Apache Conductor vs Alternatives

Bottom line

Choose Apache Conductor over Temporal if you prefer a JSON task/worker orchestration model with pluggable persistence and language-agnostic workers.

Frequently Asked Questions

How much does Apache Conductor cost?+
Free and open-source: self-host Apache Conductor now. The core project is available under the Apache license with no software license fees; costs come from your infrastructure, operations, and optional third-party managed hosting which is priced separately by vendors.
Is there a free version of Apache Conductor?+
Yes — Apache Conductor is free to self-host under Apache license. The full server, API, and UI are provided as open-source. If you want hosted Conductor with SLAs or enterprise support you must purchase a managed plan from a third-party provider.
How does Apache Conductor compare to Temporal?+
Conductor uses a JSON task/worker model rather than Temporal’s language-native workflow code. Conductor is language-agnostic with pluggable persistence; Temporal targets language SDKs and built-in durable state management with different operational trade-offs.
What is Apache Conductor best used for?+
Orchestrating long-running, event-driven microservice workflows across distributed systems. Conductor excels at saga-style transactions, ETL pipelines, and cross-service automation requiring retries, versioning, and operational visibility.
How do I get started with Apache Conductor?+
Run the official docker-compose from the Conductor docs to start server and UI locally. Then import a sample workflow via 'Metadata → Workflows → Import', start it via the UI or POST /api/workflow, and run a worker client to execute tasks.

More Automation & Workflow Tools

Browse all Automation & Workflow tools →
⚙️
Microsoft Power Automate
Automate workflows and tasks across apps and systems
Updated Apr 21, 2026
⚙️
UiPath
Automate enterprise workflows with scalable automation and orchestration
Updated Apr 21, 2026
⚙️
Make
Automate workflows and integrations for scalable operations
Updated Apr 22, 2026