Download websites that use Vigil

About Vigil

A status page earns its keep on the worst day of the quarter, which is why the software behind one tends to be chosen for stubbornness rather than for features. Vigil was written for that job. Published under the Mozilla Public License 2.0 in 2018 and implemented in Rust, it runs as a small self-hosted daemon that probes a list of endpoints on a schedule, renders a public health board from the results, and pushes an alert into chat or mail when a probe starts failing.

Choosing to host that board yourself is a decision about trust as much as about cost. A team that puts its uptime reporting on someone else's service is asking that service to stay healthy during its own outage, and plenty of engineers would rather own the risk than explain it. The Rust implementation fits the same instinct, since the process is meant to sit on a spare machine, consume almost nothing and be forgotten until it is needed. Vigil therefore turns up in stacks that were assembled deliberately by people who run their own infrastructure, not in stacks that arrived as a bundle from a hosting provider.

Detection is where a reader should slow down. As of August 2026 the number of sites where we record Vigil is 1. A count of that kind is a floor and not a census, because a status board normally lives on a subdomain of its own, frequently behind an access control layer or on an internal network, and a crawl that walks public apex domains will never reach it. Absence from the data is therefore weak evidence of absence in the wild, and anyone sizing this market from a footprint number alone will size it short.

The commercial reader is usually interested in the population next door rather than in the project itself. Vendors selling hosted status pages and incident tooling spend their outbound effort on teams that have already admitted they need a status page, and a self-managed board is exactly that admission, paired with a willingness to maintain infrastructure instead of buying it. A project shipped under a public licence also has no invoice trail, so a crawl of the web is the closest thing to an adoption figure anyone gets.

A per-domain lookup answers whether one particular site runs Vigil. The downloadable list answers the opposite direction, which is which domains run it at all, what else those domains carry, and how the group changes between refreshes. Working from the export you can pull the hosts, join them against the rest of the stack we record, and find out whether a self-hosted status board keeps company with self-hosted analytics, mail and error tracking, or whether it is one stubborn holdout inside an otherwise rented environment.