Overwatch: uptime and infrastructure monitoring service

​

What Overwatch monitors

• HTTP — requests your URL and reports the status code, latency, and whether the response is up, degraded, or down.
• TCP — opens a socket connection to any host and port, without requiring HTTP.
• TLS — inspects the SSL certificate on a domain and warns you before it expires.
• DNS — validates that a DNS record is present, missing, or has changed from a known-good state.
• Scheduled (heartbeat) — expects your cron job or background task to ping a unique URL on a schedule; alerts you if it runs late or stops checking in entirely.

​

Key features

• Uptime checks — HTTP, TCP, TLS, and DNS checks on a regular interval, depending on your plan.
• Cron job monitoring — heartbeat-based tracking for scheduled tasks with configurable expected intervals and grace windows.
• SSL certificate tracking — proactive expiration warnings so certificates never silently expire.
• Multi-channel alerts — route notifications to Slack, Discord, Microsoft Teams, email, or a generic webhook. PagerDuty and SMS support are coming soon.
• Team collaboration — invite colleagues and assign roles (owner, admin, viewer) to control who can manage monitors and alert channels.
• REST API — create monitors, manage alert channels, and query org-level status programmatically using API keys.
• Open-source core — the monitoring worker is MIT-licensed and available to self-host for free.

​

Plans

​

Where to go next