changedetection.io vs Conductor (Netflix)
| Tagline | Monitor any website for changes and get notified instantly | Microservice workflow orchestration engine open-sourced by Netflix |
| Category | Automation & iPaaS | Automation & iPaaS |
| Replaces | Zapier, Make | Zapier, Workato |
| GitHub stars | 33k | 32k |
| Language | Python | Java |
| License | Apache-2.0 | Apache-2.0 |
| Self-host difficulty | 2/5 Easy | 4/5 Involved |
| Deploy options | Docker Docker Compose Manual | Docker Docker Compose Kubernetes Manual |
| Managed hosting | ||
| Last updated | 6 days ago | 6 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.
changedetection.io
- No multi-step workflow automation — it only watches and notifies, not acts on changes
- JavaScript-heavy sites require a separately configured Playwright browser container
- No native API for programmatic watch management (REST API is limited)
- Cannot extract and transform data into downstream systems without additional tools
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
Bottom line
Choose changedetection.io if you want the lower-effort setup; choose changedetection.io for the larger community and ecosystem. Open each guide below for deploy steps and the full feature gap.
Conductor (Netflix)
Microservice workflow orchestration engine open-sourced by Netflix