Setup you can verify
Domain ownership, the certificate, the health of your origin (your own server) and a tested way back must all be in place before traffic is touched.
So funktioniert es
Nothing changes for your visitors until you say so.
You add a domain, prove it is yours, and AegiFlow starts watching. Protection is switched on later, in steps, and only after a list of checks passes. If a check fails, nothing is switched on.
What the current evidence supports
Watching costs you nothing and risks nothing. Every step that could affect a real visitor is gated behind a check you can see.
What you can see and control
Every capability has a narrow responsibility, an operational state and evidence that explains the result.
Available
Fast decisions, close to the visitor
Checks that run on each request happen locally and finish in milliseconds. They never wait for a database, a threat feed or an AI service — those run separately.
You can always see why
For each service you see how fresh the information is, what was applied, what was verified and how to undo it. A missing check is shown as Unknown, never as a green tick.
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 pathParallele AnalyseEvidence before promotion
- 01
Prove the domain is yours
You add a short text record in your DNS. Until it matches exactly, AegiFlow will not propose any change.
- 02
Watch without blocking
Traffic is measured and candidate rules run in the background. You see what they would have caught; visitors see nothing different.
- 03
Turn protection on, in steps
Only after the checks pass, and always with a time limit and a rehearsed way back.
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.
Proof of ownership before a single packet changes course
Onboarding starts with an exact DNS TXT challenge: you prove control of the domain before AegiFlow will even propose a routing change. Then the service runs in observation — traffic is measured, candidate rules run in shadow, and nothing a visitor sees is different.
Activation is a gate, not a toggle
Traffic protection changes only when a series of explicit gates pass: certificate issued, origin healthy over a stability window, health checks green, rollback rehearsed. If any gate is open, activation waits — and the interface tells you exactly which gate, why, and who can close it.
Start in observation. Activate only measured controls.
Ownership, certificate, origin health and rollback must pass before traffic protection changes.