Allowlisted bundle
Only approved public pages and assets enter the continuity package.
Safe service continuity
Keep essential information available while the origin is unsafe.
Static Continuity is a prebuilt, sanitized and signed version of approved pages, stored separately from the customer origin.
What the current evidence supports
Continuity is prepared before an incident. Forms, sessions, checkout and personal data are removed unless a separately reviewed safe workflow exists.
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
Integrity receipt
Hashes, manifest, signature, build time and sanitizer result are recorded.
Independent delivery
The final production gate requires storage and delivery outside the origin failure domain.
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 pathAnálisis en paraleloEvidence before promotion
- 01
Prepare
Capture and sanitize approved public content.
- 02
Verify
Scan, sign and preview the exact bundle.
- 03
Activate
Stop public origin traffic and serve the verified copy.
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.
A signed safe copy, built before you need it
AegiFlow builds, sanitizes and signs static continuity bundles from approved public pages. A bundle is not presented as activatable until independent delivery is exercised while both the origin and control plane are unavailable.
Independent by design
A signed copy is stored on a separate host over a restricted key-locked channel. Independent customer-traffic activation remains a release gate until an outage drill proves the whole path.
Start without changing traffic. Activate only measured controls.
Ownership, certificate, origin health and rollback must pass before traffic protection changes.