PulseKeep
Know when it goes down.
Switch between Google, GitHub, and Wikipedia below. The worker probes all three in the background. Latency lands on the chart.
Live console
Three popular public sites. The worker checks them every 30 seconds so the latency graph fills in on its own. Check now still runs an extra probe.
- HTTP + keyword
- Retry before down
- Check now
- Telegram / email
- Charts + zoom
- Incidents
- SSL expiry
- Domain expiry
- Pause / resume
- Public status
How it works
After signup, the real worker does this on a schedule.
Add a URL
Name it, set expected status, optional keyword, choose alert channels.
Worker sweeps
Background process checks due monitors, stores latency, opens incidents.
Get signaled
Telegram and/or email on down and recovery. Expiry warnings near SSL/domain brink.
Share status
Clients open your public status URL while you dig into charts and incidents.
Stack
Next.js App Router for UI and API, Postgres with Drizzle, Better Auth for sessions, and a separate Node worker under systemd. Deployed on Hetzner with Nginx and Let's Encrypt.
- Next.js
- TypeScript
- React
- Postgres
- Drizzle
- Better Auth
- Node worker
- Telegram Bot API
- RDAP + TLS
- Nginx / Hetzner