AEGIFLOW HELP CENTER

Move from question to verified result.

Every guide explains prerequisites, impact, exact steps, verification and rollback.

Operational viewIllustrative. No customer data.

Getting started

Configure your first protected serviceCreate an organization, add a domain and reach observation mode without changing production traffic.Protection states, from observation to enforcementWhat Observe, Shadow and Enforcing mean, which gates sit between them and how you move safely in both directions.

Accounts and organizations

Accounts, organizations and rolesUnderstand the boundary between your identity, an organization and the services that organization owns.Billing, plans and what free really includesHow observation stays free, what paid plans add, and why billing in AegiFlow fails closed.

Adding a domain

Add a domain without moving trafficRegister a website in AegiFlow, verify authorization and preserve the current production route.

DNS and certificates

Complete DNS ownership and certificate validationPublish the exact DNS records requested for ownership and certificate issuance, then verify both states.

Edge and origin

How the AegiFlow architecture protects your trafficUnderstand the request path, the control plane, private origins and why analysis never delays your visitors.Validate the edge and origin before activationConfirm certificate, origin health, Host and SNI behavior, private access and rollback before routing users.

Inventory and Threat Radar

The inventory Connector, explainedHow the signed, outbound-only Connector collects your software inventory without opening any door into your site.Using the public Advisory DatabaseWhat the public database at /threat-radar/database/ contains, where its data comes from and how it relates to your protected services.Understand inventory and protection statusRead software inventory freshness, advisory matches and the evidence behind affected, protected or unknown states.

Cases and response

An incident response playbook with AegiFlowA practical sequence for the first thirty minutes of a web incident: read the case, decide on containment, keep the service useful, recover with proof.Review and control a reversible responseInspect evidence, scope, health checks, time limits and rollback before keeping or reversing an action.

Continuity

Prepare a safe continuity bundleBuild an allowlisted, sanitized and signed copy of approved public content before an incident.

Recovery

Run a verified recoveryValidate integrity and business transactions before returning traffic gradually to a clean origin.

Teams and agencies

Delegate access across a portfolioAssign organization-scoped roles and keep agency access separate between customer tenants.

API and integrations

Use the API and signed integrationsIntegrate inventory, edge events and operational workflows with scoped credentials and idempotent requests.Connect security tools without fragmenting operationsUnderstand how AegiFlow receives portable detections, scanner results, threat intelligence and SOC evidence while keeping one customer workflow.

Security and data

Mapping AegiFlow evidence to NIS2 measuresWhich Article 21 risk-management measures AegiFlow produces operational evidence for, and where each proof lives.Understand data collection and retentionSee which metadata AegiFlow collects, what is excluded by default and how tenant access is constrained.

Troubleshooting

Troubleshooting and frequent questionsQuick answers for the situations owners hit most often: stuck states, missing data and what Unknown really means.Resolve a certificate that remains pendingIdentify the current validation records, remove ambiguity and verify Cloudflare hostname readiness.