GoTe runs its public traffic through AegiFlow — with every claim backed by evidence.
gote.ro is the first production service on the AegiFlow edge. Its traffic is observed in real time, its software inventory is signed, and its recovery path has been exercised — not assumed.
The numbers, from the platform itself
These figures come from AegiFlow operational data, not from marketing estimates.
How the protection was built
Each stage was verified before the next one started. No stage skipped its checks.
- 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 only over mutual TLS. Inspection runs out of the request path; visitors are not delayed.
- 04
Continuity and recovery, proven
Signed continuity bundles are rebuilt on a schedule, and recovery was exercised with drills on a validation hostname — with receipts.
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, reversible controls with a time limit are available; blanket blocking is not enabled.
Threat relevance is claimed only on exact inventory matches, never on guesses.
Every applied control keeps a tested way back.
A state is shown as verified only while its evidence is recent.
Start the same way GoTe did.
Add a domain in observation. Nothing changes for your visitors until every check passes.