Product
A platform that knows what aDAL means.
AeroCert is built around the standards, not adapted to them. The data model maps to objectives, design assurance levels, and certification artifacts directly — so the work you do day to day is the work the auditor sees.
The workflow
From program kickoff to cert package.
- Step 01
Plan
Stand up a new program in hours, not weeks. Pick your standards, your DALs, your authority structure. AeroCert generates the objective set you owe and the artifact templates you’ll author against. - Step 02
Develop
Connect your requirements tool. Author or import system, software, and hardware requirements. Allocate down. AeroCert maintains the trace as you go — not as a one-time matrix dump at the end. - Step 03
Verify
Connect your CI and test infrastructure. Test results land linked to the requirements they verify. Coverage gaps surface in real time. Independent verification is enforceable by role. - Step 04
Review
DER and AR Stage Of Involvement reviews are first-class workflows. Findings, dispositions, and signoffs are tracked end-to-end with full audit history. Read-only auditor access is built in. - Step 05
Submit
Generate the cert package on demand: PSAC, SAS, traceability matrices, configuration index, problem reports, all of it. Versioned, signed, and reproducible.
The data model
Every entity exists for a reason.
We didn’t pick a generic GRC schema and rename the columns. Programs, objectives, artifacts, evidence, findings — these are the nouns of certification, modeled the way DERs, ARs, and program managers actually use them.
- Programs
- A program is the certifying unit — an aircraft, a launch vehicle, a payload, a software item. Programs carry their applicable standards, DALs, and authority relationships.
- Requirements
- System, software, hardware, and derived requirements with parent/child relationships, allocation, and rationale. Imported from DOORS Next, Jama, Polarion, or authored in-platform.
- Objectives
- DO-178C objectives by software level (Tables A-1 through A-10), DO-254 design assurance objectives, ARP4754A development assurance — modeled directly, not as tags.
- Artifacts
- PSAC, SDP, SVP, SCMP, SQAP, SAS, HDP, HVP, FHA, PSSA, SSA — and the rest. Each artifact knows which objectives it satisfies.
- Evidence
- Test results, analyses, reviews, and tool outputs — linked to the requirement they verify and the objective they close.
- Findings
- DER and AR findings, internal review actions, audit observations — tracked from open through closure with full disposition history.
Traceability
The matrix nobody wants to maintain.
AeroCert maintains traceability as a live graph, not a quarterly spreadsheet export. Walk from a Level A software requirement up to its parent system requirement, sideways to the hardware allocation, down to the test that verifies it — in one click.
Gaps don’t hide. Orphan requirements, untested verifications, unsatisfied objectives — surfaced continuously, not at Stage 4.
// Trace from objective to evidence
DO-178C A-7.1
↳ Test procedures developed
SwReq-AOC-1147
"The autopilot shall disengage on dual AHRS failure"
↳ SysReq-FCS-208 (parent)
↳ HwReq-AHRS-44 (allocated)
↳ Test-AOC-RBT-339 (verifies)
⚠ No structural coverage evidence
Integrations
Meet your team where they work.
Nobody wants another silo. AeroCert connects to your existing requirements tools, PLM, source control, CI, and analysis tools — and pulls evidence into the cert process automatically.
Need an integration that isn’t listed?Tell us about your stack.
Submission
The cert package, on demand.
Generate a complete, audit-ready package whenever you need one — for an internal review, a Stage 4 submission, or the night before a TIA. PSAC, SAS, SDP, SVP, SCMP, traceability matrices, problem reports, configuration index. All of it.
Versioned. Signed. Reproducible from the underlying data at any point in history.
- ·PSAC — Plan for Software Aspects of Certification
- ·SDP — Software Development Plan
- ·SVP — Software Verification Plan
- ·SCMP — Software Configuration Management Plan
- ·SQAP — Software Quality Assurance Plan
- ·SAS — Software Accomplishment Summary
- ·HDP — Hardware Design Plan
- ·HVP — Hardware Verification Plan
- ·Traceability matrix (req → test → result)
- ·Problem reports & open finding log
- ·Configuration index
- ·Tool qualification data (DO-330)
Roles
Modeled on the people doing the work.
Program manager
Full program visibility, plan authoring, status reporting, and cert package generation.
Certification engineer / lead
Owns objectives, artifact authoring, and the trace. Day-to-day driver.
DER / AR
Stage Of Involvement reviews, findings, dispositions, signoff. Independent of the development team by default.
Software / hardware lead
Authoring scoped to allocated requirements and artifacts. Cannot self-verify.
Auditor (read-only)
FAA, EASA, NASA technical authority, or customer audit access. Time-bound, scope-limited, fully logged.
Get involved
Get early access.
AeroCert is in active development with design-partner customers. If your team is preparing for a cert effort in the next 12 months, we want to talk.
We respond to every request personally. No drip campaign.