Vigilant
PulseGate's liveness check found it on 4 Oct 2026; it is registered on GitHub and has been in the index since 4 Oct 2026. How this is checked
Vigilant monitors website uptime, user flows, links, Lighthouse performance, DNS, certificates, and CVEs. It sends alerts through channels such as Slack, email, and Discord, and provides branded reports and client-facing monitoring pages for businesses and agencies.
Inferred · not functionally tested
Overview
6 featuresPurpose: Detecting website outages, broken flows, performance issues, and security problems before they affect customers.
Inferred · not functionally tested
Audience: website owners, agencies, and web operations teams
Inferred · not functionally tested
Functions: monitoring, analytics
Inferred · not functionally tested
Interfaces: API: unknown · MCP: unknown · CLI: unknown · Self-hosting: unknown
Recorded constraints: pricing: unknown · license: AGPL-3.0 · platforms: WEB · deployment: browser, cloud_managed
Constraint provenance is unknown; confirm requirements with the publisher.
Record sources: govigilant.io · github.com. These links do not verify the individual claims.
Vigilant sits in PulseGate's Uptime & status pages category. Inferred · not functionally tested: It focuses on detecting website outages, broken flows, performance issues, and security problems before they affect customers. Inferred · not functionally tested: It is built as a B2B product for website owners, agencies, and web operations teams. Basis unknown · not verified: It ships for the web.
Vigilant first shipped in 2024. The project is developed in the open on GitHub with 213 stars. Inferred · not functionally tested: Key capabilities include Uptime Monitoring, Flow Monitoring, and Broken Link Detection.
Summary written by a language model from the project’s public pages.
Tasks: Inferred · not functionally tested
- Uptime Monitoring
- Flow Monitoring
- Broken Link Detection
- Lighthouse Monitoring
- DNS Monitoring
- CVE Monitoring
Topics: Inferred · not functionally tested
Built with & integrations
- GitHub Copilot
- commit c9eb72544323 · since Feb 2026
- Cloudflare
- cf-ray header · cf-cache-status header
Trust & compliance
Indexing history
1What PulseGate has recorded for this listing
- Indexed7 Sep · 02:33 UTCgovigilant/vigilant seen via GitHub Search (Smart)Source: GitHub Search (Smart) · Open
Frequently asked questions about Vigilant
- What does Vigilant do?
- Inferred · not functionally tested: Vigilant focuses on detecting website outages, broken flows, performance issues, and security problems before they affect customers. It is catalogued under Uptime & status pages on PulseGate.
- Who should use Vigilant?
- Inferred · not functionally tested: Vigilant is a B2B product built for website owners, agencies, and web operations teams.
- What platforms does Vigilant run on?
- Basis unknown · not verified: Vigilant runs on the web.
- Is Vigilant still active?
- PulseGate's liveness check found it on 4 Oct 2026.
- What are alternatives to Vigilant?
- Similar projects tracked by PulseGate include Vigilant, Vigil, and Vigilmon.VigilantVigilVigilmon
- When did Vigilant launch?
- Vigilant first shipped in 2024.
- Is Vigilant open source?
- Basis unknown · not verified: Vigilant has a public GitHub repository.
Similar projects
Closest matches by what these projects do