Polyglot Execution
Keep workers in the stacks you already run
Conductor orchestrates across languages and services instead of forcing workflow logic into a single application runtime
Conductor is maintained in the open. Use the links below to contribute code, ask questions, report issues, or review project policies.
Project resources stay public and versioned in the repository and docs site.
Ship workflow changes without redeploying workers. Write your code in any language — the engine guarantees durability, not your coding discipline.
Conductor orchestrates across languages and services instead of forcing workflow logic into a single application runtime
Start with the core OSS paths: quickstart, self-hosting, recipes, and releases
Run Conductor locally, register a workflow, and execute it end to end.
Deploy Conductor OSS with Docker, shared persistence, and production-ready topology.
Reference patterns for microservices, timers, event-driven workflows, and AI orchestration.
Download tagged releases, review changelogs, and track the project release cadence.
The real advantage is not just durability. It is durable orchestration that can evolve independently, adapt at runtime, span any language boundary, and absorb AI-native workflows without forcing a new stack.
Version, inspect, and change workflow behavior independently of worker implementations. Running executions keep their snapshot while new executions pick up the new path.
Generate workflows on demand, branch with dynamic tasks and forks, and choose sub-workflows per execution without adding a code generation or redeploy step.
LLM tasks, MCP tool discovery and calls, vector workflows, and human approval are first-class engine capabilities on the same durable runtime as service orchestration.
Keep workers in Java, Python, Go, TypeScript, C#, Ruby, Rust, or any service that can call HTTP. Orchestration should not force a single application runtime.
The mechanics behind independent workflow evolution, runtime orchestration, and long-running execution in production
Core documentation, architecture, recipes, and direct answers to the common durability and comparison questions
Architecture, APIs, workflow primitives, operations, and deployment guidance.
Read the project contract for persistence, retries, replay, and recovery behavior.
Use reference recipes for microservices, event-driven patterns, timers, and AI workflows.
Read the reasoning behind independent workflow upgrades, runtime-defined orchestration, native AI primitives, and polyglot workers.
Discuss ideas, contribute in public, and track project activity across the open-source community
Join the public Slack community and GitHub Discussions to ask questions and share patterns.
Join Slack
Follow the repository, browse issues, review releases, and track active development.
Open pull requests, report issues, and review the project security and contribution policies.
Read contributing guide →
