Changedetection.io alternatives
On-demand screenshot APIs vs scheduled change monitoring — understanding when to use each.
What changedetection.io does
Changedetection.io is a self-hosted website monitoring tool. You give it a list of URLs and a check interval (every hour, daily, etc.). It fetches each URL, compares the content against the previous version, and notifies you when something changes — via Slack, email, Discord, Telegram, or dozens of other channels through the Apprise notification library.
It supports CSS and XPath selectors to monitor specific page elements, JSON and XML API monitoring, and optional headless Playwright rendering for JavaScript-heavy pages. Each check stores a snapshot you can compare visually against previous versions.
Common use cases: price monitoring, restock alerts, content change notifications, defacement detection, and tracking competitor pages. It is Apache-2.0 licensed, self-hostable via Docker, and has 30,000+ GitHub stars.
What Openkova does differently
Openkova is a REST API, not a monitoring dashboard. It has no scheduler, no alert system, and no persistent visual history. Instead, it exposes HTTP endpoints:
POST /api/convert/url— give it a URL, get back a PNG, JPEG, WebP, or PDF immediatelyPOST /api/convert/snippet— give it an HTML string, get back a rendered imagePOST /api/convert/file— upload an HTML file, get back a rendered image
It is called from your code — an application backend, a CI pipeline, an AI agent, a batch job — whenever you need a screenshot on demand. There is no browser UI to configure; it is infrastructure you deploy and call.
When to use changedetection.io
- You want to be notified when a page changes — alerts via Slack, email, Discord
- You need a visual history — a timeline of how a page looked over time
- You are monitoring a fixed list of URLs — product pages, competitor sites, status pages
- You want a non-technical UI — changedetection.io has a web dashboard for managing monitors without code
When to use Openkova
- You need screenshots on demand from your application — generate thumbnails, OG images, or PDF invoices at request time
- You are rendering HTML templates — not just URLs; Openkova accepts raw HTML strings and file uploads
- You need a REST API — your code calls an HTTP endpoint; there is no browser UI involved
- You need private / internal URL access — self-hosted Openkova can reach localhost, staging environments, and VPN-protected services
- You are building an AI agent that needs visual web access —
@openkova/mcpgives any MCP-compatible AI client a screenshot tool
Comparison
| Feature | Changedetection.io | Openkova |
|---|---|---|
| Primary purpose | Change monitoring + alerts | On-demand screenshot API |
| Interface | Web dashboard | REST API |
| Screenshot on demand | ✗ (scheduled only) | ✓ |
| Scheduled URL monitoring | ✓ core feature | ✗ |
| Alert notifications | ✓ Slack, email, Discord, Telegram… | ✗ |
| Visual change history | ✓ | ✗ |
| HTML snippet input | ✗ | ✓ |
| HTML file upload | ✗ | ✓ |
| PDF output | ✗ | ✓ |
| MCP server for AI agents | ✗ | ✓ (@openkova/mcp) |
| Self-hostable | ✓ | ✓ |
| License | Apache-2.0 | MIT |
| GitHub stars | 30,000+ | — |
Using both together
The most capable visual monitoring setup uses both tools for what each does best:
- Changedetection.io handles the scheduling, monitoring, and alerting — it knows when a page changes and sends the notification
- Openkovahandles on-demand rendering — when your backend needs a fresh screenshot to attach to a report, email, or dashboard, it calls Openkova's REST API at that moment
Changedetection.io's webhook output can also trigger an Openkova render — when a page change is detected, fire a webhook that calls Openkova to capture and store an archival screenshot at full resolution.
# Triggered by a changedetection.io webhook on page change:
curl -X POST https://your-openkova-instance/api/convert/url \
-H "Content-Type: application/json" \
-d '{
"url": "https://monitored-page.com",
"format": "png",
"viewport": {"width": 1280, "height": 900}
}' \
--output "archive/$(date +%Y%m%d-%H%M%S).png"Alternatives to changedetection.io for visual monitoring
If you are looking for a managed (non-self-hosted) website change monitoring tool, the main options are:
- Visualping — SaaS change detection with a web UI; Business plan $100+/mo. See Visualping alternatives.
- PageCrawl.io — managed monitoring with team features and API access
- Distill.io — browser extension + cloud monitoring for page element changes
For visual regression testing in CI/CD (comparing screenshots across commits rather than monitoring live pages), see the Percy alternatives and Chromatic alternatives pages.
Frequently asked questions
What is the difference between changedetection.io and Openkova?
Changedetection.io monitors URLs on a schedule, stores a visual history, and sends alerts when pages change. Openkova is a REST API you call when you need a screenshot immediately — it returns image bytes, has no scheduler, and no UI. They are complementary tools, not competing alternatives.
Can changedetection.io take screenshots?
Yes, as part of its monitoring workflow — it captures snapshots each time it checks a URL and stores them for comparison. It is not designed for on-demand screenshot generation or batch conversion via a REST API.
Is changedetection.io open source?
Yes — Apache-2.0 license, self-hostable via Docker, 30,000+ GitHub stars, actively maintained. A managed SaaS option is also available.
Can I use changedetection.io and Openkova together?
Yes. Changedetection.io handles scheduling and alerting; Openkova handles on-demand rendering. Changedetection.io webhooks can trigger Openkova renders to archive full-resolution screenshots when a monitored page changes.
See also: Visualping alternatives, Percy alternatives, and the visual regression testing overview.