Use cases
Status pages and incident updates for SaaS teams
Vigila gives a SaaS team a public status page with components and recorded uptime, a timeline of verified facts for each incident, and AI drafts of the status update and customer email from those facts only. A person approves each update before it reaches the page and subscribers. Plans start at $19 a month.
What you need during an incident
- Tell customers quickly what's affected, without guessing at causes or fix times.
- Keep the page, the emails and the feeds saying the same thing.
- Show uptime people can trust, from real records.
How Vigila does it
- Engineers add facts as they confirm them; Vigila drafts the update and email from those facts.
- Every number, time, cause and resolution in a draft is checked against the facts in code.
- HTTP checks and alerts from Better Stack, UptimeRobot, Grafana or PagerDuty open a draft incident for someone to confirm.
- Publishing updates the page and notifies confirmed subscribers, webhooks and Slack.
Limits worth knowing
- No SMS notifications.
- Starter has 1 page and 10 components; custom domains start on Team.
What you pay
Starter $19, Team $39, Business $79 a month, with a 7-day trial. Setting up and publishing your first update is free. Unlimited team members on every plan.
Questions
Can our monitoring post to the status page directly?
No, on purpose. An alert opens a draft incident with its details as unverified facts; someone confirms it and approves the first update.
Does Vigila publish anything automatically?
No. Alerts and checks can open a draft incident, and Vigila drafts updates from your facts, but a person approves every update before it reaches the page or any subscriber.