Calafia vs page-change watchers
Competitor facts checked July 10, 2026 against each vendor's public pages — corrections welcome.
Visualping, Distill.io, and ChangeDetection.io are the workhorses of web monitoring, and they deserve their reputations: Visualping says it serves over two million users; ChangeDetection.io is open source with 30k+ GitHub stars and can be self-hosted for free. If you know the exact page — and the exact element on it — you want to watch, they are mature, reliable tools. The difference with Calafia isn't reliability. It's what you have to know before you start.
The short version: page watchers take a URL and a selector. Calafia takes a sentence and finds the sources. They're better when you already know precisely what to point at; Calafia is better when what you have is an outcome — “a June campsite in Yosemite” — and the pointing is the hard part.
What page watchers are
You give them a page URL, pick the region or element you care about (a price, a stock indicator, a block of text), and choose a check frequency. When the selected content changes, you get notified. Pricing spans from genuinely free — ChangeDetection.io self-hosted, Visualping's free tier (checks about every 60 minutes on a handful of pages) — to paid cloud plans: Visualping from roughly $10/month, Distill's cloud tiers around $15–80/month depending on frequency, ChangeDetection.io's hosted version at $8.99/month (figures from each vendor as of mid-2026).
They're generic by design, which is their power: any public page, any element.
What Calafia is
You describe what you want in plain English. Calafia picks the sources, checks them with source-aware adapters (structured requests against the actual availability data, not screenshots of a page), diffs against its own last observation, and emails you when something material changes. When it couldn't check, it says so — by email, not in a dashboard you'd have to remember to visit. You adjust it by replying.
Side by side
| Page watchers | Calafia | |
|---|---|---|
| What you provide | A URL + the element/region to watch | A sentence describing the outcome |
| Finding the right page | Your job | Calafia's job |
| Multi-source questions (“any Valley campground, those dates”) | One watch per page you set up yourself | One scout; the adapter checks the source properly |
| When the site redesigns | Generic diffs can break or alert on cosmetic changes — failures typically surface in your dashboard | Source-aware adapters are maintained; if one breaks, you get a couldn't-check email |
| Check frequency | Free tiers ~hourly; faster costs more (e.g. Distill cloud ~$15–80/mo) | Minutes-level on supported sources; watching one thing is free |
| Adjusting | Reconfigure URL/selector/settings | Reply to the email |
| Self-hosting | Yes (ChangeDetection.io, open source) | No |
| Scope | Any public page on the internet | Supported sources, growing — deep rather than universal |
When a page watcher is the better choice
Real cases, and there are plenty:
- You know the exact element. A price on one product page, a “sold out” badge, a paragraph on a terms page — pointing a selector at it is precise and cheap.
- The page is obscure. Page watchers cover the entire public web. Calafia checks sources it has adapters for; if your target is a small-town permit page we don't support yet, a page watcher is the right tool today.
- You want to self-host. ChangeDetection.io is open source; run it yourself and it costs server pennies.
- You want raw “anything changed” coverage of a whole page, not a judgment about what's material.
When Calafia is the better choice
- You have an outcome, not a URL. “Email me if a site opens at Upper Pines Aug 14–16” — no page-picking, no selector, no learning what an XPath is.
- The source is hostile to generic diffing. Availability grids re-render, session tokens shift, layouts change. A source-aware adapter reads the actual availability; a pixel or DOM diff reads the weather.
- You want failures to find you. Broken watches that quietly stop are the classic page-watcher trap — the failure lands in a dashboard. Calafia emails you when it couldn't check, in the same inbox as the alerts.
- You want to refine conversationally. “Actually, weekends only” is a reply, not a settings session.
FAQ
Aren't these tools basically the same thing?
They overlap in tech, not in job. Page watchers monitor a page you specify. Calafia pursues an outcome you describe — finding and checking the right sources is part of the product.
Can't I just point Visualping at the recreation.gov availability page?
You can try, and some people do. Availability grids are tough targets for generic diffing: dynamic rendering and layout changes can produce both false alerts and silent breakage. A tool that queries availability data directly and compares it to its own last observation has structurally fewer ways to be wrong.
Is Calafia open source or self-hostable?
No. If self-hosting is a requirement, ChangeDetection.io is genuinely good and we'd rather point you there than pretend.
What does “couldn't check” mean in practice?
Sources go down, rate-limit, or change — for every monitoring tool, ours included. When a scout's checks fail persistently, you get a plain email saying it couldn't check and that it will keep trying. Silence stays meaningful: no email means “checked, nothing changed.”
One sentence, then it's watching
Skip the selector. Say the thing: Build a scout → — it runs its first real check live on supported sources, and watching one thing is free.
More comparisons: Campnab vs Calafia: an honest comparison · Calafia vs ChatGPT scheduled tasks