Peekaping is a free, open-source, self-hosted uptime monitor built with Go and React that watches websites, APIs, databases, containers, and message brokers, then alerts through more than fifteen channels. It targets small teams that want to catch outages before users do while owning the whole stack, with live dashboards and public status pages included. The project is in beta and actively developed under the MIT license.[1][2][3]
Quick verdict
Small teams that want to own their uptime monitoring get the most from Peekaping: fifteen check types from HTTP to Kafka, fifteen-plus alert channels, and brandable status pages in one MIT-licensed Docker deployment. The decisive capability is breadth without a subscription, pairing network, database, and broker checks with live dashboards and maintenance windows. The material constraint is beta maturity plus full self-hosting responsibility, so teams with no ops capacity or production-stability requirements should choose a hosted SaaS instead. If you run Docker and want Uptime Kuma's workflow on a Go stack, start with Peekaping in non-production first.[1][2][3]
Key features
Fifteen monitor types Fifteen monitor types: HTTP/HTTPS, TCP, ping, DNS, push heartbeats, Docker containers, gRPC, and SNMP cover the network layer, while PostgreSQL, SQL Server, MongoDB, Redis, MQTT, RabbitMQ, and Kafka checks reach into databases and brokers.[1][2]
Fifteen-plus alert channels Fifteen-plus alert channels: email over SMTP, webhooks, Telegram, Slack, Discord, Signal, Matrix, Mattermost, Google Chat, WeCom, WhatsApp via gateway, PagerDuty, Opsgenie, Grafana OnCall, NTFY, Gotify, and Pushover, with retry logic and resend control against alert spam.[1][2]
Public status pages Public status pages: publish brandable pages per service group so customers check status themselves, removing the second subscription most teams pay a hosted status-page vendor.[1][2]
Live WebSocket dashboard Live WebSocket dashboard: real-time status updates, interactive charts, 24-hour uptime tracking, response-time history, and visual heartbeat history in one React admin view.[1]
Maintenance windows Maintenance windows: scheduled work suppresses alerts and marks the status page, so deploys and patching do not read as outages.[1]
Proxy and 2FA hardening Proxy and 2FA hardening: checks can route through HTTP proxies for segmented networks, and the admin login supports two-factor authentication once the watcher itself becomes a target.[1]
Three-database choice Three-database choice: SQLite for a single-file homelab setup, PostgreSQL for structured relational data, or MongoDB for document storage, with automatic cleanup of old heartbeat data.[1][2]
Documented REST API Documented REST API: a Swagger-described API plus push-monitor webhook endpoints let jobs report their own health and let operators script against monitoring state.[1]
Who will love it
Small teams owning their monitoring Small teams owning their monitoring who want Uptime Kuma-style checks on a Go stack with no subscription and no vendor lock-in.[1][2]
Operators consolidating checks and status Operators consolidating network, database, and broker checks plus a public status page into one self-hosted dashboard.[1][2]
Homelab owners starting small Homelab owners starting small with Docker and SQLite, with PostgreSQL or MongoDB available when the setup grows.[1][2]
Who should avoid it
Teams with nobody to run it Teams with nobody to run it: you own hosting, backups, upgrades, and the monitor's own availability, so a hosted SaaS fits better when ops time is zero.[1][2]
Production-aged guarantees seekers Production-aged guarantees seekers: the docs carry a beta warning with incomplete features possible, so environments needing proven stability should wait or test in non-production first.[1]
Beyond-uptime observability needs Beyond-uptime observability needs: Peekaping checks reachability and health, not full metrics, traces, or log analytics, so teams needing those should pair or choose a broader platform.[1][2]
Alternatives and compatibility
Competes with Uptime Kuma Competes with Uptime Kuma: the repository calls itself an Open Source Uptime Kuma Alternative and the docs position it as the modern option, covering the same self-hosted checks, notifications, and status pages on a strongly typed Go and TypeScript architecture.[1][2]
Complements incident response Complements incident response: PagerDuty, Opsgenie, and Grafana OnCall channels hand off to existing on-call rotations rather than replacing them, while webhooks and the REST API feed wider automation.[1][2]
Questions worth asking
What is the best Peekaping alternative for non-technical users?
Is Peekaping really no-code?
How much does Peekaping cost per month?
Sources and editorial review
Source research. Reviewed on October 12, 2026. Written by Sanjib Sah. AI assisted; reviewed by a human editor.
We have not run or tested this product.
- Peekaping homepage (official)
official · Observed October 12, 2026
Official homepage: self-hosted-only positioning, 15 monitor types, 17 listed alert channels, selectable databases, Go/React stack, Docker quick-start, demo, repo link.
- Peekaping docs welcome (official)
official · Observed October 12, 2026
Official docs: beta status, dashboard, notifications, status pages, maintenance windows, proxy, 2FA, retention, architecture, Uptime Kuma positioning.
- Peekaping repository (official)
official · Observed October 12, 2026
Official repository: Uptime Kuma Alternative description, MIT license, Go, 1203 stars, release 0.0.46, active development signals.
Compared with these products
No explicit proprietary baseline is recorded.