ChangeDetection.io
Open-source website change monitoring with 85+ notification channels. Self-host for free via Docker or use the hosted service. Tracks text changes, visual diffs, JSON APIs, and pages behind logins.
What should journalists know about ChangeDetection.io?
ChangeDetection.io solves a specific, high-value journalism problem: knowing when a web page changes before anyone else notices. Government agencies quietly edit policy pages. Companies update terms of service. Court dockets add new filings. This tool watches them all and alerts you through any of 85+ notification channels (email, Slack, Telegram, webhooks, custom APIs). The self-hosted option is the headline feature for journalists — run it on a $5/month VPS or a Raspberry Pi at home, and your monitoring activity stays entirely under your control. No third party knows which pages you're watching. That's a meaningful privacy advantage for investigative work. The visual selector lets you pinpoint specific page sections to monitor, reducing false positives from layout changes. It handles JavaScript-rendered pages through browser automation and can log into sites before checking for changes. The limitation is that it's a technical tool — Docker deployment requires comfort with the command line, and configuring complex watches (login flows, XPath selectors) takes patience. The hosted SaaS plan at $8.99/month removes the technical overhead but means the service knows which pages you're monitoring. Created by dgtlmoon (pseudonymous developer), actively maintained on GitHub with regular releases. The project has strong community adoption and is well-documented.
Monitoring government websites for policy changes, document additions, or quiet edits. Tracking court dockets, regulatory filings, or corporate disclosure pages. Watching competitor or subject websites for content changes. OSINT research requiring evidence of when pages were modified. Self-hosted deployment where no third party sees your monitoring targets.
Real-time social media monitoring (use CrowdTangle alternatives or Meltwater). Full-text search across the web (this watches specific URLs, not topics). Non-technical journalists who aren't comfortable with Docker or command-line tools (the SaaS option works but has fewer customization options). Monitoring thousands of pages simultaneously without significant server resources.
Security & Privacy
Data is scrambled while being sent to their servers
Data is scrambled when stored on their servers
Where servers are located — affects which governments can request your data
Privacy policy summary
Self-hosted: no data leaves your infrastructure. You control everything — which pages you watch, what changes are logged, where notifications go. Hosted SaaS: the service necessarily knows which URLs you're monitoring and stores page snapshots for diff comparison. Open-source code is fully auditable on GitHub. No advertising model. No user data monetization.
How to protect yourself:
Self-host if your monitoring targets are sensitive — the service seeing which government or corporate pages you're watching is itself a privacy consideration. Use a VPN or Tor exit for the monitoring server if you don't want your IP associated with page requests. Set reasonable check intervals to avoid being rate-limited or blocked. Use the visual selector to reduce false positives from irrelevant page changes. Back up your watch list and configuration regularly.
Open-source (MIT license), fully auditable code, self-hostable with zero third-party data exposure. When self-hosted, this is one of the strongest privacy stories in the journalism tool landscape — no one else knows what you're watching, when pages changed, or what the changes were. The code is actively maintained with regular releases. For the hosted SaaS version, the rating drops to 'adequate' since the service necessarily knows your monitoring targets. Self-hosted deployment is the recommended approach for any sensitive monitoring work.
Who Owns This
Known issues
Self-hosting requires Docker knowledge and ongoing server maintenance. JavaScript-heavy pages need a browser instance (Playwright/Chrome), which increases resource requirements. High-frequency monitoring of many pages can strain modest hardware. The hosted SaaS option means the service knows your monitoring targets — relevant for sensitive investigative work. Pseudonymous maintainer — healthy project community, but single-developer dependency risk. Complex login flows and dynamic pages may require troubleshooting. No native mobile app.
Pricing
Self-hosted: completely free (MIT-licensed, Docker deployment). Hosted SaaS: $8.99/month for unlimited checks and watches, includes one Chrome browser instance for JavaScript-rendered pages. No per-check fees on either tier.
This is an editorial assessment based on publicly available information as of 2026-04-11, using our published methodology. Independent security review is pending. Security posture can change at any time. This is not a guarantee of safety.
Something wrong or outdated? Report it.