Delegated portfolios
Operators see only organizations and services explicitly delegated to them.
Portfolio security operations
One operational workspace for every site your agency protects.
AegiFlow is designed for delegated portfolios, common service templates and evidence-backed reporting without weakening tenant isolation.
What the current evidence supports
Agency workspaces centralize onboarding, operations and reporting across multiple authorized services.
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
Policy templates
Shared intent compiles into per-service controls and safety limits.
Evidence reporting
Availability, incidents, actions and coverage become clear monthly evidence.
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
Import portfolio
Add clients and verify each domain independently.
- 02
Apply templates
Start with blocking turned off and preserve service-specific exceptions.
- 03
Report clearly
Give each customer a concise operational record.
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.
Every client site, one accountable workspace
Agencies operate many organizations from one workspace with real roles — owner, security admin, operator, approver — and per-tenant entitlements. Each client's data stays isolated at the database layer; each action lands in that client's audit trail.
Evidence your clients can actually read
Instead of forwarding raw scanner exports, agencies hand clients a coherent story: what was observed, what was contained, what was recovered and what the receipts say. That is a renewal conversation, not a support ticket.
Start without changing traffic. Activate only measured controls.
Ownership, certificate, origin health and rollback must pass before traffic protection changes.