# Industries > Ten industries, each with its own tools, standards and sign-off. Neural Inverse works inside all of them. Source: https://neuralinverse.com/industries/ --- ![](/photos/facility.jpg) Industries # Where software is audited. Ten industries, each with its own tools, standards and sign-off. Neural Inverse works inside all of them. [Aerospace and defence](https://neuralinverse.com/#group-0)[Mobility and devices](https://neuralinverse.com/#group-1)[Industry and infrastructure](https://neuralinverse.com/#group-2)[Financial services](https://neuralinverse.com/#group-3)[Domain modules](https://neuralinverse.com/#modules) ## Aerospace and defence DO-178C · DO-254 · DO-330 ### [Avionics](https://neuralinverse.com/industries/avionics/) Airborne software, with every controlled item approved by name. Domain module: Embedded · HDL - Requirements and trace data changed only with a named approver - Firmware and FPGA work in one editor - Runs on closed networks with self-hosted models ![](/photos/hangar.jpg) MIL-STD-882E · ECSS-E-ST-40C · DO-254 ### [Defence and space](https://neuralinverse.com/industries/defence/) Mission software built entirely inside your boundary. Domain module: Embedded · HDL - Fully disconnected, with models you host - A separate organisation, policy and audit chain per programme - Records your auditor verifies offline ## Mobility and devices ISO 26262 · ISO/SAE 21434 · ASPICE ### [Automotive](https://neuralinverse.com/industries/automotive/) Vehicle software, with every write to an ECU approved by an engineer. Domain module: Automotive - Code, bus traces and diagnostics together - Works with the interfaces already on your bench - Generated code protected from AI edits ![](/photos/bench.jpg) IEC 62304 · ISO 14971 ### [Medical devices](https://neuralinverse.com/industries/medical/) Device software with a change record your auditors can follow. Domain module: Embedded - Agents never read patient data - Controlled items wait for a named approver - Signed evidence for your design history file ![](/photos/team.jpg) DO-254 · ISO 26262 ### [Semiconductors and FPGA](https://neuralinverse.com/industries/semiconductors/) Close timing sooner, on the licences you already hold. Domain module: HDL - Open tools verified on Linux; vendor tools driven in batch - Timing and lint on the line that caused them - One way of working across vendors ## Industry and infrastructure IEC 61850 · IEC 62443 ### [Energy and utilities](https://neuralinverse.com/industries/energy/) Station files checked before they reach site. Domain module: Energy - SCL from any IEC 61850 tool, read losslessly - Automatic checks before anything is issued - Clear differences between revisions ![](/photos/facility.jpg) IEC 61131-3 · IEC 62443 ### [Industrial automation](https://neuralinverse.com/industries/industrial/) Control logic reviewed before it reaches the plant. Domain module: PLC · DCS - Structured Text for TwinCAT 3; DeltaV from its exports - Builds still go through your vendor tools - Agents never download to a controller Your quality system's change control ### [CNC and machining](https://neuralinverse.com/industries/cnc/) Machine programs and the code around them, changed on record. Domain module: None yet - Programs and post-processors compared as text - Agents kept off the shop-floor network - Every change with its approver TL 9000 ### [Telecommunications](https://neuralinverse.com/industries/telecom/) Network software changed with approval and on record. Domain module: None yet - Governed AI coding with your own models - Production kept out of agents' reach - Every change with its approver ## Financial services SOX · PCI DSS ### [Banking and mainframe](https://neuralinverse.com/industries/banking/) Modern COBOL development without leaving z/OS. Domain module: Mainframe - No conversion, no new runtime, no migration - A familiar editor instead of green screens - Agents never submit jobs or bind Db2 packages Domain modules ## Where the Editor goes deeper. Eight of the ten industries have a module that drives their vendor tools and reads their file formats. Each module is pre-release, and a capability moves to verified only on evidence. [Verification state of each module](https://neuralinverse.com/docs/build/domain-modules/) - **Embedded:** Microcontroller firmware: build, flash, debug and static analysis. Built and tested on recorded tool output; running an image in QEMU is verified. - **HDL:** FPGA and ASIC design. The open flow is verified on Linux; the vendor flows are in verification. - **Automotive:** Networks, diagnostics and calibration. Sample-file readers, XCP and the virtual bus are verified; vendor interfaces are in verification. - **Energy:** IEC 61850 substations. The SCL reader and checks are verified on 292 public files, and online MMS against open-source servers. - **PLC and DCS:** TwinCAT 3 and DeltaV. Modelled, with verification kits ready. - **Mainframe:** COBOL, copybooks and JCL on z/OS. The workstation path is verified on Linux; the z/OS path is in verification. - **Modules in development:** Dedicated modules are being built. Today: governed AI coding, named approvals and the audit record from Build and Govern. Nothing is verified by a customer yet. Govern works the same in every industry, with or without a module. In every industry ## The same three guarantees. Qualified tools stay qualified Builds run on the compilers and vendor tools you certified. People approve what matters An engineer confirms every write to hardware, and the agent actions your policy marks wait for a named approver. Every change on record Who changed what, why, and who approved it, ready for audit. Neural Inverse provides evidence toward these standards. Certification stays with your organisation and assessor. ![](/photos/team.jpg) ## 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](https://neuralinverse.com/contact/?topic=access)[Contact us](https://neuralinverse.com/contact/)