Go beyond “it’s up.”
HTTP status, latency, content assertions, and response headers.
HTTP monitoringYour early warning system
Your site can be up and still let people down. See availability, browser performance, and configuration drift together.
From your API to your TLS certificate, give every layer of your stack a canary.
Monitor overview
A heads-up before an outage. Certificate expiry is visible alongside service health.
Coverage
Start with recommended coverage, then tune individual monitors.
HTTP status, latency, content assertions, and response headers.
HTTP monitoringPage performance, accessibility, screenshots, and JavaScript errors.
Browser performanceAccessibilityDNS, TCP, TLS, and SSH reachability and configuration.
Network monitoringTLS and SSHExplainable alerts
Thresholds and drift rules create clear alerts that reach the right recipients.
A monitor crosses a threshold or finds configuration drift.
Run details show the failed assertion and observed values.
The alert is recorded and sent to configured recipients.
Questions
SiteCanary monitors HTTP endpoints, browser performance, accessibility, JavaScript errors, DNS, TCP, TLS, and SSH.
It combines availability checks with response assertions, browser measurements, accessibility scans, infrastructure diagnostics, configuration drift, and bounded long-term history.
Detailed recent runs are retained in Postgres up to each monitor's configured limit, while fixed-size ringstore files keep bounded aggregate history across longer time ranges.
HTTP monitors support manually configured request headers. Auth flows currently support saved configuration and manual tests only; they cannot be attached to monitors and do not automatically log in, refresh tokens, or share credentials with scheduled monitors.
Deployment is environment-driven and includes a documented Linux VPS workflow. Availability and commercial packaging depend on the operator providing the service.
Start simply
Create recommended coverage, then adjust each monitor as your needs grow.