Airborne software, with every controlled item approved by name.

For software and airborne electronic hardware teams under DO-178C and DO-254. Your qualified tools and plans stay as they are.

Standards: DO-178C · DO-254 · DO-330
Firmware tools: Arm GCC, Arm Compiler 6, IAR, J-Link, ST-LINK
FPGA tools: Verilator, GHDL, Yosys; Vivado, Quartus, Libero, Radiant
Agent policy: Avionics sector template
Deployment: Self-hosted, your cloud or air-gapped

What your team gets

Built around your plans, not around the AI.

Govern features are in use today. Domain modules are pre-release; their state is listed under Tools and formats.

Controlled items stay controlledThe avionics template makes agent changes to requirements and trace data wait for a named approver, and denies agent changes to qualified-tool configuration and released baselines.

Firmware in the EditorBuild, unit-test, flash and debug microcontroller firmware with your compilers and probes, with registers from the SVD and RTOS awareness.

FPGA designs for DO-254Lint, simulation, formal verification and timing reports beside the RTL, on the open tools or your vendor tools.

Evidence of AI useSigned evidence packs say which lines AI touched, which model and context were used and who approved. Anyone can verify one offline.

Closed networksGovern runs air-gapped, with models served inside your network.

Who uses it

For every role from the requirement to the certification liaison.

Software engineersBuild, test and debug flight software, with agents working under the avionics template.

Airborne electronic hardware engineersLint, simulate, synthesise and read timing for FPGA designs.

Verification engineersRun host unit tests, testbenches and formal properties, with pass or fail per test.

Configuration managersApprove changes to requirements, trace data and release branches as named approvers.

Certification liaisonExport the audit record and evidence packs for your assessor.

Tools and formats

What the modules handle, and how far each is verified.

The Embedded and HDL modules drive the tools you already qualified. They do not replace them.

Firmware projectsKeil, IAR and STM32CubeIDE projects imported into CMake; builds of a CMake preset with a Flash and RAM report; host unit tests. Built and tested on recorded tool output; not yet run against IAR or Keil.Arm GCC · Arm Compiler 6 · IAR · CMake · Ninja · CTest · Unity · .uvprojx · .ewp · .cproject

Flash and debugFlashing after a confirmation; debugging with peripheral registers from the SVD, RTOS awareness, fault decoding and a serial monitor. Running an image in QEMU is verified against QEMU 9.1.1; nothing has been run on a board.OpenOCD · SEGGER J-Link · ST-LINK (STM32CubeProgrammer) · GDB · QEMU · SVD · FreeRTOS · Zephyr · ThreadX

Static analysisCppcheck findings, including MISRA C:2012, in the Problems view. Built and tested on recorded tool output.Cppcheck · MISRA C:2012

FPGA, open flowLint, simulation, cocotb testbenches, formal verification, waveforms, synthesis and place and route. Verified on Linux. Programming a board is not yet run.Verilator · Icarus Verilog · GHDL · cocotb · SymbiYosys · Yosys · nextpnr · openFPGALoader · VCD · FST

FPGA, vendor flowsThe vendor tools driven in batch mode, with their messages and timing and utilisation reports in the same views. Kit shipped or modelled: not yet run against the vendor tools.AMD Vivado · Intel Quartus · Microchip Libero SoC · Lattice Radiant

Embedded LinuxIn early development behind a setting, not ready for use: Yocto Project and Wind River Linux builds on your Linux build server over SSH. Modelled on Linux only; not yet run on Windows, a real build server, Wind River Linux or a board.Yocto Project · Wind River Linux · BitBake · kas

Domain modules are pre-release. Nothing is verified by a customer yet, and nothing is verified on Windows. Do not rely on a capability for production work until it is verified for your tools, versions and operating system. Product names belong to their owners.

How a change moves

A person decides before anything leaves the desk.

Propose
An engineer or agent drafts a change to flight software or its trace data.
Verify
Your qualified tools build, check and test it.
Approve
A push to a release branch waits for a named approver.
Record
Change, results and approval kept together in the audit record.

Standards

Evidence for your plans. The certification is yours.

DO-178CEvidence toward DO-178C: changes to requirements, trace data and release branches with their approver and reason, in a tamper-evident record.

DO-330Evidence toward DO-330: agents are denied changes to qualified-tool configuration, and every decision is logged.

DO-254Evidence toward DO-254: each implementation run kept with the commit it came from, and each RTL change with its review and approval.

Neural Inverse provides evidence toward these standards. Certification stays with your organisation and assessor.

Rules you work under

What they ask, and what Neural Inverse gives you toward them.

We produce records your assessors and regulators can use. We never say a product makes you compliant; that stays with your organisation.

Standards

[Draft: to be approved by legal counsel before publication]

EASA Part-ISWhat it asksApproved organisations in civil aviation run an information security management system, manage information security risk and report information security incidents. It has applied to design and production organisations since 16 October 2025 (Regulation (EU) 2022/1645), and to operators, maintenance and training organisations since 22 February 2026 (Regulation (EU) 2023/203).What Neural Inverse gives youSingle sign-on and access control, approvals by named people and a tamper-evident audit log you can export when you report. Govern runs self-hosted or air-gapped, inside your boundary.

Software approval: FAA AC 20-115D and EASA AMC 20-115DWhat it asksThe FAA and EASA recognise DO-178C (ED-12C), with DO-330 for tool qualification, as an acceptable means of showing that airborne software meets the airworthiness rules, under the plans you agree with your certification authority.What Neural Inverse gives youEvidence toward DO-178C: changes to requirements, trace data and release branches with their approver and reason, in a tamper-evident record. Agents are denied changes to qualified-tool configuration and released baselines.

Airworthiness security: EASA CS 25.1319 and AMC 20-42What it asksLarge aeroplane systems and networks are protected from intentional unauthorised electronic interaction, with security risks identified, assessed and mitigated. EASA recognises ED-202A / DO-326A as an acceptable means; the FAA proposed an equivalent rule for transport category aircraft in August 2024.What Neural Inverse gives youRecords of who changed flight software and its trace data, with the named approver and reason, for your security process. Signed evidence packs say which lines AI touched, which model was used and who approved.

Questions

What avionics teams ask us first.

All questions

Does Neural Inverse work with the tools we have already qualified?

Yes. The Embedded and HDL modules drive the compilers, probes and FPGA tools you already qualified; they do not replace them. The modules are pre-release: the open FPGA flow is verified on Linux, firmware support is built and tested on recorded tool output, and the vendor FPGA flows are not yet run against the vendor tools.

Can it run on a closed or air-gapped network?

Yes. Govern runs self-hosted, in your cloud account or air-gapped, installed from an offline bundle with models served inside your network. Run each release on a host with no route out before you rely on it.

Is Neural Inverse qualified under DO-330 or certified to DO-178C?

No. Govern gives evidence toward DO-178C, DO-254 and DO-330 for your plans. Tool qualification and certification stay with you and your certification authority.

Can an AI agent change requirements or trace data on its own?

No. The avionics template makes agent changes to requirements and trace data wait for a named approver, and denies agent changes to qualified-tool configuration and released baselines.

What can we give our certification liaison?

The audit record and signed evidence packs, which say which lines AI touched, which model and context were used and who approved. Anyone can verify an evidence pack offline.

Products used

Neural Inverse Build →

Editor, Agents and CLI with the domain tools your engineers need.

Neural Inverse Govern →

Policy, approvals and audit for every AI tool your teams use.

Product names belong to their owners.

Talk to our team.

Neural Inverse is available by request. We work with your engineering, security and procurement teams from the first conversation.

Request access Contact us