Features
Everything Vigila does
What does Vigila do? It hosts status pages, keeps a timeline of verified facts for each incident, drafts status updates and customer emails from those facts only, and sends them to your page and subscribers once a person approves. Everything below is built and works today.
Status pages
Hosted pages your customers can bookmark.
- Components and groups. Show the parts of your service customers notice, grouped the way they think about them, each with its current status.
- Incident history and scheduled maintenance. Every published incident and maintenance window, with its updates, on the page and in its history.
- Uptime from recorded data only. 90-day bars computed from the statuses your team published, or from HTTP check results where a check watches the component. Days without data show as no data, never 100%.
- Your domain or ours. Serve a page at status.yourcompany.com (Team and Business), or at app.vigila.new-odyssey.com/s/your-page.Early access
- Private internal pages. Open a page with a password, or with a single-use link sent to people at your company's email domain (Business).
Incidents and drafting
Your facts are the only source.
- A timeline of verified facts. What's affected, when it started, what you know, what you're doing, the resolution and a confirmed root cause: each a separate fact with an optional time.
- Drafts from those facts only. An AI draft of the status update and the customer email, or a fact-only template draft when AI isn't switched on. Each draft lists the facts it used.
- A fact check in code. Numbers, times and dates must appear in your facts. Causes, resolutions, uptime, ETAs, scope ("all customers") and reassurances ("no data was lost") are refused unless your facts say so.
- A person approves every update. Nothing is public, and nothing is sent, until someone on your team approves that specific draft.
- Post-incident report drafts. Summary, timeline, what happened, root cause, resolution and follow-ups, from facts and published updates. Gaps stay as "[Team to add]" and block publishing.
Subscribers
Every message is one a person approved.
- Email with double opt-in. People subscribe on your page and confirm by email first. Every update email has a one-click unsubscribe that deletes the address.
- Webhook subscribers. Each published update is POSTed as signed JSON (HMAC-SHA256) to the endpoints you add.
- RSS, Atom and JSON. Feeds of published updates and a status.json for public pages.
- Slack. Post each published update to a channel through an incoming webhook.
Monitoring
Alerts open drafts; people decide what's public.
- HTTP checks. Checks run from Vigila's servers every 1 minute to 1 hour (your plan sets the fastest), with expected status codes, an optional keyword and thresholds. Private and internal addresses are refused, on every redirect.
- Inbound alerts. A secret address per integration, with adapters for generic JSON, Better Stack, UptimeRobot, Grafana and PagerDuty.
- Draft incidents, not public ones. A firing alert or a failing check opens a draft incident with its recorded facts unverified. Someone confirms it before anything can be published; a resolved alert is recorded as a fact, never published.
Questions buyers ask
Can Vigila's AI invent a cause, fix time or uptime figure?
It isn't allowed to, and the code checks every draft. Numbers, times and dates must already appear in your facts; a cause needs a confirmed root-cause fact; a resolution needs a resolved status; uptime, ETAs, scope and reassurances are refused. A draft that fails is replaced by a fact-only template draft, with the reasons shown.