Licensing gets lost in email and attachments.
Regulator requests arrive on scattered channels, responses live in disconnected folders, and no one knows for certain which version of a requirement is current. When the authority asks for the history of a decision, reconstructing it costs weeks.
Requirement map
Every regulatory requirement is an object with status, linked evidence and an owner: you always know what is missing to close the dossier.
Review flow
Authority observations enter as assigned tasks, with deadlines and history: no more spreadsheets to track RAIs.
Full traceability
Every change to a document or response is logged with author, date and rationale, audit-ready with no extra preparation.
Submission packages
Generate the authority submission package directly from live project data, with index and references already consistent.
Import
Load the applicable regulatory framework and break it into traceable requirements.
Assign
Each requirement gets an owner, a deadline and the evidence needed.
Iterate
Authority observations re-enter the flow and update status in real time.
Submit
Produce the consistent submission package and keep the full decision history.
AEGIS models licensing as a graph of requirements, evidence and revisions, with a workflow engine for authority observations and a submission-package generator. Every object carries state, owner and immutable history.
Cloud
Managed instance on sovereign cloud, with per-tenant isolation and data residency in the competent authority's jurisdiction. Suited to operators running multiple dossiers in parallel.
On-premise
Deployment in the operator data center, integrated with the identity provider and internal document systems. The licensing dossier stays entirely under sovereign control.
Air-gapped
Isolated deployment for sensitive programs: submission packages are exported on verified media and no regulatory data traverses external networks.
Evidence traceability
Every requirement is verifiably linked to its evidence and to the revision that produced it, aligned with ISO 27001 records-management principles.
Immutable audit trail
Changes to documents, responses and states are recorded in WORM storage with author, date and rationale: an authority audit needs no extra preparation.
Separation of duties
RBAC enforces distinct roles for drafting, checking and approving submissions, preventing a single actor from closing a requirement without independent control.
Regulatory data sovereignty
Configurable data residency and on-prem/air-gapped modes ensure the dossier stays in the required jurisdiction, with AES-256 encryption at rest.
Does AEGIS support multiple regulatory frameworks at once?
Yes. A dossier can map requirements to 10 CFR, WENRA and SSR-2/1 in parallel, reusing the same evidence where requirements overlap.
How are authority RAIs handled?
Each RAI becomes an assigned task with deadline, owner and history; the linked requirement's status updates automatically when the response is closed.
Is the submission package compatible with regulatory portals?
Yes. AEGIS generates PDF/A and structured XML packages compliant with the submission requirements of NRC, ENSREG and IAEA, with consistent index and cross-references.
Who verifies evidence consistency?
CORTEX automatically checks that linked evidence satisfies the requirement and flags missing references or superseded versions before submission.
The mark encodes the mechanism, not the sector: la cupola di contenimento, il nucleo, le barre di controllo.