changedetection.io vs Dittofeed
| Tagline | Monitor any website for changes and get notified instantly | Open-source customer messaging automation — email, SMS, and push journey builder |
| Category | Automation & iPaaS | Automation & iPaaS |
| Replaces | Zapier, Make | Zapier, Make, Workato |
| GitHub stars | 32k | 2.8k |
| Language | Python | Docker |
| License | Apache-2.0 | MIT |
| Self-host difficulty | 2/5 Easy | 3/5 Moderate |
| Deploy options | Docker Docker Compose Manual | Docker Docker Compose |
| Managed hosting | ||
| Last updated | today | 2 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.
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
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 changedetection.io if you want the lower-effort setup; choose changedetection.io for the larger community and ecosystem. changedetection.io has seen more recent development. Open each guide below for deploy steps and the full feature gap.
Dittofeed
Open-source customer messaging automation — email, SMS, and push journey builder