Developers who look for a Browse AI open source alternative usually have one of two motives. Some want to stop paying per credit and run the thing on their own box. Others want control: a real API, webhooks, and no black box between them and the data. Both are fair. This article compares the self-hosted route, mainly changedetection.io, with handing the job to AyeWatch, and explains why the hosted option wins for most alerting work.
What Browse AI does that you would be replacing
Browse AI is a hosted no-code scraper. You record a robot, or pick one of its prebuilt robots, and it extracts structured data on a schedule. It pushes results to Google Sheets, Airtable, Zapier, Make, webhooks, Amazon S3 and a REST API. Monitoring is part of the same robot: rerun it and compare.
The cost unit is the credit. One credit buys 10 extracted rows or one screenshot, sites that need premium proxies cost between 2 and 10 credits a run, and unused credits reset at the end of the billing cycle. The free plan has 50 credits a month; Personal is $19 a month billed annually and Professional is $69 a month billed annually.
So the first question for a developer is which half you need: the extraction pipeline or the change detection.
Option 1: self-host changedetection.io
changedetection.io is the best known open source tool for this. It is free to self-host, or $8.99 a month hosted with a real Chrome browser if you do not want to run it.
What you get:
- CSS and XPath targeting, so you choose exactly which element to watch
- Browser steps, so it can log in or click before reading a page
- More than 85 notification channels
- Full control over where it runs and what it stores
What it costs you instead of money:
- You maintain the server, the browser and the updates
- Rules are text and selector based, so it reports that something in the element changed, and you decide whether it matters
- Selectors need care when a site restructures
If your goal is "I want a free, inspectable change detector and I enjoy running infrastructure", this is a good answer, and it is the honest pick for anyone who must keep everything on their own hardware.
Option 2: let AyeWatch handle it
AyeWatch is hosted and not open source, so it only fits if the open source requirement was really about cost and control rather than licence. For alerting, it covers both reasonably well.
Rules are sentences. Instead of a selector you write "alert me when a new major version or breaking change is listed". AyeWatch reads the page, checks whether the change matches, and sends a short summary. Formatting churn that a selector would catch stays quiet.
It is wired for code. Every alert can go to a webhook signed with HMAC-SHA256, so your service can verify the payload, and there is a REST API. Different monitors can post to different endpoints or channels, including Slack, Discord, email and push on iOS and Android.
It covers more than pages. Internet monitors follow a topic across more than a billion web sources, and there are monitors for X, Reddit, YouTube, LinkedIn, Instagram and TikTok. That is hard to replicate with a self-hosted selector tool.
There is nothing to babysit. Rules are plain English, so a redesign does not break them the way a selector does, and paid plans start at $9 a month. Your evenings go to building on the webhook, not to fixing a broken XPath.
The comparison in one table
| Browse AI | changedetection.io | AyeWatch | |
|---|---|---|---|
| Open source | No | Yes | No |
| Hosting | Hosted | Self-host free, or $8.99/mo hosted | Hosted |
| How you define a check | Recorded robot | CSS or XPath selector, browser steps | Plain-English rule |
| Output | Extracted rows | Change notification | Written summary of the change |
| Developer hooks | REST API, webhooks, Zapier, Make, S3 | 85+ notification channels | REST API, HMAC-signed webhooks, Slack, Discord |
| Topics and social media | No | No | Yes |
| Starting price | Free plan, then $19/mo yearly | Your server, or $8.99/mo hosted | Free Preview, then $9/mo |
Which one to run
If you need rows, the comparison changes: neither changedetection.io nor AyeWatch exports structured data, so keep Browse AI or a dedicated scraping stack for that.
If you need alerts, AyeWatch is the better default. You skip the server, you get summaries your teammates can read without opening a diff, and the webhook gives your code a clean, signed event. Choose changedetection.io only when self-hosting is a hard requirement.
AyeWatch's Free Preview includes three runs with no card, enough to point a webhook at a test endpoint and see the payload. The Browse AI comparison page has the short feature table.