GoTe runs its public traffic through AegiFlow — with every claim backed by evidence.
gote.ro is the first operator-assisted reference service on the AegiFlow edge. The validated public snapshot below is the current source of truth; the dated figures in this study are historical evidence.
A Web Resilience Control Plane for critical services.
AegiFlow keeps critical web services available during attacks or incidents and demonstrates that they returned safely. Cloudflare supplies global ingress; AegiFlow owns service context, bounded response, continuity, recovery and evidence.
- 01Monitor
- 02Protect
- 03Continue
- 04Recover
- 05Prove
Assisted analysis is planned. No language model can directly change Cloudflare, DNS, data, secrets or rollback state.
Historical validation snapshot
Recorded on 30 July 2026 for gote.ro and its validation hostname. They are not presented as current counters; current health and freshness are shown above.
How the protection was built
GoTe was returned to shadow after the audit found that earlier enforcement did not use one unified Safety Contract. The sequence below separates demonstrated evidence from gates that remain open.
- 01
Verified onboarding
Domain ownership was proven with an exact DNS challenge before any traffic decision.
- 02
Signed inventory
A read-only, outbound-only connector collected 283 software components. Threat advisories are matched against exact package versions; unknown stays unknown.
- 03
Observation at the edge
Traffic flows through the AegiFlow edge to a private origin reachable over mutual TLS. Coraza inspection runs out of process on the request path in shadow mode, with bounded timeouts and no blocking.
- 04
Signed continuity and limited recovery drills
Signed continuity bundles are rebuilt on a schedule and recovery was exercised on a validation hostname. Independent activation, login, checkout and production-apex recovery are not yet demonstrated.
What we deliberately do not claim
Honest state is the product. Active autonomous enforcement stays disabled until every stability, shadow and rollback gate passes.
Bounded control proposals and operator rollback procedures exist; customer-traffic execution remains disabled until the broker and every gate are verified.
Threat relevance is claimed only on exact inventory matches, never on guesses.
No control may be promoted until its rollback path is linked to the activation receipt and demonstrated.
A state is shown as verified only while its evidence is recent.
Start without changing traffic.
Add a domain for analysis. Nothing changes for your visitors until every check passes.