Peekaping

Peekaping is an open-source, self-hosted uptime monitoring solution.

  • Monitoring & Logging
Peekaping is an open-source, self-hosted uptime monitoring solution. It checks your websites, APIs, databases and message queues, alerts your team through the channels they already use, and publishes status pages for your users. A modern, API-first alternative to Uptime Kuma built with Go and React, it runs on your own server and keeps your data in SQLite or PostgreSQL.

Platform availability

Available on 1 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

65/100 Good

Maintained
84last commit 4 days ago
Popular
621,231 GitHub stars
Easy to install
251 install platform, install notes
Light to run
No data
Security check
70no serious findings, 8 minor, CI, tests

Based on 4 of 5 factors.

Availability: platform listings confirmed today

GitHub stars
1,231
Open issues
66
Last commit
2026-11-18
Latest release
0.1.0
License
MIT
Activity
declining

Checked today - source: GitHub (0xfurai/peekaping)

Resources & Compatibility

Requirements not published yet.

Checked today - source: Docker Hub image tags and published docs

First-install notes

  • Start Docker on port 8383 Use the docker run command so port 8383 is open for the web app. Also keep the peekaping volume safe, or your saved settings and probe data can disappear when the container is removed. source
  • Fill in .env before starting Copy the example settings file, .env.prod.example, to .env and fill in the required values before starting Peekaping. Missing or wrong settings can stop the app from starting or make it point to the wrong database. source
  • Check api and probe are running After running docker compose up -d, run docker compose ps to confirm both the api and probe services are healthy. The probe waits for the api, so if the probe is not running Peekaping may not show as online. source
  • Beta status Peekaping is in active beta; try it outside production first and report any issues you find. source

Fetched today - each note links to its source

Alternatives (8)

  • Atlassian Statuspage
  • Better Stack - AI-driven monitoring platform providing incident management, real-time logs, uptime, traces, error tracking, infrastructure analytics, and…
  • PagerDuty - Cloud-based platform offering full-stack monitoring, incident response, event intelligence, and real-time collaboration to streamline disru…
  • Uptime Kuma - Uptime Kuma is an easy-to-use, self-hosted monitoring tool that tracks the availability of websites, APIs, network services, and Docker con…
  • UptimeRobot - Monitor up to 50 sites with 5-minute intervals for free.
  • Uptimepage
  • cachet - Cachet is an open-source, self-hosted status page system for publishing service health, maintenance windows, and incident updates to custom…
  • checkmate - Checkmate is an open-source, self-hosted infrastructure monitoring tool for self-hosters that tracks servers, websites, Docker containers,…

Checked today - source: AlternativeTo

Common questions

How should I enable HTTPS?

Put a reverse proxy in front of Peekaping. The container serves the web app and API on port 8383.

What docker volume should I preserve?

Keep the peekaping volume safe. It stores saved settings and probe data that can disappear when the container is removed.

Why might Peekaping not show as online in Docker Compose?

Check that the api and probe services are healthy after docker compose up -d. The probe waits for api, so if the probe is not running Peekaping may not show as online.

Can I upgrade an install that still uses MongoDB?

MongoDB storage was removed. Move the data to SQLite or PostgreSQL before upgrading.

What should I configure before starting from a .env file?

Copy the example .env file .env.prod.example to .env and fill in the required values. Missing or wrong settings can stop the app or point it to the wrong database.

Answers sourced from docs.peekaping.com, docs.peekaping.com, docs.peekaping.com, github.com

Community

Collected today - public community threads