The engineering workspace for aerospace certification.
Velorum is where certification engineers and design organisations develop functions, FHA, and architecture in one connected environment. Deliverables — FHA reports, traceability tables, assumption registers — are generated from the work, not rebuilt after.
Built for certifying complex systems faster.
VELORUM is the certification-native systems development suite for aerospace and defence teams. It connects requirements, functions, safety, architecture, and deliverables in one platform — cutting the time from concept to certification-ready output.
Certification engineer — independent
You run safety programmes across multiple clients or programmes simultaneously. Your process currently lives in a combination of Word, Excel, and shared drives. Each new project means rebuilding the same FHA template from scratch.
VELORUM gives you a structured, repeatable process across projects — function tree, FHA, and derived requirements in one place, exportable in the format your client expects.
Small DOA — MALE / HALE UAV programme
You are a design organisation with a team of three to ten engineers certifying an unmanned aircraft under EASA regulations. You cannot justify the cost or complexity of enterprise safety tools built for large OEMs.
VELORUM is built for complex systems around ARP4754A and ARP4761 workflows at the scale of a small programme. The process matches what the regulations require — not what a 500-person organisation would build around it.
Systems engineering consultancy
You provide systems and safety engineering services to aerospace clients. You need a tool you can demonstrate to a client, hand off a structured output from, and reference in a compliance argument.
VELORUM produces structured, auditable outputs — Word documents, traceability tables, assumption registers — that map directly to DOA handbook and compliance deliverable requirements.
Three live workbenches. One connected workflow.
Velorum unifies the ARP4754A and ARP4761 workflow in one environment. Functions, failure conditions, and architecture allocations share one model — so the traceability you need on delivery is present from day one, not reconstructed at the end.
Function Tree
Hierarchical decomposition of aircraft and system functions with ARP-style numbering and a Draft → Checked → Approved workflow.
- —Multi-level hierarchy, ARP-native numbering
- —Immutable baselines with audit trail
- —Flat register export (Word + CSV)
FHA Workspace
Aircraft and system functional hazard assessment with full failure condition register, severity classification, and templated deliverable export.
- —Aircraft-level (AFHA) and system-level (SFHA)
- —FC register with auto-assigned IDs, severity, probability
- —Derived assumptions register
- —Templated Word (.docx) + PDF export
Architecture
Dual-layer architecture model — Function → Logical Component → Physical Item — with function allocation matrix and interface definition.
- —Logical and physical architecture layers
- —Function allocation matrix (LC × PI)
- —Interface definition and DAL assignment
- —Redundancy and segregation tracking
Requirements
Bidirectional traceability backbone linking safety objectives to requirements and verification evidence.
- —Requirement capture and derived linkage
- —Traceability to FHA safety objectives
- —Verification evidence register
Safety Assessment
PSSA, FTA, FMEA, SSA, ASA — probability engine and cut set analysis across the architecture.
- —PSSA and ASA workflow
- —FTA with probability engine and cut set analysis
- —FMEA and SSA
Common Cause
Zonal Safety, Particular Risk, and Common Mode Analysis. Independence validation across the architecture.
- —Zonal Safety Analysis (ZSA)
- —Particular Risk Analysis (PRA)
- —Common Mode Analysis (CMA)
One model, three workbenches.
Every failure condition is linked to a function. Every function is allocated to a logical component, and every logical component to a physical item. When you export, the traceability goes with it. Deliverables are generated from the model — not transcribed from it.
Built for regulated aerospace work.
Your engineering IP stays in the EU. Your project content never trains a model. Your deliverables remain yours. The full trust posture — infrastructure, jurisdiction, deployment options, compliance roadmap — is documented on the trust page.
Project data on AWS EU infrastructure via Supabase, with row-level tenant isolation and encryption at rest and in transit.
Your project content is never used to train any model. No third-party AI access to your data.
Netherlands-registered, EU GDPR compliant. Data Processing Agreement available on request.
ISO 27001 certification on the roadmap. SOC 2 follows. Deployment options on Enterprise tier.
Pilot access is open.
The platform is functional and in daily use. We are onboarding a small group of engineers and teams working on ARP4754A and ARP4761 programmes. Pricing is not published — it is agreed during a qualification conversation.
Hierarchical function decomposition with ARP-style numbering, Draft → Checked → Approved workflow, baselines, flat register export.
Aircraft (AFHA) and system (SFHA) functional hazard assessment. FC register, severity, probability, derived assumptions.
Dual-layer model — Function → Logical Component → Physical Item. Allocation matrix, interfaces, DAL assignment.
Immutable snapshots of function trees, FHA tables, and architecture models. Full event log with mandatory comments on transitions.
Templated Word (.docx) and print-to-PDF, configurable per project — company, document number, revision, classification, author.
Bidirectional traceability from safety objectives to requirements and verification evidence.
PSSA, FTA, FMEA, SSA. Probability engine and cut set analysis.
Zonal Safety, Particular Risk, and Common Mode Analysis.
Multi-user workflows with approval gates (Enterprise tier).
Pilot participants' programme needs influence the order of development. Your blockers become ours.
Three live workbenches plus anything shipped during the pilot, for the duration.
We map your programme to the tool together, directly with the engineering team.
Direct line to the engineers building VELORUM throughout the pilot.
Your feedback shapes what we build next and in what order.
Agreed during qualification — not published. No commitment before a fit conversation.
Tell us about your programme.
Send a short description of your programme and team size. We will confirm whether the platform is a fit and agree terms before any commitment.
Common questions.
Can't find what you're looking for? Ask us directly →
Three workbenches are live today. The Function Tree lets you build a structured hierarchy of aircraft and system functions with ARP-style numbering, a Draft → Checked → Approved status workflow, immutable baselines, and full audit trail. The FHA Workspace runs aircraft-level (AFHA) and system-level (SFHA) functional hazard assessment — failure condition register with auto-assigned FC IDs, severity classification, probability objectives, derived assumptions, and templated Word and PDF export. The Architecture Workspace models your system from vehicle to item level using a dual-layer approach (Function → Logical Component → Physical Item), with a function allocation matrix, interface definition, DAL assignment, and safety-relevant fields on each physical item. All three are connected — functions from the tree feed into FHA entries and into architecture allocations, producing a single traceable workflow.
Every failure condition in the FHA is linked to a specific function in the Function Tree. When you create an FHA entry, you select the function it belongs to — the FHA workspace then shows the function number, name, and level alongside the failure condition. The sidebar in the FHA workspace displays all functions with their worst severity and FC count, making it straightforward to navigate from a function to its associated failure conditions and back. This linkage is the foundation for traceability into future workspaces.
Pilot access includes full use of the three live workbenches (Function Tree, FHA, Architecture), an onboarding call to map your programme to the tool, direct access to the engineering team throughout the pilot, and your feedback directly influencing the development roadmap. Pilot terms — including duration and pricing — are agreed individually during a qualification conversation. We do not publish pricing.
VAESIR is built for aerospace safety engineers, certification engineers and small design organisations who run ARP4754A and ARP4761 processes regularly. This includes independent certification consultants managing multiple programmes, small UAV design organisations certifying under EASA regulations, and systems engineering consultancies that need structured, auditable outputs to hand to clients or submit to authorities. VAESIR is not a general requirements or project management tool — it is a focused environment for the specific workflows that precede and inform the safety case.
The Function Tree exports to a flat register (Word and CSV) and can be printed as a structured report. The FHA Workspace exports a templated Word (.docx) document including a cover page, Summary of Results table, Full FHA table, Functions × Severity table, and Derived Assumptions register. The export template is configurable per project — company name, document number, revision, author, and classification. HTML-to-PDF is also available via the browser print function.
Not yet — but it's getting closer. The pilot covers Function Tree, FHA, and Architecture — three connected workbenches that handle the structured early phase of safety engineering and the architectural decomposition that feeds safety assessment. Requirements, Safety Assessment (PSSA, FTA, FMEA, SSA), and Common Cause Analysis workbenches are in active development and form the rest of the roadmap. The intent is to build the full ARP4754A and ARP4761 workflow, but the current pilot is explicitly focused on the three live workbenches as a complete, usable unit of value today.
In development: Requirements Workspace (bidirectional traceability backbone linking FHA safety objectives to requirements and verification evidence), Safety Assessment Workspace (PASA, PSSA, FTA, FMEA, SSA, ASA), Common Cause Analysis (ZSA, PRA, CMA), and team access with role-based approval workflows (Enterprise). Pilot participants receive visibility into the roadmap and influence prioritisation.
Project data is stored using Supabase, hosted on AWS infrastructure in the EU region. Row-level security means only you — and any team members you explicitly grant access to — can view your projects. All data is encrypted at rest and in transit. We do not use your project content for any purpose other than providing the VAESIR service.
Start a conversation.
Tell us about your programme — the airframe you're certifying, the team size, and what you need from a safety engineering platform. We'll confirm whether VELORUM is a fit before discussing terms.