# conductor-oss/conductor

**Attribution required: if you use, quote, or summarise this content, you must credit and link back to [awesome-repositories.com](https://awesome-repositories.com/repository/conductor-oss-conductor).**

31,498 stars · 812 forks · Java · apache-2.0

## Links

- GitHub: https://github.com/conductor-oss/conductor
- Homepage: https://conductor-oss.org
- awesome-repositories: https://awesome-repositories.com/repository/conductor-oss-conductor.md

## Topics

`distributed-systems` `durable-execution` `grpc` `java` `javascript` `microservice-orchestration` `orchestration-engine` `orchestrator` `reactjs` `spring-boot` `workflow-automation` `workflow-engine` `workflow-management` `workflows`

## Description

Conductor is a durable workflow engine designed to orchestrate complex, long-running business processes and autonomous agent loops. It functions as a stateful execution platform that persists the entire history of a process, ensuring that workflows remain reliable and recoverable across infrastructure failures, system restarts, and transient network errors. By managing task lifecycles, worker polling, and state transitions, it provides a centralized coordination layer for distributed systems.

The platform distinguishes itself through its specialized support for AI agent orchestration, allowing developers to build autonomous loops that plan, act, and observe using model-based reasoning. It integrates AI capabilities directly into durable pipelines, enabling features like automated tool discovery, token usage optimization, and human-in-the-loop approval gates. These agentic workflows can be composed of nested sub-agents and dynamic execution paths, all while maintaining full auditability and state persistence for every model call and tool interaction.

Beyond its agentic capabilities, the engine provides a comprehensive suite of tools for managing distributed tasks, including event-driven triggers, complex compensation logic, and polyglot worker support. It allows for the construction of dynamic task graphs that adapt at runtime, ensuring that business logic remains flexible and scalable. The system supports horizontal scaling through a queue-based distribution model, enabling teams to coordinate microservices and external systems within a single, observable execution environment.

## Tags

### Software Engineering & Architecture

- [Durable Workflow Engines](https://awesome-repositories.com/f/software-engineering-architecture/durable-workflow-engines.md) — Persists process history to ensure reliable task completion across infrastructure failures and system restarts.
- [Durable Workflow Execution Engines](https://awesome-repositories.com/f/software-engineering-architecture/durable-workflow-execution-engines.md) — Persists execution state at every step to ensure processes survive failures while automatically handling retries and compensation. ([source](https://docs.conductor-oss.org/index.html))
- [Durable Workflow Orchestrators](https://awesome-repositories.com/f/software-engineering-architecture/durable-workflow-orchestrators.md) — Builds reliable, long-running business processes that automatically recover from infrastructure failures and transient service errors.
- [Workflow Engines](https://awesome-repositories.com/f/software-engineering-architecture/workflow-engines.md) — Provides a core engine for executing background tasks across multiple programming languages. ([source](https://docs.conductor-oss.org/index.html))
- [Workflow Orchestration](https://awesome-repositories.com/f/software-engineering-architecture/workflow-orchestration.md) — Manages the full lifecycle of tasks including scheduling, execution, and error handling within durable workflows. ([source](https://docs.conductor-oss.org/architecture/durable-execution.html))
- [Durable Execution Persistence](https://awesome-repositories.com/f/software-engineering-architecture/durable-execution-persistence.md) — Saves the state of every workflow and task to storage, ensuring progress is recoverable after system crashes or infrastructure failures.
- [Workflow Compensation Systems](https://awesome-repositories.com/f/software-engineering-architecture/workflow-compensation-systems.md) — Implements automated rollback and cleanup logic to handle failure scenarios within durable workflow executions. ([source](https://docs.conductor-oss.org/devguide/how-tos/Workflows/handling-errors.html))
- [Workflow Orchestration Engines](https://awesome-repositories.com/f/software-engineering-architecture/workflow-orchestration-engines.md) — Durable workflow engines run workflows generated at runtime by passing definitions directly to the engine, ensuring every generated step remains durable, observable, and retryable. ([source](https://docs.conductor-oss.org/architecture/json-native.html))
- [Workflow Persistence Engines](https://awesome-repositories.com/f/software-engineering-architecture/workflow-persistence-engines.md) — Durable workflow engines save workflow and task execution state to a database at every step to ensure progress is never lost during infrastructure failures or server restarts. ([source](https://docs.conductor-oss.org/architecture/durable-execution.html))
- [State Machine Orchestrators](https://awesome-repositories.com/f/software-engineering-architecture/state-machine-orchestrators.md) — Executes complex business logic by transitioning through defined states while persisting the entire execution history.
- [Workflow Blueprints](https://awesome-repositories.com/f/software-engineering-architecture/workflow-blueprints.md) — Durable workflow engines specify task sequences, input parameters, and runtime policies like timeouts and compensation flows to create durable business logic blueprints. ([source](https://docs.conductor-oss.org/devguide/concepts/workflows.html))
- [Workflow Versioning](https://awesome-repositories.com/f/software-engineering-architecture/workflow-versioning.md) — Durable workflow engines maintain execution consistency by using immutable snapshots of definitions, ensuring active workflows complete with original logic while new executions adopt updated versions. ([source](https://docs.conductor-oss.org/devguide/ai/failure-semantics.html))
- [Distributed Transaction Managers](https://awesome-repositories.com/f/software-engineering-architecture/distributed-transaction-managers.md) — Models complex operations as sagas that automatically execute undo logic in reverse order when a step fails. ([source](https://docs.conductor-oss.org/index.html))
- [Event-Driven Architectures](https://awesome-repositories.com/f/software-engineering-architecture/event-driven-architectures.md) — Durable workflow engines register event handlers that automatically trigger the execution of specific workflows when messages arrive on configured queues or topics from external systems. ([source](https://docs.conductor-oss.org/devguide/cookbook/event-driven.html))
- [Missed Execution Handlers](https://awesome-repositories.com/f/software-engineering-architecture/missed-execution-handlers.md) — Durable workflow engines trigger all missed workflow executions automatically upon system restart to ensure data consistency for critical processes like billing or data processing. ([source](https://docs.conductor-oss.org/devguide/cookbook/workflow-scheduling.html))
- [Retry Strategies](https://awesome-repositories.com/f/software-engineering-architecture/retry-strategies.md) — Durable workflow engines manage transient failures by defining task retry behavior using fixed, linear, or exponential backoff strategies to reduce load on downstream services. ([source](https://docs.conductor-oss.org/devguide/how-tos/Workflows/handling-errors.html))
- [Workflow Monitoring](https://awesome-repositories.com/f/software-engineering-architecture/workflow-monitoring.md) — Durable workflow engines track the lifecycle of workflow instances as they transition through states like running, completed, failed, or paused during their execution. ([source](https://docs.conductor-oss.org/devguide/concepts/workflows.html))
- [Workflow Task Definitions](https://awesome-repositories.com/f/software-engineering-architecture/workflow-task-definitions.md) — Durable workflow engines create or update task definitions through the visual interface, command-line tools, or APIs to maintain consistent workflow logic. ([source](https://docs.conductor-oss.org/devguide/how-tos/Tasks/creating-tasks.html))
- [Concurrent Execution Managers](https://awesome-repositories.com/f/software-engineering-architecture/concurrent-execution-managers.md) — Durable workflow engines design workflows to handle concurrent executions by ensuring idempotency or adjusting intervals when workflow duration exceeds the frequency of the scheduled trigger. ([source](https://docs.conductor-oss.org/devguide/cookbook/workflow-scheduling.html))
- [Dynamic Task Graphs](https://awesome-repositories.com/f/software-engineering-architecture/dynamic-task-graphs.md) — Constructs and modifies execution paths at runtime based on previous outputs, enabling flexible branching and parallel processing.
- [Failure Handling Policies](https://awesome-repositories.com/f/software-engineering-architecture/failure-handling-policies.md) — Durable workflow engines manage task-level failures by marking steps as optional, signaling terminal errors to bypass retries, or setting specific timeouts to prevent blocking workflow execution. ([source](https://docs.conductor-oss.org/devguide/how-tos/Workflows/handling-errors.html))
- [Microservices Process Coordinators](https://awesome-repositories.com/f/software-engineering-architecture/microservices-process-coordinators.md) — Chains multiple service calls and parallel operations into a single, observable, and versioned execution pipeline.
- [Reliable Task Queues](https://awesome-repositories.com/f/software-engineering-architecture/reliable-task-queues.md) — Durable workflow engines ensure at-least-once task delivery by automatically redelivering tasks if a worker fails to report completion within the configured response timeout period. ([source](https://docs.conductor-oss.org/architecture/durable-execution.html))
- [Retry Policies](https://awesome-repositories.com/f/software-engineering-architecture/retry-policies.md) — Durable workflow engines set task-level durability settings including retry policies, backoff strategies, and timeout thresholds to handle transient failures and long-running operations. ([source](https://docs.conductor-oss.org/architecture/durable-execution.html))
- [Task Templates](https://awesome-repositories.com/f/software-engineering-architecture/task-templates.md) — Durable workflow engines create reusable task configurations including retry policies, timeout limits, and input parameters to standardize behavior across multiple workflow definitions. ([source](https://docs.conductor-oss.org/devguide/concepts/tasks.html))
- [Timeout Policies](https://awesome-repositories.com/f/software-engineering-architecture/timeout-policies.md) — Durable workflow engines determine whether a task should be retried, trigger a workflow failure, or log an alert when execution limits are exceeded. ([source](https://docs.conductor-oss.org/devguide/how-tos/Workflows/handling-errors.html))
- [Idempotency Mechanisms](https://awesome-repositories.com/f/software-engineering-architecture/idempotency-mechanisms.md) — Durable workflow engines reject duplicate task completion callbacks automatically to prevent redundant state transitions or multiple workflow advancements for the same task. ([source](https://docs.conductor-oss.org/devguide/ai/failure-semantics.html))
- [Idempotency Patterns](https://awesome-repositories.com/f/software-engineering-architecture/idempotency-patterns.md) — Ensures reliable operations by requiring workers to handle duplicate task identifiers, preventing redundant side effects.

### Artificial Intelligence & ML

- [Agent State Persistence](https://awesome-repositories.com/f/artificial-intelligence-ml/agent-state-persistence.md) — Saves the entire execution state of an agent to ensure reliability across system restarts and failures. ([source](https://docs.conductor-oss.org/devguide/ai/durable-agents.html))
- [AI Agent Orchestration Frameworks](https://awesome-repositories.com/f/artificial-intelligence-ml/ai-agent-orchestration-frameworks.md) — Provides a specialized runtime for managing autonomous agent loops, tool discovery, and model-based reasoning.
- [Durable AI Agent Orchestration](https://awesome-repositories.com/f/artificial-intelligence-ml/durable-ai-agent-orchestration.md) — Maps agent concerns like planning and memory management to durable workflow primitives for reliable execution. ([source](https://docs.conductor-oss.org/devguide/ai/production-agent-architecture.html))
- [AI Agent Orchestrators](https://awesome-repositories.com/f/artificial-intelligence-ml/ai-agent-orchestrators.md) — Connects language model providers with external tools and human approval steps to build automated intelligent pipelines. ([source](https://docs.conductor-oss.org/index.html))
- [AI Workflow Orchestration](https://awesome-repositories.com/f/artificial-intelligence-ml/ai-workflow-orchestration.md) — Integrates model inference and tool calling into workflows to connect AI capabilities with business logic. ([source](https://docs.conductor-oss.org/devguide/concepts/tasks.html))
- [Autonomous Agent Loops](https://awesome-repositories.com/f/artificial-intelligence-ml/autonomous-agent-loops.md) — Combines reasoning tasks with conditional execution logic to repeatedly plan, act, and observe until completion. ([source](https://docs.conductor-oss.org/devguide/ai/dynamic-workflows.html))
- [Agent Failure Mitigation](https://awesome-repositories.com/f/artificial-intelligence-ml/agent-failure-mitigation.md) — Executes automated compensation workflows and retry policies to resolve errors during complex agentic operations. ([source](https://docs.conductor-oss.org/devguide/ai/durable-agents.html))
- [Human Approval Gates](https://awesome-repositories.com/f/artificial-intelligence-ml/human-approval-gates.md) — Requires human approval before executing actions to prevent unauthorized real-world consequences. ([source](https://docs.conductor-oss.org/devguide/ai/human-in-the-loop.html))
- [Multi-Agent System Composition](https://awesome-repositories.com/f/artificial-intelligence-ml/multi-agent-system-composition.md) — Nests sub-agents within parallel structures to delegate specialized tasks and synthesize results. ([source](https://docs.conductor-oss.org/devguide/ai/durable-agents.html))
- [Agentic Tool Orchestration](https://awesome-repositories.com/f/artificial-intelligence-ml/agentic-tool-orchestration.md) — Manages tool discovery, planning, and task execution through standardized interfaces for agentic operations. ([source](https://docs.conductor-oss.org/devguide/ai/dynamic-workflows.html))
- [Autonomous Agent Creation](https://awesome-repositories.com/f/artificial-intelligence-ml/autonomous-agent-creation.md) — Builds autonomous agent loops using conditional logic to repeatedly think, act, and evaluate progress. ([source](https://docs.conductor-oss.org/devguide/ai/first-ai-agent.html))
- [Human Approval](https://awesome-repositories.com/f/artificial-intelligence-ml/human-approval.md) — Inserts human-in-the-loop tasks into workflows to pause execution until a user approves planned actions. ([source](https://docs.conductor-oss.org/devguide/ai/first-ai-agent.html))
- [Workflow-as-a-Tool Exposure](https://awesome-repositories.com/f/artificial-intelligence-ml/workflow-as-a-tool-exposure.md) — Exposes existing workflows as tools through a gateway, allowing external agents to discover and invoke them. ([source](https://docs.conductor-oss.org/devguide/ai/mcp-guide.html))
- [Automated Output Evaluation](https://awesome-repositories.com/f/artificial-intelligence-ml/automated-output-evaluation.md) — Automates quality and safety checks by using a secondary model to judge outputs. ([source](https://docs.conductor-oss.org/devguide/ai/human-in-the-loop.html))
- [External Tool Execution](https://awesome-repositories.com/f/artificial-intelligence-ml/external-tool-execution.md) — Runs tools on external servers with durable execution and automatic retries to ensure reliability. ([source](https://docs.conductor-oss.org/devguide/ai/mcp-guide.html))
- [Human Interaction Management](https://awesome-repositories.com/f/artificial-intelligence-ml/human-interaction-management.md) — Handles long-running human interaction tasks by configuring explicit timeouts and escalation patterns. ([source](https://docs.conductor-oss.org/devguide/ai/failure-semantics.html))
- [Model Task Retries](https://awesome-repositories.com/f/artificial-intelligence-ml/model-task-retries.md) — Retries failed model tasks automatically using configurable backoff strategies while preserving workflow state. ([source](https://docs.conductor-oss.org/devguide/ai/failure-semantics.html))
- [Token Optimization Strategies](https://awesome-repositories.com/f/artificial-intelligence-ml/token-optimization-strategies.md) — Persists model call results to storage to prevent redundant execution and minimize token usage during retries. ([source](https://docs.conductor-oss.org/devguide/ai/token-efficiency.html))
- [AI Agent Workflow Definition](https://awesome-repositories.com/f/artificial-intelligence-ml/ai-agent-workflow-definition.md) — Configures agent workflows using data definitions that orchestrate tool discovery and planning. ([source](https://docs.conductor-oss.org/devguide/ai/first-ai-agent.html))
- [Conditional Result Review](https://awesome-repositories.com/f/artificial-intelligence-ml/conditional-result-review.md) — Triggers human review of tool execution results only when specific conditions are met. ([source](https://docs.conductor-oss.org/devguide/ai/human-in-the-loop.html))
- [External Tool Call Timeouts](https://awesome-repositories.com/f/artificial-intelligence-ml/external-tool-call-timeouts.md) — Configures timeouts for external tool calls to trigger retries while maintaining execution idempotency. ([source](https://docs.conductor-oss.org/devguide/ai/failure-semantics.html))
- [External Tool Discovery](https://awesome-repositories.com/f/artificial-intelligence-ml/external-tool-discovery.md) — Queries external servers at runtime for tool names and parameter schemas to enable dynamic capabilities. ([source](https://docs.conductor-oss.org/devguide/ai/mcp-guide.html))
- [Multimodal Generation Pipelines](https://awesome-repositories.com/f/artificial-intelligence-ml/multimodal-generation-pipelines.md) — Integrates native system tasks to generate and process images, audio, video, and documents within automated execution pipelines. ([source](https://docs.conductor-oss.org/devguide/ai/llm-orchestration.html))

### DevOps & Infrastructure

- [Distributed Task Orchestrators](https://awesome-repositories.com/f/devops-infrastructure/distributed-task-orchestrators.md) — Manages task lifecycles, worker polling, and parallel execution branches across heterogeneous computing environments.
- [Distributed Task Queues](https://awesome-repositories.com/f/devops-infrastructure/distributed-task-queues.md) — Workers retrieve pending tasks from a centralized queue system, enabling horizontal scaling and decoupling of execution logic.
- [System Task Executors](https://awesome-repositories.com/f/devops-infrastructure/system-task-executors.md) — Durable workflow engines run built-in system tasks directly on the server to handle common operations like HTTP requests, event publishing, and inference without writing custom worker code. ([source](https://docs.conductor-oss.org/devguide/concepts/tasks.html))
- [Worker Scaling Strategies](https://awesome-repositories.com/f/devops-infrastructure/worker-scaling-strategies.md) — Durable workflow engines increase worker capacity horizontally by running multiple instances, applying rate limits, and using domain isolation to route tasks to specific worker groups. ([source](https://docs.conductor-oss.org/devguide/concepts/workers.html))
- [Event-Driven Workflow Triggers](https://awesome-repositories.com/f/devops-infrastructure/event-driven-workflow-triggers.md) — Resumes or initiates workflow execution by listening for external signals and messages from integrated message brokers.
- [Task Worker Configurations](https://awesome-repositories.com/f/devops-infrastructure/task-worker-configurations.md) — Durable workflow engines set task execution parameters including retry policies, response timeouts, and concurrency limits to manage how workers process tasks within a workflow. ([source](https://docs.conductor-oss.org/devguide/concepts/workers.html))
- [Event Brokers](https://awesome-repositories.com/f/devops-infrastructure/event-brokers.md) — Durable workflow engines send messages to external message brokers by configuring an event task with a specific destination and input parameters. ([source](https://docs.conductor-oss.org/devguide/cookbook/event-driven.html))
- [Worker Pool Management](https://awesome-repositories.com/f/devops-infrastructure/worker-pool-management.md) — Durable workflow engines adjust worker pool capacity by tuning polling intervals, thread counts, and concurrency limits to route tasks to specific worker environments efficiently. ([source](https://docs.conductor-oss.org/devguide/bestpractices.html))

### Development Tools & Productivity

- [Distributed Task Schedulers](https://awesome-repositories.com/f/development-tools-productivity/distributed-task-schedulers.md) — Automates recurring business operations with precise timing, retry policies, and backoff strategies.
- [Event-Driven Automation Platforms](https://awesome-repositories.com/f/development-tools-productivity/event-driven-automation-platforms.md) — Triggers and resumes complex business processes based on external signals and message bus events.
- [Workflow Schedulers](https://awesome-repositories.com/f/development-tools-productivity/workflow-schedulers.md) — Durable workflow engines define workflow execution schedules using expressions with second-level precision to trigger automated tasks at specific intervals or times. ([source](https://docs.conductor-oss.org/devguide/cookbook/workflow-scheduling.html))
- [Workflow Scheduling Constraints](https://awesome-repositories.com/f/development-tools-productivity/workflow-scheduling-constraints.md) — Durable workflow engines restrict the active period of a workflow schedule by defining specific start and end timestamps to automate the lifecycle of time-bound tasks. ([source](https://docs.conductor-oss.org/devguide/cookbook/workflow-scheduling.html))

### System Administration & Monitoring

- [System Monitoring](https://awesome-repositories.com/f/system-administration-monitoring/system-monitoring.md) — Durable workflow engines track queue sizes and worker activity using the interface or API to detect backlogs and capacity issues in real time. ([source](https://docs.conductor-oss.org/devguide/how-tos/Workers/scaling-workers.html))
- [Execution History Auditors](https://awesome-repositories.com/f/system-administration-monitoring/execution-history-auditors.md) — Durable workflow engines search and retrieve the execution history of scheduled workflows to monitor their status, including timestamps and success or failure states. ([source](https://docs.conductor-oss.org/devguide/how-tos/Workflows/scheduling-workflows.html))

### Web Development

- [Event-Driven Integration Platforms](https://awesome-repositories.com/f/web-development/event-driven-integration-platforms.md) — Connects disparate microservices by triggering workflows from events and coordinating asynchronous task execution.