Peekaping Self-Hosted Uptime Monitor

AWS Observability

peekaping, the open source, self hosted uptime and status monitor: watch websites, APIs, TCP services and DNS with heartbeat history and public status pages, secured on first boot by cloudimg.

Base
Hardened build
minimal ports, security patches applied at build time
Access
Unique credentials
generated on first boot, readable only by root
Verified
Boots working
services pass a health gate before release
Support
24/7, 365 days
by email and live chat, 24 hour response SLA

Overview

Peekaping is an open source, self hosted uptime and status monitoring system and a modern alternative to Uptime Kuma. It watches your websites, APIs, TCP services and DNS records, records a heartbeat for every check, calculates uptime statistics over time, publishes status pages your users can subscribe to, and sends alerts through notification channels, all from a clean web interface you run yourself rather than a hosted service. The stack is the official upstream topology: a Go API and web interface with a bundled PostgreSQL database and Redis queue, so a working monitoring console is ready as soon as the instance is up. It suits developers, operators and small teams who want a self owned view of whether their sites and services are up.

Why the cloudimg image

cloudimg ships Peekaping as the official upstream container stack behind nginx, ready on first boot. Peekaping accepts an administrator registration only while none exists, which on a public server is a race an attacker can win, and cloudimg closes it: on each instance's first boot, before the port is reachable, a unique administrator password, database password and cache password are generated, fresh session signing keys are minted into an empty database, and the image verifies that a further registration is refused. The database, cache and container images live on a dedicated, independently resizable data volume, and every deployment comes with a paired deployment guide and 24/7 cloudimg support.

Common uses

  • Monitor websites and API endpoints with heartbeat history and uptime statistics
  • Publish a public status page for your users and stakeholders
  • Alert on downtime through notification channels for a self owned service

Key features

  • Production-ready uptime monitoring from first boot: launch this AMI and have a fully operational Peekaping console serving in minutes. Monitor HTTP, TCP, ping and DNS endpoints with heartbeat history, uptime statistics, public status pages and configurable notification channels - no manual Docker, Compose, PostgreSQL, Redis or reverse proxy setup required. Ideal for SaaS teams tracking API health or DevOps engineers consolidating monitoring into a single self-hosted platform they fully control.
  • Zero-trust security generated automatically per instance: every launch creates unique administrator, database and cache passwords, mints fresh session signing keys into an empty database, and closes self registration before the port is reachable. No default credentials ever exist in the image and no secret is shared between instances, eliminating the first-boot administrator race condition that affects manual deployments of Peekaping and similar tools.
  • Hardened network topology with dedicated storage and 24/7 support: only SSH and the nginx web interface are exposed while the Go API, PostgreSQL and Redis remain on loopback or inside a private container network. All stateful data lives on a dedicated, independently resizable EBS disk separate from the OS volume. Backed by 24/7 cloudimg engineering support for deployment, TLS termination, notification integration, backup planning and scaling.

See it running

Real screenshots taken while testing this image against its deployment guide.

Peekaping Self-Hosted Uptime Monitor screenshot 1 Peekaping Self-Hosted Uptime Monitor screenshot 2 Peekaping Self-Hosted Uptime Monitor screenshot 3

Description

This is a repackaged open source software product wherein additional charges apply for cloudimg support services.

# Overview Peekaping is an open source, self-hosted uptime and status monitoring system and a modern alternative to Uptime Kuma. It watches your websites, APIs, TCP services, DNS records and more, records a heartbeat history for each check, calculates uptime statistics over time, publishes status pages your users can subscribe to, and sends alerts through notification channels - all from a clean web interface running inside your own AWS account. This image delivers Peekaping fully installed and running as the official upstream container stack, so a working monitoring console is serving within minutes of launch. ## Who This Is For A SaaS operations team monitoring dozens of API endpoints and publishing a customer-facing status page. A DevOps engineer at a mid-size e-commerce company consolidating uptime checks that previously ran across multiple free-tier tools. A platform team tracking hundreds of microservices that needs full data ownership without vendor lock-in. If you need reliable, self-hosted monitoring without cloud dependencies, this AMI gets you there without the setup burden. ## Why This Image Instead of Self-Deployment Deploying Peekaping by hand means installing Docker, wiring up an eight-container Compose topology, standing up PostgreSQL and Redis, generating secrets, configuring a reverse proxy and solving the first-run administrator race before an attacker does. This image removes that burden: every component is pre-configured and tested, all secrets and the administrator account are generated automatically on first boot, stateful data lives on a dedicated resizable disk, and the full stack starts on boot via systemd. You skip hours of setup and go straight to adding your first monitor. ## What Is Included - Peekaping (MIT licensed) with every container pinned by image digest

  • Bundled PostgreSQL and Redis, pinned by digest, reachable only inside a private container network
  • Docker Engine with the Go API and React web interface behind nginx on port 80
  • Unique administrator password, database password and cache password generated per instance on first boot
  • Fresh session signing keys minted into a brand new database
  • Self registration closed on first boot so nobody can claim the administrator account ## Application Stack The appliance runs the official Peekaping topology under a single systemd service: a Go API and socket.io server, a monitor scheduler, a check worker and a heartbeat ingester, a React single-page web interface, a one-shot database migrator, and a bundled PostgreSQL database and Redis queue. Host nginx on port 80 is the sole public entry point and routes API and socket.io traffic to the loopback API while serving the web interface same-origin. Every stateful Docker volume - the database, the cache and the pinned images - lives on a dedicated, independently resizable EBS data disk kept separate from the operating system disk. ## Secure First Boot Peekaping accepts a registration only while no administrator exists, which on a public server is a race an attacker can win. This image closes it: on the first boot of your instance, before the port is reachable, a unique administrator is created with a per-instance password, and the image then verifies that a further registration attempt is refused. No shared or default password ships in the image, the database initialises empty, and the session signing keys are unique per instance. The administrator credentials are recorded in a file that only the root user can read. ## Getting Started 1. Launch the AMI and wait for the instance to reach a running state

2. Retrieve the generated administrator password over SSH

3. Open the console in your browser and sign in

4. Add your first monitor, watch its heartbeat history and uptime, and publish a status page The unauthenticated health endpoint also serves as a probe for load balancer and uptime checks. ## Evaluation Path To evaluate Peekaping at minimal cost, launch on a small instance type, add a handful of monitors, and explore the dashboard, status pages and notification channels. The full feature set is available immediately with no feature gating. ## cloudimg Support 24/7 technical support by email and chat. Our engineers help with deployment, reverse proxy and TLS termination, notification integration, backup and storage planning, and scaling. Book a free deployment walkthrough by contacting our team to get guided onboarding for your environment. Note that upstream describes Peekaping as beta software under active development. All product and company names are trademarks or registered trademarks of their respective holders. Use of them does not imply any affiliation with or endorsement by them.

Related technologies

uptime monitoringstatus pageself hosted monitoringuptime kuma alternativewebsite monitoringheartbeat monitorhttp monitordns monitortcp monitornotification alertsopen source monitoringdocker compose amiapi monitoring