Uptime Kuma Monitoring

Self-host uptime monitoring with a public status page and alerts, at a flat cost for any number of sites.

A complete recipe for self-hosting an open-source uptime monitor on a single low-cost server, with a database backend, a reverse proxy with TLS, a public status page, and alerts over Telegram, Slack or email with a full incident lifecycle. From one dashboard you watch the HTTP health, response latency, TLS certificate expiry, DNS resolution and open ports of every site you operate, for a flat monthly cost instead of per-site SaaS pricing, and the data stays on infrastructure you own.

$15 one-time
Add to a kit →

Prices include 20% VAT. · Forged on real agency work · one-time, no lock-in

  • Type Skill
  • Category DevOps & Infra
  • Delivery Email · instant
  • License One-time
Run preview
forgehouse, uptime-kuma-monitoring

Inside the run · no black box

See the actual work before you buy it.

Finding out about downtime from a customer is unacceptable. This recipe stands up a monitor you own, watching every site from one dashboard:

  1. Deploys the uptime monitor with a database backend behind a reverse proxy with TLS as a container stack
  2. Adds HTTP, keyword, TLS, DNS and port checks per site, with latency tracking and a response-time threshold
  3. Tunes alerting to fire only after several consecutive failures and to suppress during maintenance windows
  4. Publishes a public status page with an incident timeline, and routes alerts to Telegram, Slack or email
  5. Provides an SLA-report query and an incident-postmortem discipline for when it went down, what was done and what was learned
Use cases · what happens when you plug it in

One power source. 6 lines out.

uptime-kuma-monitoring · core

core active · 6 lines

  1. Watching the health of every site you operate from one dashboard

    ✓ watching the health of e…
  2. Getting a downtime alert before a client or a social post tells you

    ✓ getting a downtime alert
  3. Publishing a public status page as a trust signal

    ✓ publishing a public status
  4. Alarming on TLS certificate expiry well before it lapses

    ✓ alarming on tls certific…
  5. Reporting a monthly uptime percentage in a client report

    ✓ reporting a monthly uptime
  6. Running incident postmortems with a clear timeline

    ✓ running incident postmor…
Benefits · what you walk away with

Yours to keep.

Drag time forward. Watch what stays.

Forever

That's what owning means.

The rented stack

ai writing tool: subscription

expired · access lost

analytics suite: subscription

expired · access lost

design platform: subscription

expired · access lost

(nothing left)

Your forge

  1. One flat monthly cost no matter how many sites you watch

    license: perpetual
  2. Alerts reach you before customers notice the outage

    license: perpetual
  3. A public status page reassures visitors and clients

    license: perpetual
  4. Your monitoring data stays on infrastructure you own

    license: perpetual

subscriptions expire · deeds don't

What's included · the full manifest

Everything in the box.

Pick a piece up. Watch it work.

A production container stack with a database backend and reverse proxy

part 01 of 06 · in the box

6 parts · one working system · ships instantly by email

Who it's for

This wasn't forged for everyone.

  • Not for you if you'd rather rent a tool than own one.
  • Not for you if you want someone else to run your stack.
  • Not for you if you're happy guessing.
Still here? Good.

Teams operating multiple sites who want one self-hosted monitor, a public status page and reliable alerts at a flat cost.

then this was forged for you.

Works with

Universal by design: these run in any AI. Delivered in the open Agent Skills + MCP format (native in Claude); ChatGPT, Gemini, Cursor and Copilot adapt the same files their own way.

  • Claude Native format
  • ChatGPT Adapts via open standards
  • Gemini Adapts via open standards
  • Cursor Adapts via open standards
  • Copilot Adapts via open standards
Questions · still in the air

Catch what's on your mind.

the air is clear. nothing between you and the forge.
catch a spark: the forge will answer

  1. Why self-host instead of a monitoring SaaS?

    Per-site SaaS pricing scales with the number of sites, while a self-host runs at a flat server cost no matter how many you watch. Once you monitor more than a handful, the self-host pays off, and the data stays on your own infrastructure.

  2. How does it avoid waking me for a brief blip?

    It alerts only after several consecutive failures, since a single failure is usually a transient network glitch. It also suppresses alerts during maintenance windows and flags flapping monitors instead of paging on each flip.

  3. Can clients see the status?

    Yes. A public status page shows current health, an incident timeline and planned maintenance, which acts as a trust signal, while the edit side stays protected behind authentication.

  4. How is it delivered?

    By email right after purchase: ready to run, downloaded instantly, no setup wait.

  5. One-time or subscription?

    A one-time purchase; no subscription or hidden fees. VAT (20%) is included.

  6. Can I get a refund?

    As a digital product, it can’t be refunded once downloaded. That’s why we show exactly what’s inside and who it’s for, right here.