1
Step 1
Select Your Goal
What should this monitor watch for? We'll set up the right detection, filters, and alerts that you can customize later.
Privacy-first · Runs 100% locally · No accounts
DEVELOPERS & API
Web monitoring from your terminal.
CLI, MCP server, YAML config, BYOK AI. Watch dependency docs, API changelogs, and status pages — and pipe results into the AI clients and pipelines you already use.
The documentation you integrated against last quarter is not the documentation that exists today. API providers update endpoints, rename parameters, add required fields, and deprecate features on their own schedules. If you are not actively watching, you find out the hard way — through a broken build or a failed request.
Changelogs are unreliable. Many providers do not maintain them, publish them inconsistently, or bury breaking changes under unrelated updates. RSS feeds go stale. Email announcements go to spam. By the time a change reaches your backlog, it has already cost you time.
"The docs you integrated against last quarter are not the docs that exist today."
PageSignal watches the pages you care about, on your machine, and tells you exactly what changed — through your terminal, your scripts, or your AI assistant.
CLI-first workflow.
A full terminal interface for monitor, alert, snapshot, incident, and shared tool operations. Top-level shortcuts for the most frequent operations (`list`, `search`, `get`, `run`, `status`). Grouped command sets for structured workflows. Table output by default, JSON with a flag — pipe straight into `jq`, your shell scripts, or your CI pipeline.
- monitors · alerts · snapshots · incidents · tools · watch · serve
- Batch runs by UUID, domain, name, profile, or label
- `pagesignal alerts list --json | jq` works as expected
MCP server for AI integration.
Run `pagesignal serve` and the MCP server exposes 30+ tools and 10 resource templates to any MCP-compatible AI client. Tools cover querying monitor status, reading alert history, triggering runs, comparing snapshots, managing incidents. Preset configurations ship for Claude Desktop, Claude Code, ChatGPT, Codex, Gemini CLI, OpenCode, and a generic JSON format.
- 30+ MCP tools, organized by category
- 10 URI-style resource templates (`pagesignal://monitor/{uuid}/...`)
- Catalog-driven; tool enablement per deployment
BYOK AI — no PageSignal account, no PageSignal cloud.
PageSignal integrates with AI providers using your own API keys. Four providers supported: OpenAI, Anthropic, Google Gemini, and Ollama (fully local). Five CLI adapters: Claude Code, Codex, Gemini CLI, OpenCode, and a custom adapter. Route-based model assignment lets you point different tasks at different models — cheap models for summaries, capable models for analysis.
- OpenAI · Anthropic · Gemini · Ollama
- Provider validation and health checks at startup
- URL redaction strips internal paths before any AI call
USE CASES Built for
Built for
the way you ship.
Third-party API documentation
Point a monitor at the API reference for every dependency. When a provider renames a response field or adds a required header, you get alerted before it breaks production.
SaaS pricing & limits
Vendors update rate limits, storage quotas, and seat counts without announcement. A CSS-selector monitor on the pricing comparison table catches changes the day they happen.
Status pages
Status pages change during incidents and sometimes between events. A text monitor gives you an independent signal that does not depend on the provider's notification system.
AI workflows via MCP
Connect the MCP server to Claude Desktop or Claude Code. Ask natural-language questions about your monitoring data — what changed, which monitors have unresolved alerts, what the last comparison showed.
YAML automation
Store monitor definitions in your infrastructure repo. Provision new machines or onboard team members by importing the YAML. Import preview confirms nothing unexpected changes.
Dependency changelogs
Monitor the changelog of libraries you depend on. Text match rules alert specifically when a new major version is mentioned, so you can plan upgrades early.
Cloud provider deprecations
Cloud providers announce deprecated services and removed APIs on their docs sites. Monitoring those pages surfaces deprecation notices in your alert feed instead of your incident queue.
SDK & library docs
When a library updates its docs for a new major version, text diff and layout diff both signal the change. Track the migration guide page to get alerted when migration docs are published.
AI-assisted triage
When an alert fires, ask your AI assistant to summarize the change, compare it to the previous snapshot, and suggest what in your codebase might be affected — MCP gives the AI direct access.
Features Everything you need to
Everything you need to
track the web
Six detection modes
Text, layout, visual diffs, price/number tracking, SEO signals, and AI-evaluated changes. Run one alone or combine them with AND/OR gating on the same monitor.
Visual Text Layout Price SEO AI
Point-and-Click
Select any element on a page to monitor just that — a price, button, paragraph, anything.
Briefs
Get a daily brief of what matters most across the pages you watch.
Smart Noise Filtering
Strips ads, timestamps, and carousels. Only real changes reach you.
Real Browser Captures
Checks pages in a real browser so JavaScript, sessions, and dynamic content render correctly.
Conditional Logic Gates
Set rules like "notify me only if price drops below $50" or "alert when 'Sold Out' disappears."
IF price < $50.00
THEN Notify → Desktop + Telegram
BYOK AI
OpenAI, Anthropic, Google Gemini, or local Ollama. Your key, your model, your route — plain-English summaries of every change.
Login-Protected Sites
Reuses your active browser session to monitor pages behind authentication.
Anti-Bot Mode
Human-like rendering with jitter bypasses Cloudflare and bot detection.
NOTIFICATIONS Pipes into
Pipes into
your stack.
Webhook for Telegram / JSON pipelines · Telegram bot with inbound commands · Desktop for immediate alerts · Email for weekly digests.
Webhook
POST · 200 OK { "event": "change.detected", "monitor": "..." }
Telegram
@pagesignal_bot · 14:43 🔔 Change detected — tap to review the diff
Desktop
2 min ago Page changed on amazon.com · -$120
Email
Monday · 09:00 Subject
Weekly digest · 14 changes across 8 monitors
How It Works Set it up in seconds
Set it up in seconds
in 60 seconds.
No accounts, no cloud, no complicated setup.
2
Step 2
Choose what to track
Pick one of six detection modes — or combine them with AND/OR gating on a single monitor.
3
Step 3
Set your rules
Schedule (60s–24h), text match rules, price thresholds, AI focus instructions, noise filters.
4
Step 4
Get notified
Desktop, email, Telegram, or webhook — immediate, grouped, or digest.
Privacy-First What makes us
What makes us
different.
No accounts. No cloud. No tracking. Everything stays on your device.
100% Local
Nothing touches a remote server.
No Account
No sign-ups or personal info.
Zero Telemetry
No analytics, no phone-home.
Full Export / Migration / Backups
YML and ZIP backups, anytime.
PageSignal
Cloud monitors
Browser extensions
Runs locally
Yes
No
Sometimes
Cloud account
No
Yes
Sometimes
Local backup
Yes
No
Limited
Real browser capture
Yes
Sometimes
Limited
Login-protected pages
Yes
Limited
Limited
AI summaries
Optional
Sometimes
Limited
Runs locally
PageSignal Yes
Cloud monitors No
Browser extensions Sometimes
Cloud account
PageSignal No
Cloud monitors Yes
Browser extensions Sometimes
Local backup
PageSignal Yes
Cloud monitors No
Browser extensions Limited
Real browser capture
PageSignal Yes
Cloud monitors Sometimes
Browser extensions Limited
Login-protected pages
PageSignal Yes
Cloud monitors Limited
Browser extensions Limited
AI summaries
PageSignal Optional
Cloud monitors Sometimes
Browser extensions Limited
FAQ Developer
Developer
questions.
How do I install and run the CLI?
The `pagesignal-cli` binary ships with the desktop app. After installing PageSignal you can call it directly from any terminal. JSON output mode (`--json` flag) makes it scriptable; table mode (default) is for interactive use.
Which AI providers are supported?
Four API providers — OpenAI, Anthropic, Google Gemini, and Ollama. Five CLI adapters — Claude Code, Codex, Gemini CLI, OpenCode, and a custom adapter with configurable command, prompt input, and JSON extraction path. Ollama support means you can run AI entirely locally with no external calls.
Can I version-control my monitor configurations?
Yes. Export to YAML, commit to your infrastructure repo, import on any machine. Three export profiles (settings-only, monitors-only, both). Import preview shows a dry-run before any change is applied. Two-phase restore for safe re-provisioning.
What does the MCP server expose?
30+ tools across 7 categories (monitors, alerts, incidents, history, organization, settings, storage) plus 10 resource templates using URI-style addressing (`pagesignal://monitor/{uuid}/alerts`, etc). Preset client configs ship for Claude Desktop, Claude Code, ChatGPT, Codex, Gemini CLI, OpenCode, and a generic format.
Does any monitoring data leave my machine?
No — by default everything stays in a local SQLite database. AI features are opt-in and only the content you route through AI is sent to the provider you chose. URL redaction strips paths from prompts before they leave. AI request logging records every outbound call so you have a full audit trail.
Ready to monitor from your terminal?
Watch your stack. Stay ahead of breaking changes.
Download macOS · Windows · v3.2