Conductor (Netflix) vs Leon
| Tagline | Microservice workflow orchestration engine open-sourced by Netflix | Open-source personal assistant server you fully control and run on your own machine |
| Category | Automation & iPaaS | Automation & iPaaS |
| Replaces | Zapier, Workato | Zapier, Make |
| GitHub stars | 32k | 17k |
| Language | Java | Nodejs |
| License | Apache-2.0 | MIT |
| Self-host difficulty | 4/5 Involved | 4/5 Involved |
| Deploy options | Docker Docker Compose Kubernetes Manual | Manual |
| Managed hosting | ||
| Last updated | 8 days ago | 5 days ago |
| View repo | View repo |
Where each falls short
The honest trade-offs — what you give up with each, versus the proprietary tools they replace.
Conductor (Netflix)
- Workflow logic defined in JSON/YAML; no drag-and-drop canvas for non-technical users
- Requires Elasticsearch and a relational DB for production — non-trivial infrastructure
- Community edition lacks built-in RBAC available in the commercial Orkes Cloud offering
Leon
- Skill catalog is far smaller than Alexa's or Google Assistant's third-party ecosystem
- No official Docker image; setup involves Node.js, Python, and optional model downloads
- Voice accuracy depends on local NLU models that require additional setup and tuning
- Not designed for multi-user household scenarios — user accounts and permissions are limited
Bottom line
Both are a similar lift to self-host; choose Conductor (Netflix) for the larger community and ecosystem. Leon has seen more recent development. Open each guide below for deploy steps and the full feature gap.
Conductor (Netflix)
Microservice workflow orchestration engine open-sourced by Netflix
Leon
Open-source personal assistant server you fully control and run on your own machine