Back to browse
Pongo – a self hosted uptime monitor using configuration as code

Pongo – a self hosted uptime monitor using configuration as code

by linesofcode·Feb 25, 2026·1 point·2 comments

AI Analysis

●●●BangerShip ItSolve My ProblemSlick

Config-as-code uptime monitoring beats dashboard vendor lock-in with git-driven workflows.

Strengths
  • TypeScript + Bun stack optimizes for developer velocity and quick iteration
  • Version-controlled alerts mean PR review before deployment, full git history
  • Multi-region redundancy and dual persistence (SQLite/PostgreSQL) scales from hobby to production
Weaknesses
  • Crowded uptime monitoring market (Uptime Robot, Betterstack, Pingdom dominate)
  • Early project: no clear evidence of community adoption or battle-tested reliability claims
Target Audience

Backend developers, DevOps engineers, teams preferring infrastructure-as-code patterns

Similar To

Uptime Robot · Betterstack · Grafana Cloud

Post Description

Say hello to https://pongo.sh/

self-hosted uptime monitoring, configured entirely in TypeScript and built on NextJS and Bun.

No UI forms. No vendor lock-in. Just code in your repo.

Monitors, dashboards, alerts, incidents, and status pages — all defined as TypeScript files and Markdown, version-controlled alongside your application.

You can one-click deploy it to Vercel or anywhere you can run node/bun/docker.

Your monitoring config lives in your repo like everything else.

Want to know what's monitored and why? Read the code.

Need to review a change? It's in the PR. Need to roll back a bad alert? Git revert.

No more clicking through dashboards wondering who changed what and when.

Built with Next.js, Drizzle ORM, and Bun. Runs with SQLite for simplicity or PostgreSQL for production.

Fully open source and ready to use today.

Would love to hear what you think and what features you'd want to see next, leave a star on GitHub

https://github.com/TimMikeladze/pongo

Similar Projects