For teams
Keep your error tracker. Add the operations engineer.
Vigilia turns what breaks in production into incidents anyone on the team can read, hands them to your agents over MCP, and confirms fixes with real traffic. It plugs into what you already run.
Fits your stack
Signed webhooks
HMAC-signed JSON for every alert, with retries — into PagerDuty, Zapier, Make, n8n or your own service.
API and MCP
A REST API with per-token scopes and rate limits, and an MCP server your coding agents can use directly.
Readable by everyone
Plain language by default for product and support; stack, request and breadcrumbs one click away for engineers.
Checks nobody else runs
Secret keys in the shipped bundle, expiring certificates, provider outages and deploy timing — all on the incident.
Where it stands
Vigilia watches browser apps on every plan, and JavaScript backends on paid plans, through @getvigilia/server. The Team plan adds 5 seats with roles (members see and fix; admins also change settings), OpenTelemetry ingest, GitHub, Linear and Jira issues, and a Sentry bridge. If you run Sentry, read Vigilia and Sentry; the short version is: use both.
Try it on one app
Free, and it runs alongside whatever you already use.
Questions
Where is data stored?
In the EU (Belgium). Personal data is scrubbed in the browser before it’s sent and again on the server.
How do we verify webhooks?
Each request carries Vigilia-Signature: a timestamp and an HMAC-SHA256 of the timestamp and raw body with your channel’s secret. The docs have Node and Python snippets.
Will it slow my app down?
No. The script is under 10 KB, loads without blocking the page, and never throws into your app — if anything goes wrong inside it, it gives up quietly.