What Witch is.

• HTTP and TLS monitoring
• Real Chromium browser monitoring (desktop and mobile viewports)
• Visual baselines and regression detection
• DOM, element, and selector checks
• JavaScript and browser failure detection
• Native JavaScript Error Tracking
• Incident evidence correlation and forensics
• Email and Discord alerts
• Monthly reports
• Public status pages

An uptime monitor asks whether an endpoint answers. That is necessary but insufficient: a page can return HTTP 200 while its checkout button vanished, its JavaScript bundle 500s, or its layout collapses on mobile.

Witch renders the page in a real Chromium browser — separate desktop and mobile viewports — compares against accepted visual baselines, verifies expected elements, and collects browser and JavaScript failure signals. When something breaks, the incident carries the evidence: screenshots, failed requests, DOM signals, and correlated runtime errors.

Witch includes error tracking built in: browser errors are captured, grouped into issues, and correlated with monitoring incidents — so a TypeError spike and a failed check appear in one investigation instead of two disconnected tools. Error tracking supports monitoring; it never marks a site down on its own.

Agencies and freelancers who run client sites, teams that ship changes to production and need to know when the page — not just the server — stops doing its job, and anyone who has learned the hard way that a 200 status does not mean the checkout works.

Witch is observational monitoring. It is not a vulnerability scanner, not a security testing or exploitation platform, and not a load-testing tool. It watches pages the way a user's browser would and raises incidents when something that matters changes for the worse.