PageCrawl vs changedetection is a common comparison for developers because the two sit at opposite ends of the same job. PageCrawl.io is a hosted service with a large feature list and per-plan quotas. changedetection.io is open source you run yourself, or rent hosted for $8.99 a month. Both diff pages. Neither decides what a change means unless you add AI on top. This piece compares them on what developers wire into their own tooling, then makes the case for a third option, AyeWatch, which starts from the meaning instead of the diff.
The short version
| AyeWatch | PageCrawl.io | changedetection.io | |
|---|---|---|---|
| Hosting | Hosted only | Hosted, EU data centres | Self-host (Apache 2.0) or $8.99/mo hosted |
| How changes are judged | Semantic AI against your written rule | Text, visual and element diffs, AI score 0-100 | Text and element diffs, optional LLM rules |
| AI cost | Part of the plan | 15 to 10,000 AI uses a month by plan, or your own key | Your own LLM key or local model |
| API | REST on paid plans | On every plan | REST |
| Webhooks | Signed, paid plans | Every plan | Via Apprise |
| Beyond your URLs | Topics, news, forums, six social platforms | Auto-discovers new pages on tracked sites | No |
| Starting price | Free Preview, then $9/mo | Free, then $160/yr | Free self-hosted |
Where PageCrawl wins
PageCrawl gives a lot away on the free tier. API access, webhooks, n8n, Zapier, Home Assistant and its MCP server are on every plan, including the six-page free one. Perform Actions can click, type and submit forms before a check, and paid plans add login-protected pages. Enterprise and Ultimate add residential proxies for sites that block bots, and Ultimate records every check as a WACZ web archive.
The AI layer is real: each alert carries a short summary, changes get a 0 to 100 importance score with a threshold you set, and dismissing a change teaches the filter. AI uses are capped per plan, from 15 a month on Free to 10,000 on Ultimate, unless you connect your own OpenAI, Gemini, Claude or OpenRouter key.
For a developer, the downside is that everything is configuration in someone else's UI and quota system. When checks hit the monthly cap, they pause.
Where changedetection.io wins
If the data must stay on your hardware, changedetection.io is the answer, and nothing else here competes. You get CSS, XPath, JSONPath and jq filters, Browser Steps for scripted logins, restock and price detection, and PDF text diffs. Connect an LLM endpoint, including a local Ollama model, and you can write intent rules and get AI summaries.
The cost is operations. A Chrome container to keep alive, proxies that get blocked, volumes to back up, and selectors that quietly match nothing after a redesign.
Why AyeWatch is the better default
Both tools above start from "what changed in this element" and add AI to filter the result. AyeWatch starts from "what do I care about" and works backward. A monitor is one or more URLs plus a sentence, and the AI compares each new version against that sentence. There is no selector to drift and no score threshold to tune.
For developer workflows, the interface is small and scriptable:
- REST API on paid plans: create, list, update and delete monitors from CI or a script.
- Signed webhooks:
topic.updateevents with an AI summary in the payload, HMAC-signed so you can verify the sender. - MCP server at
https://ayewatch.ai/api/mcp, so a coding agent can set up a monitor from a prompt like "watch this SDK's release notes and tell me about breaking changes". - Per-monitor routing to Slack, Discord, email or webhook.
The reach is the other difference. A dependency's breaking change often appears in a GitHub discussion, a Reddit thread or a maintainer's post on X before the docs change. AyeWatch topic monitors cover news, forums, blogs and six social platforms, which neither diffing tool attempts.
Paid plans start at $9 a month. For a developer, the appeal is that the judgment happens before the webhook fires: your code receives a signed event with a summary of a change that already matched your rule.
How to choose
- You want alerts that track intent, plus coverage beyond your URL list, without running anything: AyeWatch.
- You need self-hosting, or full control of the stack: changedetection.io.
- You need hundreds of URLs checked every few minutes, logins, bot-blocking workarounds or WACZ web archives: PageCrawl. At that scale its per-page pricing is hard to beat.
Most developers tracking a few dozen pages and a handful of projects will spend less time on AyeWatch than on either alternative. The PageCrawl comparison table has the full feature list.