CI passed. The deploy completed. Your signup page just broke.

Not currently, and it is worth knowing before you start. Sitewatch monitors publicly reachable pages — which for most SaaS products is the part that decides whether anyone becomes a customer: marketing, pricing, docs, the login and signup pages themselves, and public API endpoints.

Yes, on Starter and Pro. Monitor your health-check and public endpoints alongside your pages, checking the response and the content that comes back rather than only whether something answered.

One on Free, 25 on Starter, 100 on Pro. A "site" is a domain, and you can monitor as many individual pages within a domain as you need — so marketing, docs and app entry points on one domain do not eat three slots.

Yes. If your marketing site, docs and app all deploy from one repo, you can either use a deploy hook per project or a single hook that triggers checks across every monitored property.

On Pro, Sitewatch checks from two regions — EU and US — so an edge location serving failures shows up rather than being averaged away by the region your team happens to sit in.

An error tracker reports problems your code knows about, from inside sessions that already loaded. Sitewatch checks from the outside, on a schedule, and catches the failures where nothing errors at all — a file that stopped being served, a page that quietly changed, an endpoint that stopped answering. Most teams run both.