Agency workspace
Manage a delegated portfolio with explicit tenant and service boundaries.
Account and service activation
Bring one real service and one measurable risk.
The first cohort is intentionally small: agencies, WordPress and WooCommerce operators, hosting partners and web services without a dedicated security team.
What the current evidence supports
Every service has documented scope, rollback, data handling and explicit exclusions. Traffic is activated only after ownership and technical preflight are complete.
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 · planned
Service activation
Test one exact hostname with blocking turned off before any control.
Threat inventory
Connect signed software inventory and measure actionable relevance.
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 pathAnalyse en parallèleEvidence before promotion
- 01
Qualify
Confirm ownership, service type and risk objective.
- 02
Analyse
Run preflight and measure candidate controls without customer impact.
- 03
Decide
Promote only the controls supported by measured evidence.
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.
Start without changing traffic. Activate only measured controls.
Ownership, certificate, origin health and rollback must pass before traffic protection changes.