November 2026
What the IT incident demo does, and what is simulated
The sequence and the approval are real mechanics. The outage is not.
Why it is synthetic
AegisOps does not yet have a client incident it is allowed to show. Inventing one would be a case study we have not earned. The demo uses a made-up payments service so the pattern can be inspected without borrowing someone else’s outage.
What is simulated
The monitor, the logs, the deploy, the ticket, and the recovery figures are synthetic. Nothing is connected to a client network. The numbers are there to make the sequence readable, not to claim an improvement.
What is real
The order of work is the one we implement: trigger, gather, recommend, wait, then act and record. The agent cannot take the runbook step. A person has to approve or refuse. The refusal path logs that nothing changed.
What it does not do
It does not page an on-call, change infrastructure, or learn from your data. A pilot on one of your services is a separate engagement, read-only first.