vigil
Vigil is an open-source status page and monitoring platform written in Rust that tracks the health of distributed infrastructure services. It automatically sends alerts via Slack, email, SMS, and other channels when services go down, and displays public status to end users.
Key facts
Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.
| Field | Value |
|---|---|
| Repository | valeriansaliou/vigil |
| Owner | valeriansaliou |
| Primary language | Rust |
| License | MPL-2.0 — OSI-approved |
| Stars | 1.9k |
| Forks | 143 |
| Open issues | 43 |
| Latest release | v1.29.0 (2026-03-26) |
| Last updated | 2026-05-03 |
| Source | https://github.com/valeriansaliou/vigil |
What vigil is
Built in Rust, Vigil monitors HTTP/TCP/SSH/ICMP endpoints, integrates with application reporters, and supports local monitoring daemons. It provides a web-based status dashboard, webhook notifications, and configuration via text files with environment variable interpolation.
Get the vigil source
Clone the repository and explore it locally.
git clone https://github.com/valeriansaliou/vigil.gitcd vigil# follow the project's README for install & configurationNeed it deployed, integrated, or customized instead? DEV.co ships production installs.
Best use cases
Implementation considerations
- Requires Rust build environment or pre-built binary; Docker images available but may lag behind latest release.
- Dependencies include OpenSSL headers (libssl-dev) and optionally XMPP library headers (libstrophe-dev); pin your build toolchain to avoid version mismatches.
- Configuration is file-based (vigil.cfg) with environment variable interpolation; no dynamic UI-based config management is evident.
- Monitoring is active/pull-based (probes) for HTTP/TCP/SSH/ICMP, but requires agent installation (Vigil Reporter) for application-level health reporting.
- State and alert history are stored in the running process; no explicit data persistence layer described—understand retention and backup implications.
When to avoid it — and what to weigh
- Minimal operational overhead required — Vigil requires self-hosting, maintenance, and infrastructure management. If you want a fully managed solution, consider hosted alternatives like Crisp Status.
- Require advanced observability features — Vigil focuses on availability monitoring and alerting. It does not provide metrics, logs, traces, or performance profiling—use dedicated APM tools for those needs.
- Need commercial support guarantees — This is a community-maintained open-source project. There is no documented SLA or paid support offering, only community engagement.
- Cannot host on your own infrastructure — Vigil must be self-hosted. It cannot be deployed to managed platforms without substantial custom work, and there is no official SaaS offering.
License & commercial use
Licensed under MPL-2.0 (Mozilla Public License 2.0), a weak copyleft license. Source code modifications must be disclosed, but proprietary applications can link and distribute as long as the license terms are preserved. Commercial use is permitted under MPL-2.0 terms.
MPL-2.0 permits commercial use, but imposes copyleft obligations: any modifications to Vigil source code must be shared. Packaging Vigil in a commercial product requires careful review of file-level modifications. No trademark grants, liability limitations, or warranty disclaimers are stated in the license text alone—review the full LICENSE file in the repository for complete terms.
DEV.co evaluation signals
Editorial assessment — not user reviews. Directional, with an explicit confidence level.
| Signal | Assessment |
|---|---|
| Maintenance | Active |
| Documentation | Adequate |
| License clarity | Clear |
| Deployment complexity | Moderate |
| DEV.co fit | Good |
| Assessment confidence | High |
Self-hosting eliminates third-party data exposure, but introduces responsibility for API credentials (Slack, email, SMS). MPL-2.0 source code visibility allows community audit but does not guarantee secure development practices. No explicit statement of security testing, vulnerability disclosure policy, or incident response process. Probe functionality (HTTP/TCP/SSH) requires careful firewall and access control configuration. Vigil Reporter integration requires secure token management.
Alternatives to consider
Crisp Status (SaaS)
Hosted alternative explicitly mentioned in the README. Eliminates self-hosting overhead and integrates with Crisp platform (chatbox, helpdesk) for richer user notifications.
Uptime Kuma (open-source)
Another OSS status page and monitoring tool; may offer simpler deployment or different notification feature set—requires separate evaluation.
Datadog / New Relic (SaaS)
Commercial full-stack observability platforms with status pages, alerting, and support; trade self-hosting for breadth of APM, metrics, and logs.
Build on vigil with DEV.co software developers
Vigil gives you self-hosted status monitoring with multi-channel alerting. Evaluate the documentation, test with your microservices, and deploy via Docker or pre-built packages.
Talk to DEV.coRelated open-source tools
Surfaced by semantic similarity across the DEV.co open-source index.
Related on DEV.co
Explore the category and the services that help you build with it.
vigil FAQ
Can I use Vigil for commercial SaaS products?
Does Vigil support authentication and access control?
Is there a hosted version of Vigil I can use?
What is the performance impact of Vigil on my infrastructure?
Custom software development services
From first prototype to production, DEV.co delivers software development services around tools like vigil. Our software development agency staffs experienced software developers and web developers for custom software development, web development, integrations, and ongoing support across open-source observability and beyond.
Ready to Monitor Your Infrastructure?
Vigil gives you self-hosted status monitoring with multi-channel alerting. Evaluate the documentation, test with your microservices, and deploy via Docker or pre-built packages.