Get started
03:12:41webhook-relay · check timed out · down03:12:44incident opened · VIGIL runs DNS, TCP, HTTP and TLS checks03:13:02verdict ready. you already know what broke

Uptime Kuma plugin · monitoring

Your Uptime Kuma, owned by VIGIL.

Ask in chat which monitors you have and whether anything is down. VIGIL answers from your live Uptime Kuma, manages monitors with approval, opens incidents from alerts and diagnoses every outage.

In plain words

What it is, where it lives, when to reach for it

What is it
Connects your Uptime Kuma to VIGIL, the alerts agent: ask about monitors, manage them with approval, get diagnosed incidents.
Where do I use it
In chat and the quox kuma CLI, reading your own Uptime Kuma server.
When would I use it
When something looks down and you want your uptime checks beside the rest of your fleet view.
How do I use it
Buy it once in the store for $9, then an org admin installs it from the dashboard's Plugins page.

See it work

The board, mid-incident.

The pulse behind this page is the heartbeat stream: every strand a monitor, every beat a check coming back. Pay once in the store and paste your licence key in Settings. No subscription, ever.

This is the kind of board your Uptime Kuma feeds. Watch one service break, then watch VIGIL open the incident and diagnose it.

Example board · illustrative example data
collector-apihttps · group: core
up12 ms24 h 99.99%
dashboardhttps · group: core
up21 ms24 h 100%
postgrestcp · group: data
up3 ms24 h 99.98%
webhook-relayhttps · group: edge
up48 ms24 h 99.94%
qdranttcp · group: data
up5 ms24 h 99.97%
Illustrative data. On your install the board is fed by your own Uptime Kuma instance, and the example hosts here are made up.

What it does

Green until it is not.

VIGIL is the alerts agent. Ask it “which monitors do we have, is anything down?” and it answers from your live Uptime Kuma. When its data is stale, it says so.

Changes go through people. VIGIL proposes a monitor add, edit, pause, resume or removal, a person approves it in the inbox, and only then does it run. Each change is recorded as a signed evidence envelope. An agent writing to your monitors directly is refused.

When Kuma raises an alert, Quox opens an incident, closes it on recovery with the duration, groups flapping, and has VIGIL diagnose the outage with a plain verdict.

In testing

Now in testing, next on the list.

These are built and being exercised. We list them here so you know what is coming, and we do not count them as proven yet.

Coverage auditquox kuma coverage compares fleet hosts and verified domains against your monitors and proposes the gaps, each one gated by approval.
Uptime reportsquox kuma sla produces signed uptime reports you can verify offline.
MaintenanceMaintenance windows, customer-safe status-page notices, and read-only checks inside managed hosts through the governed exec path.

What VIGIL does, proven

AskAsk VIGIL, the alerts agent, which monitors you have and whether anything is down. It answers from your live Uptime Kuma and calls stale data stale.
Managequox kuma monitors list|add|edit|pause|resume|remove, from chat or the CLI. Every change is proposed, waits for a human approval in the inbox, and runs only after approval.
EvidenceEach approved change is recorded as a signed evidence envelope (quox.kuma.monitor.add and its siblings). Proven end to end: an add proposed in chat, approved by a person, executed, recorded.
SafetyAgents can never change monitors directly. A direct write by an agent is refused.
IncidentsKuma alerts arrive on a per-organisation webhook. The secret is stored only as a hash. Outages open incidents, recoveries close them with their duration, flapping is grouped, and every transition is recorded as evidence.
DiagnosisEvery outage is diagnosed automatically by VIGIL: DNS, TCP, HTTP status, TLS expiry and keyword checks from outside, with a plain verdict. Switch it off per organisation if you prefer.
CLIRead-only: quox kuma status|down|uptime|incidents|diagnose. down exits 3 when anything is down, so scripts can act on it.

Pricing

One more row on the board.

Plugins are one-off purchases, not subscriptions. This one reads like the services it watches.

uptime-kuma · plugin licenceone payment · group: yours
$9one-off · no renewal
Add to cartView in the store

requires QuoxCORE 1.0+ · requires an Uptime Kuma instance · licence: commercial · version 1.0.0 · unlock: licence key in Settings