At a Glance:
Peekaping is a self-hosted, API-first uptime monitoring system built with Golang and React that supports multiple monitor types, alert channels, status pages, and storage backends including SQLite, PostgreSQL, and MongoDB.
Overview:
Peekaping is an open-source uptime monitoring solution that tracks the availability and health of websites, APIs, databases, and other services through a range of protocol-level and application-level monitors. It is built as an API-first system with a Golang server and React frontend, designed for teams that need programmatic access to all monitoring functions. The project includes flexible storage options across SQLite, PostgreSQL, and MongoDB, and it exposes monitoring status through public status pages and SVG badges. Alerting is supported across more than 20 notification channels, including email, Slack, Telegram, Discord, PagerDuty, and Opsgenie. Peekaping is currently in beta and actively developed.
Key Decision Points:
API-first architecture: All system functions are accessible through a RESTful API, which the README states is designed for integration with CI/CD processes and Infrastructure as Code tools.
Self-hosted deployment: The project provides Docker-based setup instructions with SQLite as the default storage, and also documents support for PostgreSQL and MongoDB backends.
Storage flexibility: Three database options are available — SQLite, PostgreSQL, and MongoDB — allowing deployment to match existing infrastructure.
Beta status: The software is in active development and explicitly recommended for non-production testing first, with caution that some features may change.
Extensibility model: The server architecture is described as modular, allowing new monitor types and notification channels to be added without modifying the core codebase.
Core Features:
HTTP/HTTPS monitoring: Monitor website and API endpoint availability and response.
TCP, Ping, DNS, and gRPC monitors: Check network-level and protocol-level service health.
Database and broker monitors: Monitor PostgreSQL, MySQL/MariaDB, MongoDB, Microsoft SQL Server, Redis, MQTT, RabbitMQ, and Kafka Producer connectivity.
Docker container and SNMP monitoring: Track container status and network device metrics.
Push monitor: Accept incoming webhook pings for passive monitoring scenarios.
Alert channels: Send notifications through Email, Webhook, Telegram, Slack, Discord, PagerDuty, Opsgenie, Signal, Matrix, WhatsApp, and more.
Use Cases:
DevOps teams can use Peekaping as a self-hosted monitor for production services and infrastructure, with all alerting and configuration accessible via API for integration into existing toolchains.
System administrators can deploy Peekaping with PostgreSQL or MongoDB storage to monitor database instances, Docker containers, and network endpoints from a single dashboard.
Open-Source Alternative Value:
Peekaping is presented as an open-source alternative to Uptime Kuma, with a focus on API-first design and a Golang-based server for lower resource consumption. The project provides public status pages, SVG status badges, multi-factor authentication, and brute-force login protection. Its modular server architecture aims to simplify extending monitor types and notification channels. Storage flexibility across SQLite, PostgreSQL, and MongoDB allows the monitoring system to be adapted to different deployment environments. The project is MIT-licensed and available as source code for self-hosted use.
