Global Edge
Cloudflare for SaaS provides global ingress; AegiFlow adds service context.
Web protection and service resilience
AegiFlow
AegiFlow identifies the threats affecting your web services, contains attacks through reversible measures, and keeps essential functions available.
The visitor stays on a fast local path. Inventory, threat relevance, cases and evidence are processed in parallel.
- Local edge decisions
- Parallel analysis
- Verified rollback
OPERATIONAL NETWORKIllustrative flow, no customer data
NORMAL TRAFFICRequests are inspected locally and delivered without waiting for deep analysis.Fast path: Cloudflare -> Envoy -> Coraza -> origin
- Visitor traffic enters through Cloudflare.
- Envoy and Coraza make local request decisions.
- Telemetry is analyzed asynchronously by Threat Radar and Live Cases.
- Static Continuity can replace an isolated origin.
- Recovery returns traffic gradually after business checks pass.
From domain to measured protection.
Every stage explains who acts, what changes, how AegiFlow verifies the result and how to return safely.
- 01
Create account
Organization and roles are kept separate from protected traffic.
- 02
Verify domain
A DNS proof confirms that the service is authorized.
- 03
Observe
AegiFlow measures compatibility without blocking visitors.
- 04
Activate safely
Certificate, origin, health checks and rollback must all pass.
02
A new vulnerability becomes a clear answer.
AegiFlow connects advisories to the exact software inventory of each service. Unknown evidence stays unknown; it is never presented as safe.
Explore Threat RadarProtection statusIn observation
CRITICAL
Relevant WordPress vulnerabilityExact package and version match
97%shop.exampleAffectedUpdate required
portal.exampleControl installedLast verified 8 min ago
api.exampleUnknownInventory is stale
Example data. A protected state requires current inventory and verification evidence.
Fast traffic. Deep analysis in parallel.
Databases, threat feeds, AI and the dashboard are never dependencies of the visitor request.
SYNCHRONOUS REQUEST PATH
CloudflareEnvoyCorazaOrigin
Bounded local controls onlyASYNCHRONOUS OPERATIONS
TelemetryCasesThreat matchEvidence
Sampling is reduced before traffic is affectedCASE-0041Action required
Credential stuffing contained on /login
- Scope
- 1 route · 7 fingerprints
- TTL
- 15 min
- Health checks
- Passing
- Rollback
- Ready
04
Automation has a scope, a clock and a way back.
Candidate controls run without blocking first. Canary checks, a short lease and explicit rollback precede active enforcement.
Review reversible responseKeep the service useful, then recover deliberately.
Approved public content remains available while the origin is isolated. Business checks control the gradual return of traffic.
Signed continuityApproved pages only
Business checksHomepage, login, API
Gradual recovery1% → 5% → 25% → 50% → 100%
One control plane. Four integration modes.
Choose the operating boundary that fits the service.
Needs configuration
Native Edge
Envoy and Coraza apply provider-neutral controls close to the origin.
Hybrid Resilience
Global and native paths share the same safety contract and evidence.
Observe Only
Inventory, availability and threat relevance without traffic enforcement.
07
A state is credible only when the evidence is recent.
Capability state, inventory freshness, applied controls and recovery results remain explicit. A missing check becomes Unknown, never a green status.
Open the Trust CenterCapability stateAvailable, observing, degraded or unavailable
Protection PassportInventory, control and verification freshness
Evidence receiptsHash, release, decision and result
Explain this stateOwner, next action, verification and rollback
START WITH OBSERVATION
Add one domain. Change no traffic until the checks pass.
AegiFlow guides ownership, origin, certificate and rollback before activation.