Welcome to KEEPitALIVE

KEEPitALIVE monitors the workflows and services that usually fail quietly: APIs, web apps, cron jobs, heartbeats, TCP services, DNS records, and game servers. It combines checks, incidents, triggers, notifications, public status pages, embeds, and API access into one operational loop.

THE LOOP

• Observe: create monitors for the signal you actually have - poll an endpoint, open a TCP socket, query DNS/game servers, or receive heartbeats/events.
• Decide: each check becomes a normalized state: up, degraded, down, maintenance, or paused.
• Record: incidents track when something started, why it opened, how long it lasted, and how it resolved.
• Notify: route state changes to email, in-app, Discord, Slack, Teams, Telegram, PagerDuty, Pushover, FCM, WebPush, and more.
• Automate: triggers react to transitions or payload conditions, call webhooks, send custom notifications, and open/auto-close incidents.
• Share: publish sanitized status pages, single-monitor embeds, SVG badges, or read-only API views.

WHAT YOU GET

• Seven monitor families: HTTP/API, Browser, Ping, TCP, DNS, Heartbeat/Event Receiver, and Game Server checks.
• Real-time dashboard, group overview, per-monitor detail, latency charts, check history, incidents, and activity feed.
• Payload-aware triggers with expression rules, signed webhook delivery, notify actions, and trigger-owned incidents that auto-resolve when conditions clear.
• Public status pages, private sharing, watch lists, monitor embeds, SVG badges, and JSON status endpoints.
• Scoped API keys for scripts, CI/CD, internal tools, and autonomous agents.

WHERE TO GO NEXT

• Start with "Monitor Types" if you are deciding what kind of monitor to create.
• Use "Quick Start" for the shortest path from account setup to a useful dashboard.
• Use "Heartbeat" for cron jobs, deploy pipelines, background workers, and event receivers.
• Use "Triggers", "API", and "Notifications" when you want KEEPitALIVE to operate with your existing tools.