Verified onboarding
Domain ownership, certificate readiness, origin health and rollback are mandatory before cutover.
From domain to verified protection
A short visitor path. A complete operational loop.
AegiFlow verifies ownership and origin health before traffic changes. Fast controls stay at the edge, while inventory, threat relevance, cases and evidence are processed in parallel.
What the current evidence supports
A service starts with analysis that does not block visitors and advances to active protection only when certificates, health checks, rollback and service-specific safety limits are verified.
GoTe now
GoTe nowGoTePrivate beta · operator-assisted
- Traffic
- Checking current route
- Protection
- Unknown
- Runtime
- Unknown
- Scope
- Not verifiable
- Traffic proof until
- Not verifiable
Current state is shown only after a fresh, schema-validated snapshot is loaded.
Open status evidencePlatform capabilities
These cards describe product scope. Current delivery stage, runtime health, scope and freshness are reported separately from the validated public snapshot above.
Platform · implemented
Fast request path
Cloudflare, Envoy and Coraza make bounded local decisions without waiting for a database, feed or AI.
Evidence-backed operation
Inventory freshness, applied controls, verification and rollback state remain visible for every service.
02
How you use it in an operating workflow
The visitor path remains short. Configuration, verification and rollback stay visible to the operator at every stage.
Fast request pathParallel analysisEvidence before promotion
- 01
Verify the service
Confirm ownership, origin, certificate and critical business routes.
- 02
Analyse without blocking
Measure traffic and candidate rules without changing visitor access.
- 03
Promote with proof
Use canary, health checks, a time limit and verified rollback before enforcement.
The interface explains what is known, unknown and required
AegiFlow does not turn missing evidence into a reassuring zero. Every state links to its source, freshness and next action.
- Delivery stage
- Planned, implemented, verified, activatable or active.
- Runtime health
- Healthy, degraded, stale, unknown or unavailable — independently of delivery stage.
- Evidence
- Source, timestamp, scope and last successful verification.
- Action
- The responsible party, exact change and expected impact.
- Way back
- Rollback instructions are defined before an active change.
In depth
How this capability behaves in production — grounded in the platform's documented, current operation.
Proof of ownership before a single packet changes course
Onboarding starts with an exact DNS TXT challenge: you prove control of the domain before AegiFlow will even propose a routing change. Then traffic and candidate rules are measured with blocking turned off, so nothing a visitor sees is different.
Activation requires proof, not just a toggle
Traffic protection changes only after explicit safety checks pass: certificate issued, origin healthy over a stability window, health checks green, rollback rehearsed. If a check fails, activation waits — and the interface tells you exactly which check, why, and who can fix it.
Start without changing traffic. Activate only measured controls.
Ownership, certificate, origin health and rollback must pass before traffic protection changes.