Better Stack (Uptime)
Uptime monitoring and incident management service that alerts teams when websites or services go down
Peekaping
Modern self-hosted uptime monitoring with Go and React
Self-hosted uptime monitoring for websites, APIs, and services. Features 16+ monitor types, 24+ notification channels, status pages, and SSL tracking—built with Go and React.
Overview
Modern Uptime Monitoring for Self-Hosted Environments
Peekaping is a feature-rich uptime monitoring system designed for teams and developers who need reliable, customizable infrastructure monitoring. Built with Go on the backend and React on the frontend, it delivers high performance with a small footprint while maintaining strong type safety and extensibility.
Comprehensive Monitoring Capabilities
Monitor HTTP/HTTPS endpoints, TCP services, DNS, Docker containers, gRPC, SNMP, and databases including PostgreSQL, MongoDB, MySQL, Redis, and SQL Server. Push monitors accept incoming webhooks, while specialized monitors track MQTT brokers, RabbitMQ, and Kafka producers. Integrate alerts across 24+ channels including Slack, PagerDuty, Telegram, Discord, email, and Opsgenie.
Deployment and Architecture
Deploy via Docker with SQLite for single-instance setups or scale with PostgreSQL and MongoDB backends. The strongly typed, modular codebase enables developers to add custom monitor types, notification channels, or swap database layers without major refactoring. Public status pages, SVG badges, MFA, and brute-force protection are built in.
Note: Peekaping is currently in beta. Test in non-production environments and report issues to help drive stability.
Highlights
16+ monitor types: HTTP, TCP, Ping, DNS, Docker, gRPC, databases (PostgreSQL, MySQL, MongoDB, Redis), and message queues
24+ notification channels including PagerDuty, Slack, Opsgenie, Telegram, Discord, and email
Public status pages with SVG badges, SSL certificate expiration tracking, and MFA
Strongly typed Go/React architecture designed for extensibility and custom integrations
Pros
- Extensive monitor and notification channel coverage out of the box
- Lightweight Go backend with small resource footprint and high performance
- Modular, strongly typed codebase simplifies adding custom monitors and channels
- Flexible deployment: Docker with SQLite, PostgreSQL, or MongoDB
Considerations
- Currently in beta; features may change and stability is not production-guaranteed
- Smaller community and ecosystem compared to mature alternatives like Uptime Kuma
- Multi-user support, access levels, and incident management are still on the roadmap
- Migration tooling from other platforms (e.g., Uptime Kuma) is not yet available
Managed products teams compare with
When teams consider Peekaping, these hosted platforms usually appear on the same shortlist.
Looking for a hosted option? These are the services engineering teams benchmark against before choosing open source.
Fit guide
Great for
- Development teams needing extensible, type-safe monitoring they can customize
- Self-hosted infrastructure monitoring with diverse service types (databases, message queues, containers)
- Organizations requiring broad notification channel support (PagerDuty, Opsgenie, Slack, etc.)
- Early adopters comfortable testing beta software and contributing feedback
Not ideal when
- Production-critical environments requiring battle-tested, stable monitoring solutions
- Teams needing multi-user access controls, role-based permissions, or incident management today
- Organizations migrating from Uptime Kuma without manual reconfiguration
- Users seeking a mature plugin ecosystem or extensive third-party integrations
How teams use it
Multi-Database Health Monitoring
Track uptime and performance of PostgreSQL, MongoDB, MySQL, and Redis instances with unified alerting to Slack and PagerDuty.
Microservices and Container Oversight
Monitor Docker containers, gRPC endpoints, and HTTP APIs from a single dashboard with real-time notifications via Opsgenie.
Public Status Page for SaaS
Publish a branded status page with SVG badges to keep customers informed about service availability and SSL certificate health.
Message Queue and Broker Monitoring
Ensure RabbitMQ, Kafka producers, and MQTT brokers remain operational with automated alerts to Telegram and Discord.
Tech snapshot
Go58%
TypeScript35%
Astro3%
Shell2%
JavaScript1%
CSS1%
Frequently asked questions
Is Peekaping production-ready?
Peekaping is currently in beta. While functional, it is recommended for testing in non-production environments. Report issues to help drive stability toward a production release.
What databases does Peekaping support for its own backend?
Peekaping can run on SQLite (for single-instance deployments), PostgreSQL, or MongoDB. Choose the backend that fits your scale and infrastructure.
Can I migrate from Uptime Kuma to Peekaping?
A migration tool is on the roadmap but not yet available. Manual reconfiguration of monitors and notification channels is currently required.
Does Peekaping support multi-user access and role-based permissions?
Multi-user support, groups, and access levels are planned features but not yet implemented. MFA and brute-force protection are available for single-user deployments.
How do I add a custom monitor or notification channel?
Peekaping's strongly typed Go backend and modular architecture are designed for extensibility. Fork the repository, implement your custom module, and submit a pull request or deploy your own build.
Project at a glance
Active- Stars
- 1,003
- Watchers
- 1,003
- Forks
- 48
LicenseMIT
Repo age8 months old
Last commit3 weeks ago
Self-hostingSupported
Primary languageGo
Last synced 3 hours ago