Conductor (Netflix) vs Dittofeed
| Tagline | Microservice workflow orchestration engine open-sourced by Netflix | Open-source customer messaging automation — email, SMS, and push journey builder |
| Category | Automation & iPaaS | Automation & iPaaS |
| Replaces | Zapier, Workato | Zapier, Make, Workato |
| GitHub stars | 32k | 2.9k |
| Language | Java | Docker |
| License | Apache-2.0 | MIT |
| Self-host difficulty | 4/5 Involved | 3/5 Moderate |
| Deploy options | Docker Docker Compose Kubernetes Manual | Docker Docker Compose |
| Managed hosting | ||
| Last updated | 7 days ago | 4 months 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
Dittofeed
- In-app messaging channel (tooltips, banners, modals) is not yet supported
- Deliverability tools like dedicated IP warm-up and domain authentication wizards are absent
- Mobile push requires manual integration with APNs/FCM; no managed SDK
- Feature cadence for the self-hosted version can lag behind the cloud offering
Bottom line
Choose Dittofeed if you want the lower-effort setup; choose Conductor (Netflix) for the larger community and ecosystem. Conductor (Netflix) 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
Dittofeed
Open-source customer messaging automation — email, SMS, and push journey builder