Peekaping
by Peekaping · Self-hosted uptime monitoring for websites, APIs and infrastructure
BenchRank score
Screenshots of Peekaping
Homepage
Overview
Peekaping is a self-hosted uptime monitor written in Go with a React and TypeScript dashboard, deployed with Docker. It checks HTTP/HTTPS, TCP, ping, DNS, gRPC, SNMP, Docker containers, databases and message brokers, and sends alerts through email, webhooks, chat tools and on-call services. It publishes public or private status pages and stores data in SQLite, PostgreSQL or MongoDB.
- Best for
- Small teams that want to run their own uptime monitoring for websites, APIs and infrastructure.
- Pricing
- No prices are shown; the page describes the project as 100% open source and self-hosted, so hosting costs are your own.
- Runs on
- Self-hosted
Strengths and trade-offs
Strengths
- Checks HTTP, TCP, ping, DNS, gRPC, SNMP, Docker and databases
- Alerts via Slack, Telegram, email, webhooks, PagerDuty, ntfy
- Storage is selectable: SQLite, PostgreSQL or MongoDB
- Runs entirely in your environment, with data kept on your server
Trade-offs
- Self-hosted only; the page says no hosted option exists yet
- You supply and maintain the server, database and upgrades
- Early-stage project: 1.2K GitHub stars and few testimonials
How Peekaping markets itself
A structured read of the promise, proof and page design on Peekaping’s captured homepage.
Homepage capture
“Open Source & Self-Hosted uptime monitoring for small teams to catch outages before users do”
- Angle: Open source / ownership
- Hero: Product screenshot
Pricing
Published plans and prices from Peekaping’s own pricing page.
How this score is made up
Each dimension is scored out of 100 and combined into the headline score using fixed weights.
MCP support
Whether an agent can drive the product through the Model Context Protocol, and how much setup that takes.
API quality
Public API surface: machine-readable spec, official SDKs, documented auth, errors, rate limits and versioning.
Documentation
Publicly reachable docs — coverage, freshness, code samples and machine readability.
Agent friendliness
How readable the site is to an automated client: llms.txt, structured data, server-rendered content, crawler access.
Changelog
A public, dated record of what shipped and when — the clearest signal that a product is still alive.
Marketing site structure
Whether the site answers a buyer's questions: clear positioning, the pages that matter, and accessibility.
Page speed
How fast the site loads for real visitors: Chrome UX Report 75th-percentile LCP, INP and CLS, with a Lighthouse mobile run standing in where a site has too little traffic for field data.
Operational trust
Status page and incident history, security disclosure, compliance and data-processing documentation.
Measured, but not part of the score
Useful to know, but not a mark for or against the product — so these do not affect the ranking.
Openness
Source availability, self-hosting, data export and open standards. Scored and shown, but not part of the composite — paid SaaS is not worse for being paid SaaS.
Maintenance
Release cadence and repository activity. Scored and shown, but not part of the composite — it is only measurable for open repositories.
This doesn’t look right — report a problem with Peekaping’s score
Where this comes from
The Peekaping pages BenchRank reads when it scores the product — its documentation, release notes, status and security pages, and its repository where there is one.
Alternatives in Monitoring & Observability
Ranked 1
87.4 — BenchRank score out of 100openstatus
OpenStatus · Open source status pages with uptime monitoring from 28 regions
Best for: Teams that need a public status page and uptime checks while working towards SOC 2.
Ranked 2
86.7 — BenchRank score out of 100OneUptime
OneUptime · Open-source observability and incident management on one platform
Best for: Teams wanting monitoring, on-call, status pages and observability on one open-source platform
Ranked 3
83.1 — BenchRank score out of 100Sentry
Sentry · Error tracking and application performance monitoring for developers
Best for: Development teams wanting error monitoring, tracing and session replay tied to one trace
Is this your product?
Claim Peekaping to manage its profile. Claiming lets you suggest edits to the descriptive fields — it never changes scores or rankings.