Core Concepts
The key building blocks of OpsKitty and how they fit together.
- Website
- A logical container that maps to a domain or service you own (e.g.,
example.com). Websites group related endpoints together and appear as components on your status page. You can enable or disable a website to pause all its checks at once. - Endpoint
- A specific target to monitor — a URL, IP:port, hostname, or DNS record. Each endpoint has a type (HTTP, TCP, DNS, ICMP, SSH), a check interval, and a timeout. OpsKitty checks each endpoint independently on its own schedule from one or more regions.
- Check
- A single monitoring result produced when OpsKitty contacts an endpoint from one region at one point in time. A check records the status (success or failure), response time in milliseconds, HTTP status code, error message on failure, region, and timestamp. Checks are stored and used to compute uptime percentages and feed alert rules.
- Alert
- A rule that connects an endpoint to a notification channel. An alert fires when the endpoint fails a configurable number of consecutive times (failure threshold) and resolves when it recovers a configurable number of times in a row (success threshold). Supported channels include email, Slack, Discord, PagerDuty, Telegram, Microsoft Teams, webhook, Twilio, and OpsGenie.
- Status Page
- A public webpage showing the real-time health of your services. Each organization gets one status page. You add components mapped to your endpoints or groups that display their current status: operational, degraded performance, partial outage, or major outage. Incidents can be posted and updated as timeline entries to keep users informed during downtime.
- Organization
- A workspace that contains all your websites, endpoints, alerts, and team members. Organizations are fully isolated — billing, settings, and data are separate between orgs. A single user account can belong to multiple organizations, making it easy to manage monitoring for different clients or projects.
- Regions
- Geographic locations from which OpsKitty dispatches checks. Running checks from multiple regions eliminates false positives caused by transient local network issues — if only one region reports a failure, it is likely not a real outage. The number of available regions scales with your plan: 1 region on Free, up to 20 on Enterprise.
How they connect
An organization contains one or more websites. Each website has one or more endpoints. OpsKitty runs checks on every endpoint at its configured interval from one or more regions. When consecutive checks fail, alerts fire notifications to your team. Your public status page reflects the aggregate health of all components in real time.