Orchestrate resilient workflows for automation & workflow
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.
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.
Three capabilities that set Apache Conductor apart from its nearest competitors.
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 |
Choose Apache Conductor over Temporal if you prefer a JSON task/worker orchestration model with pluggable persistence and language-agnostic workers.