Changedetection.io is the honest answer when someone asks how to watch a page for free. Spin up Docker, point it at a URL, get a diff when the HTML moves. It works. I have used it.
The part nobody puts on the README is the second job that comes with it. The VPS invoice. The compose file that breaks after an update. The watcher that was "temporarily" down for a week while you shipped something else. The change still happened. You just did not get the ping.
Self-host is a product. Watching a URL is a chore.
If you like running infra, Changedetection is great. You own the data. You tune the poll interval. You wire webhooks however you want.
Most teams who say they want "website change detection" do not want another service to keep alive. They want one concrete outcome: when this pricing page, ToS, or careers page changes, tell me before a customer does.
Screenshot tools like Visualping catch pixel noise. Selector tools like Distill need CSS babysitting. Google Alerts watches articles, not the URL you quote from. Self-hosted Changedetection sits in the middle and still asks you to be the on-call.
Paste the URL. Get the alert. Skip the server.
What I use now is simpler. Paste the exact page that would change a decision. Ask for an alert when the text on that page changes. Open the diff. Decide if it matters.
I use AyeWatch for that. Free Preview is $0 with 3 topics and 6 lifetime runs. Pro is $9 a month.
No Docker. No CSS selectors. No screenshot false alarms from a cookie banner. Just the page I already cared about, watched on a schedule I do not have to maintain.
When Changedetection is still the right call
Keep Changedetection (or any self-hosted watcher) if you need full control, air-gapped polling, or a custom pipeline into your own stack. That is a real product need.
If your actual goal is "tell me when this public URL changes," skip the second job. Watch the page. Let the alert be the only thing you operate.
Top comments (0)