conductor
★ 32.4k
vs
leather
★ 17
conductor vs leather
conductor: Conductor is an open-source, scalable microservices orchestration engine originally built at Netflix. It empowers developers to define and manage resilient, distributed, and asynchronous workflows across various services and systems.; leather: Leather provides a local agent infrastructure in a single Go binary, enabling declarative agents to run scheduled jobs, webhook-driven workflows, and tool calling without a Python stack or external dependencies. It includes features like multi-stage agent routing, queues, and developer tools for comprehensive LLM-powered workflow automation.
01
TL;DR
conductorWorkflow Automation · ★ 32.4k
When to choose:
- You want an Apache-2.0 durable workflow engine where workflows are defined as JSON graphs and workers can be written in any language.
- You want built-in LLM task types, MCP tool calling, human approval steps, and vector workflows on top of a microservice orchestrator.
When to skip:
- You prefer writing workflows purely as code rather than JSON graph definitions; Temporal or AutoKitteh fit better.
- You want a lightweight embedded rule engine inside a single Go binary with zero external middleware; RuleGo is designed for that.
leatherWorkflow Automation · ★ 17
Scheduled Automation: Run agents on a predefined schedule for routine tasks.
02
Side-by-Side Comparison
Field
conductorleatherCategory
Workflow Automation
Workflow Automation
Stars
★ 32.4k
★ 17
License
Apache-2.0
GPL-3.0
Install Command
npm install -g @conductor-oss/conductor-cli
go install github.com/TGPSKI/leather/cmd/leather@latest && go install github.com/TGPSKI/leather/cmd/shell-mcp@latest
Updated
1d ago
1mo ago
Open Source
Yes
Yes
Tags
Microservices Orchestration, Workflow Engine, Distributed Systems
Go, LLM Agents, Workflow Automation
03
Features
conductor01Workflow as code with JSON definition
02Rich task types (HTTP, JSON, Lambda, Sub Workflow, Event)
03Dynamic workflow management independent of services
04Built-in UI for monitoring and management
05Flexible persistence and queue options (Redis, MySQL, Postgres)
leather01Agent Definition: Define agents using Markdown with system prompts and variable support.
02Tool Calling: Integrate shell commands and other skills as agent tools.
03Multi-Agent Curing: Bind agents to queues for flexible multi-stage routing and complex workflows.
04Persistent Queues: Utilize filesystem FIFO queues with configurable depth, backpressure, and concurrency.
05Developer UI (DevTools): A web-based UI with session timeline, event inspector, and live updates for monitoring workflows.
04
Use Cases
conductor↳Orchestrating complex microservice interactions
↳Automating event-driven business processes
↳Building resilient and observable distributed systems
leather↳Scheduled Automation: Run agents on a predefined schedule for routine tasks.
↳Event-Driven Workflows: Trigger agent runs via webhooks for reactive automation.
↳Multi-Agent Pipelines: Orchestrate multiple agents into complex, multi-stage processing pipelines.
↳Local LLM Integration: Integrate local LLM endpoints (e.g., Ollama) for privacy-preserving AI tasks.
↳DevTools for Monitoring: Visualize and debug agent execution and workflow events in real-time.
05
Best For
conductorMost PopularEssentialTrending
leather—
FAQ
FAQ
What is the difference between conductor and leather?
Both conductor and leather are in the Workflow Automation category. conductor has 32.4k stars, while leather has 17 stars.
Which is better, conductor or leather?
The best choice depends on your use case. Choose conductor if Orchestrating complex microservice interactions, and leather if Scheduled Automation: Run agents on a predefined schedule for routine tasks..
Is conductor free or open source?
Yes, conductor is open source on GitHub (Apache-2.0).
Is leather free or open source?
Yes, leather is open source on GitHub (GPL-3.0).
Cloud Infrastructure
AdDeploy on DigitalOcean
Host your MCP servers, Docker containers, and AI agents with $200 free credit over 60 days.
→