UNDER CONSTRUCTION

LOADING... AIGENTS COMING UP...

<WATCH_THE_FACTS> // OPEN_SOURCE: AGPL-3.0 + MIT

WTF IS A
WATCHDOG?

IT'S NOT A CHATBOT WAITING FOR YOUR PROMPT. IT WATCHES ONE THING, AND IT WRITES TO YOU WHEN IT CHANGES. SILENCE IS ALSO AN ANSWER.

CHK: 15m

Live log // Latido

> GET tu-sitio.com [200 OK · 412ms]
> DIFF vs SNAPSHOT [0]
> 03:14 [503] DOWN → TELEGRAM

PUT ONE TO WORK
Five watchdogs below

THE CATALOG

LICENSE: MIT // WATCHDOGS: 05

TOTAL SOVEREIGNTY

> SELF-HOST // YOUR PROJECT, YOUR DATA, YOUR BOT

It runs in your own Supabase account, with your own bot. If this project disappeared tomorrow, yours would keep running. That's not a promise — it's the license.

1. ONE JOB ONLY

A watchdog watches one thing. It doesn't do everything badly.

2. SET UP BY TALKING

You tell it what to watch on Telegram. There is no dashboard to fill in.

3. IT WRITES TO YOU

You don't go and check. It shows up when something changed, and only then.

4. OPEN SOURCE

AGPL-3.0 core, MIT catalog. Audit it, host it, change it.

VIGILANCE_LOOP LIVE
> CRON 15m → 1 VIGILANCIA
> OBSERVAR... [200 OK · 412ms]
> SNAPSHOT DIFF... [0 CAMPOS]
> MODEL CALLS: 0
> COSTO: $0.00
> SILENCIO: NADA QUE AVISAR
> NEXT CHECK: 15m
REQUEST ACCESS
LATIDO // WATCHDOG_03 // CADENCE: 15 MIN
02:44 DIFF: 0 FIELDS // SILENCE
02:59 DIFF: 1 FIELD (footer date) // MATTERS: NO // SILENCE
03:14 HTTP 503 // DIFF: 3 FIELDS // MATTERS: YES // ALERT SENT
03:29 DIFF: 0 FIELDS // SILENCE
v0.2
SNAPSHOT_STORED // DIFF: 0 FIELDS
Why_It_Stays_Quiet

ALERTING
TOO MUCH
IS WORSE

It's easy to build one that tells you everything: any change, at any hour. The problem shows up a week later, once you've muted it — because a muted watchdog won't tell you the day something real happens. So this one compares before it speaks, and most of the time it decides to stay quiet.

How it's built // whitepaper
WATCHDOGS: 05MIN CADENCE: 5 minLICENSE: AGPL-3.0 + MITMODEL: ONLY ON CHANGEBETA: CLOSED