Developers who outgrow WebSite-Watcher often go looking for an open source website watcher next. The reasoning is simple: if the tool is going to run on a machine you maintain anyway, it may as well be one you can read, script and put in a container. This comparison looks at the two open source options people usually land on, what they give up compared with Aignes's program, and where a hosted service with an API fits in.
What you are replacing
WebSite-Watcher is closed-source Windows software, and it is more programmable than its interface suggests. The Personal and Business editions include a scripting language and a plugin system written in an integrated Basic dialect; Aignes's example is a plugin that alerts only when a price falls inside a range. Reports export to HTML, CSV, JSON or XML. Business adds a scraper and proxy rotation. Check macros record logins and form steps and replay them before each check.
So the bar for a replacement is not "can it diff a page". It is "can I put logic between the diff and the alert".
urlwatch
urlwatch is an open source command-line tool distributed on PyPI. It fetches the pages you list, compares them with the last run and sends a unified diff by email, to the terminal or through third-party services.
- Good for: a single developer with a server, a cron entry and a preference for plain text.
- Logic: you shape what gets compared and where results go through its configuration and your own scheduling.
- Gives up: any interface, any hosted option and anything that runs while your server is down.
changedetection.io
changedetection.io is open source and can be self-hosted for free, or rented as a hosted service for $8.99 a month. It supports CSS and XPath rules, trigger text, ignore text and browser steps for pages behind a click or a login form, and it can notify more than 85 kinds of targets including Slack, email and Discord.
- Good for: a team that wants a web interface and a Docker container instead of a desktop app.
- Logic: filters and triggers, not a scripting language.
- Gives up: you now patch and monitor the monitor.
A hosted option with an API
Not every developer wants to run another service. AyeWatch is not open source, but it covers the "programmable" part from a different direction. Every paid plan includes a REST API to create, list, update and delete monitors, and signed topic.update webhook events that carry an AI summary of what changed. Webhooks are signed with HMAC, so your receiver can verify them. Paid plans also include an MCP server, so an AI agent can manage monitors with an API key.
The rule itself is a sentence rather than a selector. Instead of an XPath that breaks when a page is redesigned, you write "alert when a new major version is released or a breaking change is listed", and a model decides whether each change qualifies.
A small receiver is enough to wire it into existing tooling: verify the signature, read the summary field, and post it to a team channel or open an issue in your tracker. That covers much of what WebSite-Watcher users build with bookmark actions and exported reports, without a Windows host in the loop.
Side by side
| WebSite-Watcher | urlwatch | changedetection.io | AyeWatch | |
|---|---|---|---|---|
| Source | Closed | Open | Open | Closed |
| Runs on | Windows | Your machine | Your server or hosted | Cloud |
| Custom logic | Basic plugins, scripting | Config, your scripts | Filters, triggers, browser steps | Plain-English rule |
| Output | Email, reports, actions | Diff by email, terminal, services | 85+ notification types | Push, feed; paid: email, Slack, Discord, webhooks, API |
| Cost | Free edition, €49 or €299 | Free | Free self-hosted, $8.99/mo hosted | Free Preview, then $9/mo and up |
Picking one
If the point is owning every line, choose urlwatch for a single script or changedetection.io for something a team can click through. Both keep the WebSite-Watcher habit of precise targeting and lose its Windows dependency.
If the point is to stop running infrastructure, AyeWatch is the better fit. Paid plans start at $9 a month and include the REST API, signed webhooks and the MCP server, so your code receives a summary of what changed, already judged against a plain-English rule, rather than a raw diff to parse.
Stay on WebSite-Watcher if your workflow leans on recorded login macros, the Business scraper or Basic plugins, since none of the alternatives here copy those one for one. For the rest, the AyeWatch API docs and Free Preview are a quick way to test whether a sentence can replace your filters.