How the AegiFlow architecture protects your traffic
Understand the request path, the control plane, private origins and why analysis never delays your visitors.
You can explain what touches a visitor request and what runs asynchronously.
The request path stays short
A visitor request crosses exactly three stages: global ingress, the AegiFlow edge, and your origin. The edge applies bounded local policy - strict timeouts, connection limits, a last-known-good configuration - and inspection runs out of process so a slow analyzer can never hold a request hostage.
Everything else is asynchronous
Case correlation, threat feeds, dashboards, reports and notifications run in the control plane, outside the request path. If the control plane degrades, your website keeps serving. Telemetry admission is rate-limited per producer with daily quotas.
Private origins
A protected origin can be completely private: reachable only over mutual TLS from the AegiFlow edge, with no inbound port exposed to the internet. The platform’s own connections are outbound-only tunnels.
Provider neutrality
Global ingress is currently provided through Cloudflare for SaaS, while the AegiFlow edge remains provider-neutral. The design preserves an exit path: your protection logic does not depend on any single vendor.
Verification
- You can name the three hops of the request path
- You know which components may degrade without affecting traffic