Incident communications and status pages
Keep customers informed during incidents without drafting every update.
Enter the verified facts. Vigila drafts the status update and the customer email from those facts only. You approve it, and it's published to your status page and sent to your subscribers.
No account needed for the demo: nothing is published or sent, and it's deleted after 24 hours.
For SaaS teams, agencies running client sites, and internal IT.
Northpeak status
What's affected: Customers can't complete card payments at checkout. Browsing works.
When it started: 14:02 UTC
What we know: Errors began after the 13:58 deploy of the payments service.
What we're doing: Rolling back the 13:58 deploy.
We're investigating a problem affecting Checkout API. Customers can't complete card payments at checkout; browsing works. It started at 14:02 UTC. Errors began after the 13:58 deploy of the payments service, and we're rolling that deploy back. We'll post another update here as we learn more.
Approve and publishSample data
During an incident, writing the update is the job nobody has time for.
The engineers are fixing it. Someone else is asked to tell customers, fast, without overpromising. The update goes out late, or says something nobody confirmed.
Customers then hear guesses about the cause, a fix time that slips, and silence until it's over.
Vigila turns what your team has confirmed into a clear update in seconds, and nothing goes out until a person approves it.
How it works
Facts in, draft out, you publish.
Write what you know
What's affected, when it started, what you know, what you're doing. Short facts, as you'd tell a colleague. Alerts and failing checks can start the list for you, as a draft.
Draft from those facts only
Vigila writes the status update and the customer email. Every draft is checked in code: a cause, fix, time, number or uptime figure that isn't in your facts sets the draft aside.
Approve and publish
Edit if you like, then approve. Your status page updates and confirmed subscribers get the email, plus webhooks, RSS and Slack if you use them.
Close with a report
When it's resolved, Vigila drafts a post-incident report from the facts and the published timeline. Gaps stay marked for your team; it can't be published until they're filled.
Example
The draft says what the facts say. Nothing more.
A draft that said "fixed within the hour" or "no data was lost" would be set aside: neither is in the facts.
The company, incident and times here are made up.
Investigating · 14:09 UTC
We're investigating a problem affecting Checkout API. Customers can't complete card payments at checkout; browsing works. It started at 14:02 UTC. Errors began after the 13:58 deploy of the payments service, and we're rolling that deploy back. We'll post another update here as we learn more.
Sent to confirmed subscribers by email with a one-click unsubscribe, posted to Slack and the page's feeds, after a person approved it.
Who it's for
One habit, three kinds of team
SaaS teams
A public status page with components and uptime from your own records, updates drafted from the incident channel's facts, and subscribers told when you publish.
For SaaS teams →Agencies running client sites
A page per client (Team: 3, Business: 10), each on the client's domain if you like, with HTTP checks that open a draft when a site goes down.
For agencies →Internal IT
A private page staff open with a company email link or a password (Business), and outage emails to the people who subscribe.
For internal IT →Safety boundary
What Vigila's AI may and may not do
This is enforced in the code, not just asked of the model.
- Only your facts.
- Drafts are written from facts your team entered or confirmed, and Vigila's own records (titles, components, recorded times, updates already published). Unconfirmed alert data is left out.
- No invented resolutions.
- A draft can't say it's fixed or restored unless you chose a resolved status or recorded the resolution.
- No invented causes or timelines.
- A cause needs a confirmed root-cause fact. Every number, time and date must already be in your facts.
- No invented uptime.
- Uptime figures come from recorded statuses and check results, computed in code. A draft that mentions uptime or availability is set aside.
- A person publishes.
- Every public update, every email, webhook and Slack post follows one person approving one draft. The database refuses a published update without an approver.
- Your data
- Subscribers' addresses are never sent to the AI provider. Model calls are logged by length and cost, never by text. Export everything (JSON) and your subscribers (spreadsheet), forget one subscriber, or delete the workspace, from Settings. The demo keeps what you paste for 24 hours, then deletes it.
Pricing
Plans from $19 a month, limits shown
Every plan has every feature except custom domains (Team and Business) and private pages (Business). Plans differ by pages, components, subscribers and checks. Every plan starts with a 7-day free trial.
Starter
$19/month
One public status page for a small product.
- 1 status page
- 10 components
- 500 subscribers
- 5 HTTP checks, every 5 min at the fastest
- Vigila address (no custom domain)
- Public pages
Team
$39/month
A few pages on your own domain, for a growing SaaS or an agency.
- 3 status pages
- 50 components
- 5,000 subscribers
- 25 HTTP checks, every 1 min at the fastest
- Custom domain
- Public pages
Business
$79/month
Many pages, private internal pages, and room for a large audience.
- 10 status pages
- Unlimited components
- 25,000 subscribers
- 100 HTTP checks, every 1 min at the fastest
- Custom domain
- Private pages (password or email domain)
Before you choose a plan: 1 status page, 10 components, publishing to your page, email to up to 25 subscribers and 1 HTTP check, free. Your first published update doesn't wait for a card.
Questions
Does Vigila publish updates on its own?
No. Vigila drafts; a person on your team approves each update before it appears on your status page or goes to subscribers by email, webhook or Slack. Alerts and failing checks can open an incident only as a draft, and someone confirms it before anything can be published.
Can the AI make up a cause, a fix time or an uptime number?
It's not allowed to, and the code checks. Every number, time and date in a draft must appear in your facts; causes need a confirmed root-cause fact; resolutions need a resolved status or fact; uptime and ETAs are refused. A draft that fails is set aside and replaced by a fact-only template draft, with the reasons shown.
Where do the uptime figures come from?
Only from what Vigila recorded: the statuses your team published for each component, or HTTP check results where a check watches it. Days with no data show as no data, not 100%. The model never sees or writes uptime figures.
What if AI isn't switched on?
Vigila still drafts, from a fact-only template: a fixed opening for the status you chose, then your facts as written. It's labeled as a template draft.
How do subscribers work?
People subscribe on your page and confirm by email (double opt-in); nothing is sent before they confirm. Every email has a one-click unsubscribe. You can also add signed webhook subscribers, follow RSS or Atom feeds, and post updates to a Slack channel.
Which monitoring tools can open incidents?
Vigila runs HTTP checks itself, and accepts inbound alerts as generic JSON or from Better Stack, UptimeRobot, Grafana and PagerDuty. Each opens a draft incident with the alert's details as unverified facts, for your team to confirm.
Can I use my own domain, or keep a page private?
Custom domains (like status.yourcompany.com) come with the Team and Business plans. Private pages, opened with a password or a single-use link to your company's email domain, come with Business.
What does it cost?
Starter is $19 a month (500 subscribers, 1 page), Team $39 (5,000 subscribers, 3 pages, custom domain), Business $79 (25,000 subscribers, 10 pages, private pages). Every plan starts with a 7-day trial; setting up and publishing your first update is free.
Can I try it before signing up?
Yes. The demo at app.vigila.new-odyssey.com/try drafts a status page and customer updates from a sample incident or a timeline you paste. It's clearly a demonstration: nothing is published or sent, and it's deleted after 24 hours.
Who's behind Vigila?
Vigila is made by New Odyssey. Questions: clio@new-odyssey.com.
See your next incident update drafted from the facts.
Pick a sample incident or paste your own timeline. No account, nothing published, nothing sent.
Ready already? Create an account