Changedetection.io

Changedetection.io is a self-hosted web application that monitors websites for content changes, including text, prices, stock, and errors, and sends alerts…

  • Automation
  • Communication
  • Home Automation
  • Monitoring & Logging
  • Network Services
  • Other
Changedetection.io is a self-hosted web application that monitors websites for content changes, including text, prices, stock, and errors, and sends alerts when monitored pages change, giving homelab users a self-managed alternative to commercial page watchers.

Platform availability

Available on 4 of 10 platforms

  • Unraid
  • TrueNAS
  • Umbrel
  • ZimaOS
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

88/100 Excellent

Maintained
100last commit 17 days ago
Popular
9135,505 GitHub stars
Easy to install
654 install platforms, install notes, Docker image
Light to run
801 GB minimum RAM, runs on ARM

Availability: platform listings confirmed today, links checked 8 days ago

GitHub stars
35,505
Open issues
383
Last commit
2026-11-04
Latest release
0.60.10
License
Apache-2.0
Activity
rising

Checked 17 days ago - source: GitHub (dgtlmoon/changedetection.io)

Resources & Compatibility

Minimum requirements: 1 GB RAM, 1 CPU core(s), 10 GB disk. ARM (e.g. Raspberry Pi) is supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Give it a data folder and a port Start it with an empty folder and port, such as `changedetection.io -d /path/to/empty/data/dir -p 5000`, then open http://127.0.0.1:5000. That folder stores your watches and settings, so if you don’t point it at a folder you keep safe, you can lose your whole setup if you reinstall or move servers. source
  • Enable USE_X_SETTINGS behind a proxy If you serve it through Nginx on a subpath like /app, set USE_X_SETTINGS=1 (the setting that tells the app to use the proxy’s address information) and pass the X-Forwarded headers in the Nginx config. Without that, the app can’t correctly see its real web address, which can break links, forms, or saved page actions. source
  • Start the browser helper on boot If you use the Playwright/browser-based fetcher (the option for pages that need JavaScript), enable both the browserless and changedetection.io systemd services so they start after a reboot. If the browser helper is not running, some dynamic web pages may fail to load or change-detect properly. source

Fetched 54 days ago - each note links to its source

Alternatives (4)

  • Distill Web Monitor - Distill is a web monitoring tool.
  • Huginn - Huginn is a self-hosted automation platform for building custom agents that monitor online sources, react to events, and take actions on yo…
  • Visualping - Visualping is the easiest to use website change monitoring, website change detector and website change alert software of the web.
  • WebSite-Watcher - WebSite-Watcher detects website updates and highlights all changes in the text.

Checked 51 days ago - source: AlternativeTo

Common questions

Which directory holds my configuration, and why should I back it up?

The data directory you provide at startup stores your watches and settings. If you do not keep that folder safe, you can lose the whole setup when you reinstall or move servers.

How do I configure it correctly behind an Nginx subpath?

Set USE_X_SETTINGS=1 and pass the X-Forwarded headers in the Nginx config. Without this, the app cannot correctly see its real web address, which can break links, forms, or saved page actions.

What must start if I use the Playwright browser fetcher?

Enable both the browserless and changedetection.io systemd services so they start after a reboot. If the browser helper is not running, dynamic web pages may fail to load or change-detect properly.

Why can the element picker be unreliable on some pages?

Obfuscation from ad blockers like uBlock Origin can interfere with the UI picker when the element text or path contains random fragments. This can make the target basically unpickable.

Answers sourced from github.com, github.com, github.com, www.reddit.com

Community

Collected 48 days ago - public community threads