PLATFORM FAQ

Aegis SafeForge is an AI-assisted engineering workflow platform for functional safety, cybersecurity, and regulated risk work. It connects project context, source documents, analysis tables, requirements, reviews, approvals, traceability, and evidence in one governed workspace.

Aegis SafeForge is pilot-ready today around the automotive HARA chain for ISO 26262: Item Definition, HARA, Safety Goals, FSR, TSR, and verification evidence, alongside TARA for ISO/SAE 21434. FMEA, FMEDA, FTA, ETA, lifecycle dashboards, expanded reporting, and other industry-specific artifacts are actively being worked on. Railway, medical-device, and process-safety profiles are expansion tracks through configured pilots and domain-specific workflow setup.

Aegis SafeForge is being built with CRA and AI Act principles in mind: human oversight, transparency, traceability, cybersecurity, logging, source grounding, access control, and governed AI assistance. The compliance dashboard direction starts with CRA, AI Act, ISO 26262, ISO/SAE 21434, and selected industry standards, helping teams identify gaps, rank audit readiness, and maintain documentation as built-in artifacts. Official qualification or conformity-assessment support will be handled as required by customer context and applicable law.

No. AI accelerates drafting, retrieval, and structuring. Qualified people remain responsible for reviewing assumptions, changing generated content, approving engineering decisions, and determining compliance.

Artifacts can be linked across the engineering chain, including item definitions, hazards, threats, goals, requirements, controls, claims, and verification evidence. Aegis SafeForge is designed to build traceability while work happens, so teams do not have to reconstruct spreadsheet relationships right before review.

Spreadsheets are flexible but weak on traceability, ownership, and review governance. Generic ALM tools are powerful, but often require heavy setup and are not safety-workflow-first. Generic AI tools can draft text, but they do not manage review state, approval, deterministic checks, source grounding, or downstream impact. Aegis SafeForge connects workflow structure, AI assistance, human approval, traceability, and evidence in one governed environment.

Generation can use the active system and project context, selected standards, approved upstream artifacts, structured schemas, and documents made available to the relevant organisation, project, or system scope.

The platform is designed to expose field-level reasoning and source references where available. Users can review supported source documents and inspect the project context behind AI-assisted suggestions instead of treating model output as an untraceable answer.

No. AI proposes, the platform governs, and humans decide. Generated records begin in a reviewable state and follow configured review and approval gates. Review state is part of the artifact, deterministic checks handle supported repeatable rules, and engineering judgment remains human-owned.

The platform uses authenticated access, organisation and project boundaries, role-based permissions, and protected service-to-service communication. Deployment-specific controls and customer responsibilities are confirmed during onboarding.

In production, browser traffic is intended to go through the authenticated backend. The retrieval and generation service is treated as an internal service and protected with service credentials.

Aegis SafeForge supports managed SaaS, region-specific SaaS, private cloud or VPC, and self-hosted deployment models. EU companies can request EU servers for SaaS. Regional availability, data-residency scope, and architecture are confirmed during onboarding.

No. Aegis SafeForge supports engineering workflows and audit preparation. It does not certify products, guarantee compliance, or replace independent assessment where one is required.

Contact the Aegis SafeForge team to discuss your standards, workflow, deployment constraints, and pilot scope. Early-access evaluations are planned around a defined use case and review process.

The platform supports document ingestion and structured requirement workflows. Supported formats and migration scope should be confirmed for the specific pilot dataset.