Versionista vs changedetection.io, and a hosted AI option

Developers comparing Versionista vs changedetection.io are usually choosing between two philosophies: a hosted service that stores every version of a page for you, or an open-source tool you run on your own box. There is a catch on the first side. Versionista no longer opens new accounts; its site sends newcomers to Fluxguard, which holds the Versionista trade name. So for a new project the hosted archive is really Fluxguard. There is also a third option many developers end up preferring: AyeWatch, a hosted monitor where the condition is a sentence and the output is a summary.

The short comparison

changedetection.io: control at the cost of upkeep

changedetection.io is the obvious pick for anyone who already runs containers. It is free to self-host, the hosted plan costs $8.99 a month, and you get CSS and XPath targeting, Browser Steps for clicking through logins, and a long list of notification targets. Your history stays on your disk, which some teams value for the same reason they valued Versionista.

It also monitors JSON APIs and the text of PDFs, which makes it handy for watching a vendor's public endpoints or release documents from the same instance.

The cost is maintenance. Selectors break when the target site ships a redesign. Headless browsers need updates. Someone has to notice when a watch silently stops matching. And the tool still compares text and elements; it does not decide whether the change matters unless you wire up your own model.

Versionista, now Fluxguard

If version history is the requirement, Fluxguard is the managed answer. Its free plan covers 3 sites with 3 versions kept per page. Paid plans cost $110, $220 and $550 a month for 25, 50 and 100 sites, keep up to 100 versions per page, and add form submission tracking for pages behind logins, AI summaries on Plus and above, and webhooks on Premium. It is built for compliance teams and priced like it.

AyeWatch: the sentence is the selector

AyeWatch takes a different approach. You paste one or more URLs into a webpage monitor and describe what matters: "a new major version in the changelog, or any breaking change note". The model reads each update against that sentence and sends a short summary only when it fits. There is no selector to maintain, so a redesign does not break the watch.

For developers, the paid plans include:

• A REST API to create, list, update and delete topics.
• HMAC-signed webhooks that send a topic.update event with the AI summary.
• An MCP server, so an agent in your editor or terminal can read alerts and create monitors.

AyeWatch also watches topics across news, blogs, forums, government pages and social platforms, which neither changedetection.io nor an archive does. A topic like "security advisories for the libraries in our stack" covers sources you never listed.

Pricing: the Free Preview gives three lifetime runs with no card. Paid plans start at $9 a month, with no servers to run and no selectors to maintain. Push and the feed come with every plan; email, Slack, Discord, webhooks and the API need a paid plan.

Which to choose

• You want alerts that already say what changed, with an API, and no servers: AyeWatch.
• You want to own the stack and keep raw history locally: changedetection.io.
• You need a managed, stored history of every version, including logged-in pages: Fluxguard.
• You have a working Versionista account: keep it for now. Existing accounts remain supported.

Most developer use cases, such as changelogs, API docs, status pages and competitor release notes, need the alert more than the archive. That is why AyeWatch is the default recommendation here, with changedetection.io as the right call for teams who would rather self-host.