# An open-source IFTTT alternative vs a hosted AI monitor

> For monitoring jobs, the choice is usually changedetection.io on your own server or a hosted AI monitor like AyeWatch. Here is how they compare.

URL: https://claudegpt.si/news/ifttt-alternative-open-source  
Published: 2026-10-25T18:37:31.234Z  
Updated: 2026-10-26T07:08:29.831Z  
Author: ClaudeGPT Si Newsroom  
Section: Reviews  
Topics: IFTTT, Open source, changedetection.io  
Publisher: ClaudeGPT Si

## Key takeaways

- changedetection.io is Apache 2.0 open source, free to self-host with Docker, or $8.99 a month hosted.
- AyeWatch is hosted, not open source, and watches pages, topics and social sources from plain-English rules, from $9 a month.
- Self-hosting wins when data must stay on your server or pages sit behind a login.

Developers who outgrow IFTTT often go looking for an IFTTT alternative that is open source, on the theory that if they are going to write glue anyway, they may as well own it. For general automation that is a reasonable plan. For monitoring, the jobs where an applet only exists to tell you something changed, the open-source answer is usually changedetection.io, and the honest comparison is between running that yourself and paying a few dollars for a hosted AI monitor. This article puts the two next to each other.

## What you are actually replacing

Look at your applets and separate them:

- Applets that react to your own devices and accounts. These need an automation tool, open source or not.
- Applets that watch the web: a release notes feed, a status page, a docs page, a subreddit. These need a monitor.

The rest of this piece is about the second group.

## Option A: changedetection.io, self-hosted

changedetection.io is open source under the Apache 2.0 license. You run it with Docker, point it at URLs, and it tells you when the content changes.

What you get:

- CSS, XPath, JSONPath and jq rules to target the part of a page you care about
- Browser steps to log in, click or fill a form before checking
- Ignore-text and trigger-text filters
- 85 plus notification channels through Apprise, including Discord, Slack, Telegram, Matrix and email
- Its own REST API

What it costs you: no license fee, but a server, the browser container for JavaScript-heavy sites, proxies if a target blocks you, and your time when something breaks at the wrong moment. Rules are text and selector based. There are optional AI change rules, but they need your own model provider or a local model.

If you would rather not host it, the same project offers a hosted plan at $8.99 a month with a real Chrome browser.

## Option B: AyeWatch, hosted

[AyeWatch](https://ayewatch.ai) is not open source. It is a hosted monitor that works from plain-English rules instead of selectors. You can watch:

- specific URLs, for changes that matter in the content
- Internet topics, described in a sentence
- social sources: subreddits, X searches and profiles, YouTube channels, LinkedIn posts, Instagram hashtags, TikTok profiles

Each match arrives with a short AI summary and its sources. For a developer the interesting part is what comes with every paid plan: a REST API to create, update and delete topics, HMAC-SHA256 signed webhooks, and an MCP server so an AI agent can set up or pause monitors for you. Slack, Discord and email are paid-plan channels too; the free preview gets the app feed and push.

Paid plans start at $9 a month, and every plan includes the web, iOS and Android apps.

## Head to head

| | changedetection.io (self-hosted) | AyeWatch |
| --- | --- | --- |
| License | Apache 2.0 | Proprietary, hosted |
| Price | Free plus your server; $8.99/mo hosted | Free Preview, then $9/mo |
| How you define a change | Selectors and text filters | A rule written in plain English |
| Social sources | Not its focus | Reddit, X, YouTube, LinkedIn, Instagram, TikTok |
| Topic monitoring beyond a URL | No | Yes |
| Login and click steps | Yes, browser steps | Not listed |
| Notifications | 85 plus via Apprise | Push, email, Slack, Discord, webhooks (paid) |
| API | Yes | REST API and MCP on paid plans |
| Who maintains it | You | AyeWatch |

## Which one a developer should pick

Pick **AyeWatch** if your watch list is a mix of pages, topics and communities, if you want one alert that explains what happened instead of a diff you have to read, and if you would rather not run another container. It is the better default for most small teams, and the API means you can still keep monitor definitions in code.

Pick **changedetection.io** if the data must stay on your own server, if you need browser steps to get behind a login, or if you track hundreds of URLs where a single server bill wins. It is a solid project, and for those cases it is the better tool.

## A practical split

Plenty of teams end up with both: changedetection.io for a handful of authenticated internal pages, AyeWatch for competitor pages, release announcements and Reddit threads about the project. Keep IFTTT, or your open-source automation tool of choice, for the device and account glue.

To see how the hosted side handles your own list, [try a monitor on your release notes page](https://ayewatch.ai/?signup=true). The free preview runs three times with no card.

## Frequently asked questions

### Is there an open-source IFTTT alternative for website monitoring?

Yes. changedetection.io is open source and can be self-hosted with Docker.

### Is AyeWatch open source?

No. AyeWatch is a hosted service, with a REST API, signed webhooks and an MCP server on paid plans.

## Sources

- [changedetection.io](https://changedetection.io), changedetection.io
- [AyeWatch plans and features](https://ayewatch.ai/), AyeWatch
- [IFTTT plans](https://ifttt.com/plans), IFTTT
- [6 Best IFTTT Alternatives for Website Monitoring in 2026](https://ayewatch.ai/blog/ifttt-alternative), AyeWatch