Sken.io vs changedetection.io: hosted boxes or your own Docker

A developer who wants to know when a docs page, a status page or a vendor's terms change has two familiar routes. Pay a small monthly fee for a hosted service, or run something yourself. Sken.io vs changedetection is that choice in its simplest form. This piece compares the two on what a developer cares about, then makes the case for a third route, AyeWatch, which skips both the box-drawing and the server.

The short version

Prices and features from each vendor's site, checked October 2026.

Sken.io: the low-effort hosted option

Sken.io's appeal is that there is almost nothing to set up. Paste a URL, drag a rectangle around the part you care about, choose an interval from one minute to one month, and pick visual or content mode. Visual mode compares how the area renders. Content mode compares its text and ignores styling. Element removal drops cookie bars, chat widgets and rotating ads before comparing.

For developers there is more under the hood than the landing page shows. The Sken.io API docs describe scoped API keys, job and check endpoints, bulk imports, exports, rate-limit headers and an OpenAPI spec, plus an MCP server.

The trade-off is that you get the history Sken.io keeps, up to 12 snapshots per monitor, and you work within its targeting model. If you want logic beyond "this box changed", you build it downstream.

changedetection.io: the one you own

changedetection.io is the default answer for developers who like control. It is open source under Apache 2.0, runs from a Docker image or pip, and costs nothing beyond your hosting. Browser Steps let it log in and click through flows, which Sken.io does not aim to do. Notifications reach more than 85 services through Apprise.

The cost is time. You maintain the instance, you keep selectors working when a site's markup shifts, and you tune filters by hand. For a homelab or a team with spare ops capacity, that is fine. For everyone else it becomes one more service to babysit.

Where both leave you

Both tools answer "did the bytes change?" A developer usually wants "did something change that affects me?" A docs page that bumps its copyright year, a changelog that reorders entries, a status page that refreshes a timestamp: all real diffs, all noise. Selectors and boxes cut some of it. They cannot tell a deprecation notice from a typo fix.

AyeWatch: describe the change, skip the selector

AyeWatch takes a URL and a sentence. "Alert me when any endpoint is marked deprecated, an auth method changes or a rate limit is lowered." It reads each change on the page against that sentence and sends a short summary only when it matches. No rectangle, no XPath, no container.

Three things make it useful on a developer's new tab:

1. Topic monitors. Describe a library or vendor and AyeWatch searches more than a billion sources, including news, forums and blogs, for outages, security reports or release news that never show up on the page you watch.
2. API and MCP. Every paid plan includes the REST API to create, list, update and delete topics, with HMAC-signed webhook events that carry the AI summary. The MCP server works with an API key on paid plans.
3. Phone and desktop. Push and the feed come with every plan on web, iOS and Android.

Paid plans start at $9 a month after a Free Preview of three lifetime runs with no card, and you can cancel at any time.

How to choose

• You want a visual record or one-minute checks for a few euros: Sken.io.
• You want logins, full control and no subscription: changedetection.io on your own box.
• You want alerts that already know what matters: AyeWatch.

The fastest test is to take the changelog you check most and set it up as an AyeWatch monitor next to whatever you run now. AyeWatch also keeps a feature comparison against Sken.io.