Checks that mean something
Not «does the server answer», but «does the homepage load, can someone sign in, does the ordering path work».
Verified recovery
Coming back online is a test, not a hope.
After an incident, the risky moment is the return: everything looks fine, traffic comes back, and the problem returns with it. AegiFlow brings traffic back in small steps and checks that the things that matter actually work at each step.
What the current evidence supports
Recovery is rehearsed on a test address before it is trusted in production, and each rehearsal keeps a pass or fail record.
What you can see and control
Every capability has a narrow responsibility, an operational state and evidence that explains the result.
Available
A little traffic at a time
Traffic returns gradually. If a check fails at any step, the step is undone instead of pushed through.
Proof you can hand over
Each rehearsal and each real recovery leaves a record you can show a client, an auditor or your own board.
02
How you use it in an operating workflow
The visitor path remains short. Configuration, verification and rollback stay visible to the operator at every stage.
Fast request pathParallel analysisEvidence before promotion
- 01
Rehearse on a test address
The whole return is tried out where no real visitor is affected.
- 02
Return in steps
A small slice of traffic first, then more, only while the checks keep passing.
- 03
Record the result
Passed or failed, the outcome is kept with its evidence.
The interface explains what is known, unknown and required
AegiFlow does not turn missing evidence into a reassuring zero. Every state links to its source, freshness and next action.
- State
- Available, observation, configuration required, degraded, unavailable or planned.
- Evidence
- Source, timestamp, scope and last successful verification.
- Action
- The responsible party, exact change and expected impact.
- Way back
- Rollback instructions are defined before an active change.
In depth
How this capability behaves in production — grounded in the platform's documented, current operation.
Drills with receipts, not assumptions
Recovery is exercised on a validation hostname: real requests, real checks, pass or fail — and the receipt is retained. Five drills have passed to date on the first production service; each one is recorded with its evidence.
Traffic returns gradually, gated by business checks
Return to normal is staged — 1%, 5%, 25%, 50%, 100% — and each step must pass business-transaction checks on the routes that matter: homepage, login, API. If a check fails, the step rolls back instead of hoping.
Start in observation. Activate only measured controls.
Ownership, certificate, origin health and rollback must pass before traffic protection changes.