# 0xfurai/peekaping

Open Source Uptime Kuma Alternative

Repository: https://github.com/0xfurai/peekaping
Canonical: https://ross.abutalabs.com/products/peekaping
Homepage: https://peekaping.com
Language: Go
License: MIT
License Family: permissive
Topics: monitor, monitoring, self-hosted, selfhosted, telemetry, uptime, uptime-monitoring
Last push: 2026-05-24T21:20:21+00:00

## Health v2 (maintenance only)
Score: 72/100 (v2, computed 2026-09-03T02:20:16.233290+00:00)
- activity 84, release rhythm 78, longevity 32
- inputs: {"age_days": 457, "days_push": 101, "days_rel": 145, "gap_med": 0.5, "n_releases_24m": 41}
- flags: none
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 1179, forks 68 (observed 2026-08-28T04:03:53.243580+00:00)

## What it is
Peekaping is a self-hosted, open-source uptime monitoring system built with Go and React, offering HTTP/TCP/ping/DNS/database/Docker checks, alert notifications, and public status pages. It is an API-first alternative to Uptime Kuma designed for automation and DevOps workflows, currently in beta.

## Use cases
- monitor website and API uptime
- self-hosted uptime monitoring alternative to Uptime Kuma
- get alerts when a service goes down
- publish a public status page for my services
- monitor docker containers and database health
- integrate uptime checks into CI/CD via API
- check tcp port and dns availability

## When to choose
- you want an API-first, automation-friendly uptime monitor for IaC/CI-CD integration
- you need flexible storage backends (SQLite, PostgreSQL, MongoDB)
- you want a lightweight Go-based monitor with low resource usage
- you need many monitor types (HTTP, TCP, ICMP, DNS, gRPC, MQTT, Kafka) and alert channels
- you prefer self-hosted monitoring with no vendor lock-in

## When to avoid
- you need battle-tested production stability - it is in beta
- you want a mature ecosystem with long-term plugin support
- you need full observability (metrics, logs, traces) rather than uptime checks
- you prefer a managed cloud monitoring service

## Facets
- artifact type: application
- maturity: active
- function: monitoring, alerting, http-client, webhook, api-framework, self-hosted
- domain: monitoring, self-hosted, networking, analytics
- platform: self-hosted, go, cross-platform
- tags: uptime-monitoring, status-page, uptime-kuma-alternative, heartbeat, incident-alerting, api-first, devops, docker, linux, web-server

## Member repositories
- 0xfurai/peekaping (main) score 72

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:03:53.243580+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-30T06:25:24.162266+00:00, confidence not recorded.
  - readme: https://github.com/0xfurai/peekaping (fetched 2026-08-28T04:03:53.243580+00:00, sha 79fba35bc443)
  - homepage: https://peekaping.com (fetched 2026-08-29T12:32:15.919192+00:00, sha 8f5e5d82902f)
  - site_page: https://docs.peekaping.com (fetched 2026-08-29T12:32:15.921880+00:00, sha 714221fa4d59)
- Data as of 2026-08-30T08:39:29.467469+00:00.
