> ## Documentation Index
> Fetch the complete documentation index at: https://docs.overwatchapp.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Overwatch: uptime and infrastructure monitoring service

> Overwatch monitors your websites, APIs, cron jobs, and SSL certificates with regular checks and multi-channel alerts for your whole team.

Overwatch is an infrastructure monitoring platform that runs continuous checks against your HTTP endpoints, TCP services, TLS certificates, DNS records, and scheduled jobs. When a check fails or a status changes, Overwatch fires an alert to the channels your team already uses — Slack, Discord, Microsoft Teams, email, or any webhook endpoint. This page covers what Overwatch does, who it is for, and how to choose the plan that fits your setup.

## What Overwatch monitors

Overwatch runs five types of checks:

* **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

| Plan           | Price         | Monitors  | Alert channels  | Team members | Check interval |
| -------------- | ------------- | --------- | --------------- | ------------ | -------------- |
| **Free (OSS)** | \$0 forever   | Unlimited | Email & webhook | —            | Custom         |
| **Starter**    | \$10 / month  | 10        | 1               | 1            | 5 minutes      |
| **Pro**        | \$200 / month | 200       | 5               | 5            | 1 minute       |
| **Enterprise** | Custom        | Unlimited | Custom          | Unlimited    | 10 seconds     |

All paid plans include a 14-day free trial with no credit card required. The Free plan is the self-hosted open-source binary — see [processfoundry/overwatch](https://github.com/processfoundry/overwatch) on GitHub to get started.

<Note>
  Log retention is 90 days on Starter and Pro. Enterprise plans include up to 2-year retention and a dedicated SLA.
</Note>

## Where to go next

<CardGroup cols={2}>
  <Card title="Quickstart" icon="rocket" href="/quickstart">
    Create your first monitor and alert channel in 5 minutes.
  </Card>

  <Card title="Core concepts" icon="book" href="/concepts">
    Learn how monitors, check results, statuses, and alert channels work together.
  </Card>

  <Card title="Monitors" icon="gauge" href="/monitors/overview">
    Configure HTTP, TCP, TLS, DNS, and cron job monitors in detail.
  </Card>

  <Card title="API reference" icon="code" href="/api-reference/authentication">
    Manage your setup programmatically with the REST API.
  </Card>
</CardGroup>