Needs configuration
Global ingress
Exact hostnames, managed certificates and global edge protection form the launch route.
Provider-neutral architecture
One control model. Multiple enforcement planes.
The launch path uses Cloudflare for SaaS. Envoy and Coraza preserve first-party policy, telemetry and an incremental path toward Native Edge.
01
What this capability is responsible for
Each function has a narrow operating boundary and a state derived from evidence.
In observation
AegiFlow Edge
Envoy and Coraza provide service-specific inspection and future provider portability.
Available
PostgreSQL control plane
A modular Go application, durable jobs and RLS keep the control plane understandable and testable.
02
How the operating flow works
The visitor path remains short while control, evidence and rollback stay explicit.
- 01
Local decision
The edge enforces the last valid signed policy.
- 02
Durable control
The control plane records cases, workflows and provider reconciliation.
- 03
Independent recovery
Continuity storage must survive both edge and origin failure.
Start with observation. Promote only measured controls.
Every traffic activation requires ownership, certificate, origin and rollback checks.