SiteCanary

Monitoring for applications and infrastructure

Catch outages and drift before customers do.

Monitor availability, performance, configuration, and browser behavior from one place.

SiteCanary is a monitoring platform for engineering teams. Monitor HTTP endpoints, browser performance, accessibility, JavaScript errors, DNS, TCP, TLS, and SSH from one operational view.

Start monitoring View docs

Monitor overview

Current health

Illustrative
HTTP APIapi.example.com
Healthy
184 ms
TLS certificateexample.com:443
Expiring soon
14 days
DNS resolutionexample.com
Healthy
4 answers

Coverage

Monitor each layer of your stack

Start with recommended coverage, then tune individual monitors.

Application

HTTP status, latency, content assertions, and response headers.

HTTP monitoring

Questions

SiteCanary FAQ

What does SiteCanary monitor?

SiteCanary monitors HTTP endpoints, browser performance, accessibility, JavaScript errors, DNS, TCP, TLS, and SSH.

How is SiteCanary different from a basic uptime monitor?

It combines availability checks with response assertions, browser measurements, accessibility scans, infrastructure diagnostics, configuration drift, and bounded long-term history.

How long does SiteCanary retain monitoring data?

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.

Can SiteCanary monitor authenticated applications?

Yes. Reusable authentication flows can obtain cookies, bearer tokens, API keys, basic-auth credentials, or custom headers before supported application checks run.

How is SiteCanary deployed?

Deployment is environment-driven and includes a documented Linux VPS workflow. Availability and commercial packaging depend on the operator providing the service.

Explainable alerts

Know what changed

Thresholds and drift rules create clear alerts that reach the right recipients.

  1. 1
    Detect

    A monitor crosses a threshold or finds configuration drift.

  2. 2
    Explain

    Run details show the failed assertion and observed values.

  3. 3
    Route

    The alert is recorded and sent to configured recipients.

Start simply

Start with one URL.

Create recommended coverage, then adjust each monitor as your needs grow.

Start monitoringView docs