Warden's own console
If this is down, nobody can see what any of the others are doing.
- the site answers200 in 1340ms
- the process is uponline, 11 restarts since deploy
Warden
Your software should not need you awake to keep running.
Warden watches the things you have running, investigates them when they break, fixes what your policy lets it fix, proves the fix by re-running the check that failed — and wakes you only when the answer is genuinely yours to give.
3services watched
255checks run
10incidents
10closed without waking anyone · median 5m down
Nothing of yours yet.
Give Warden a URL and it starts checking. Give it the machine and the process as well and it can read the logs, the process table and the last few commits when that URL stops answering — and, if you let it, put the thing back up and prove it by asking the check again.
No account and no email: a signed cookie makes a service yours. Below is the fleet this Warden actually watches, live — it is not a screenshot, and the incidents in it really happened.
Point it at somethingWatching, right nowanyone can watch these · nobody but their owner can change them
up
Vigil
A public site. If it is down, visitors get nothing.
- the site answers200 in 50ms
- the process is uponline, 11 restarts since deploy
SAGE
Someone else's production, and it is submitted to two competitions. Warden watches it and touches nothing.
- the site answers200 in 197ms
- the process is uponline, 5 restarts since deploy