01

Lightweight Remote Agents

The agents are plain scripts (Bash, Python, PowerShell, and ash on OpenWrt) that need nothing beyond their interpreter and curl. Cron starts them, they send one report and exit.

  • Short Install: On Linux and OpenWrt download, register with a token and add to cron; on Windows a scheduled task, in Docker one container.
  • Secure Communication: Agents establish outgoing connections and push telemetry data securely via HTTPS.
  • System Metrics out-of-the-box: Gathers real-time CPU utilization, RAM usage, storage loads, and network activity.

$ ./agent.sh --register YOUR_REGISTRATION_TOKEN https://YOUR-DOMAIN/status/agent_api.php

Registruji nového agenta na https://YOUR-DOMAIN/status/agent_api.php...

OK: Agent byl úspěšně zaregistrován a nastavení bylo uloženo do /opt/bk-agent/agent.cfg (AGENT_KEY=…)

$ ./agent.sh --verbose

…

OK: Statistiky úspěšně odeslány.

02

Beautiful Public Status Pages

Give your users confidence. Build and share customizable status pages mapping service metrics on your custom domain.

  • Public by choice: A status page shows only the monitors marked public, without their addresses or internal error texts.
  • Incident History: Record downtime reasons, timeline events, and planned maintenance cycles transparently.
  • Custom Branding: Embed your corporate logo, adjust color styling, and customize navigation bars.

What the public status page carries

  • Current state of the monitors you make public
  • Incidents with their updates
  • Planned maintenance windows
  • E-mail subscribers (double opt-in)
  • An SVG badge and an RSS feed
  • Your logo, colour theme and navigation links
Open the live status page →
03

Instant Notifications

Don't rely on users to tell you when a service goes down. Receive instant alerts on any failure event.

  • Discord & Slack: Each alert names the monitor, its new state, the time and the error the check recorded.
  • Email (SMTP): Secure delivery of outage warnings straight to your inbox.
  • More channels: SMS (Twilio), WhatsApp (CallMeBot), Telegram, Pushover and PagerDuty, plus an escalation webhook for incidents nobody acknowledged.

Alert channels in the code today

  • E-mail (SMTP or PHP mail)
  • SMS through Twilio
  • WhatsApp through CallMeBot
  • Discord, Slack and Telegram
  • Pushover and PagerDuty
  • Escalation webhook for unacknowledged incidents
04

Monitoring That Admits When It Fails

The worst outage is the one your monitoring sleeps through. When the collector dies, a dashboard full of last-known green tells you nothing is wrong - so we made silence impossible.

  • Heartbeat monitors: Backups and cron jobs report in on their own. Nothing to ping, nothing to miss.
  • External watchdog: A Cloudflare Worker checks the collector from outside the server and speaks up when it stops.
  • Never invented: Unmeasured values stay empty. A blank is honest; a fabricated zero is not.

How silence is caught

  • Each heartbeat monitor expects a ping within its interval
  • A Cloudflare Worker checks from outside that the collector still runs
  • The dashboard marks stale data instead of showing it as current
  • A value nobody measured stays empty, never a zero

Ready to take complete control?

Try Blood Kings Monitoring today. Completely free and open-source.