Under the hood
For the person carrying the pager
Where you actually work with Virca
The interface
For the engineer who set it up
You don't watch Virca. You talk to it.
There is no console to staff. Tell Virca what you want from the AI tools your team already works in — or from Virca itself, when the incident finds you on your phone at 2:14am. The screen is not a wall of charts. It shows what is installed, what the agent may run, and everything it did, with the supporting data attached to each record. Nobody hunts for a graph to find out what happened.
In the tools you already use
A person used to do this in a GUI. Now your own AI client does it over MCP — looking an ActionBook up, drafting one, adjusting an event rule. The same approved boundary travels with it, and an action graded irreversible is refused outright.
Or wherever the incident finds you
Virca's own conversation surface takes the 2am path. The person who approves does not have to be the person who set it up, and nobody needs a laptop.
You read the record, not a dashboard
Install status, the approved action set, and every execution — filterable, and linkable to a single incident for the retro.
Evidence comes to you
The chart that explains the incident arrives attached to the report and to the log entry, at the moment it matters — not parked on a dashboard until someone looks.