Vehicle software, with every ECU write approved.

For network, ECU, validation, diagnostics and calibration engineers. Your interfaces, databases and vendor tools stay as they are.

Standards: ISO 26262 · ISO/SAE 21434 · ASPICE
Databases: DBC, LDF, ARXML, A2L, ODX
Protocols: CAN, LIN, UDS, DoIP, XCP
Interfaces: Vector, PEAK, Kvaser, python-can
Deployment: Self-hosted, your cloud or air-gapped

What your team gets

CAN, diagnostics and calibration in the IDE.

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

Network databasesDBC, LDF and ARXML as tables and bit layouts, with consistency checks and navigation.

The bus on your benchVector, PEAK and Kvaser interfaces through each vendor's own library, or a virtual bus for tests and CI.

Traces and simulationDecoded traces and a live bus monitor; the rest of the network simulated from the database.

Diagnostics and calibrationUDS diagnostics on CAN or DoIP; XCP measurement and calibration from the A2L.

Generated code protectedThe automotive template denies agent edits to Embedded Coder output and the AUTOSAR RTE. Changes to safety components, A2L and ARXML wait for a named approver.

Who uses it

One environment for every role around the vehicle network.

Network engineersMaintain DBC, LDF and ARXML databases and check them for consistency.

ECU software engineersWrite and debug ECU code with the bus and its signals beside it.

Validation engineersRun software-in-the-loop tests on a virtual bus in CI, and replay recorded traces.

Diagnostics engineersRead fault memory, data identifiers and routines over UDS.

Calibration engineersMeasure and calibrate over XCP from the A2L.

Tools and formats

What the Automotive module handles, and how far each is verified.

The module turns on by itself in a trusted workspace that holds automotive work.

Databases and descriptionsRead, checked and navigated; encoding and decoding; C code generated from a database. DBC and ARXML reading, the codec and ODX are verified on vendor and standards-body sample files, which are demo size.DBC · LDF · ARXML · A2L · CDD · ODX · PDX

Bus interfacesEach vendor's interface through its own installed library. The bus monitor is verified on python-can's virtual interfaces. Vector, PEAK and Kvaser are kit shipped: run only against test libraries.Vector · PEAK · Kvaser · python-can

Diagnostics and calibrationUDS over CAN and DoIP; XCP from the A2L. XCP is verified against XCPlite.UDS · ISO-TP · DoIP · XCP

Traces and testsCAN traces and Ethernet captures opened and decoded; CANoe test units run through CANoe4SW Server Edition. Modelled.CAN traces · Ethernet captures · CANoe4SW Server Edition

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

Tested on Linux only, with no CAN hardware and no real ECU, and nothing the module writes has yet been opened in the vendor tools. 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 ECU software.
Verify
Your qualified tools build, check and test it.
Approve
Changes to safety components and calibration data wait for a named approver.
Record
Change, results and approval kept together in the audit record.

Standards

Evidence for your safety and security cases. The certification is yours.

ISO 26262Evidence toward ISO 26262: changes to safety-relevant components with their named approver, and generated code kept out of agents' reach.

ISO/SAE 21434Evidence toward ISO/SAE 21434: agent reads of ECU keys and certificates are denied and logged.

ASPICEEvidence toward ASPICE assessments: every change kept with its reason, 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]

UN Regulation No. 155What it asksVehicle manufacturers run a certified cyber security management system and show that each vehicle type is protected against cyber attack. In the EU it has applied to new vehicle types since 6 July 2022 and to all new vehicles since 7 July 2024.What Neural Inverse gives youEvidence toward ISO/SAE 21434: the automotive template denies and logs agent reads of ECU keys and certificates, and changes to safety components, A2L and ARXML wait for a named approver.

UN Regulation No. 156What it asksVehicle manufacturers run a software update management system that records the software on each vehicle type and controls every update. In the EU it has applied on the same dates as UN Regulation No. 155.What Neural Inverse gives youEvery change kept with its reason, review and approval, in a tamper-evident audit log you can export. Generated code from Embedded Coder and the AUTOSAR RTE is kept out of agents' reach.

China GB 44495-2024What it asksChina's mandatory vehicle cyber security requirements: a cyber security management system and protection of the vehicle's external connections, communications, software updates and data. It applies to new vehicle types from 1 January 2026, alongside GB 44496-2024 on software updates.What Neural Inverse gives youSelf-hosted or in your own cloud account, in the region you choose, with the same records of changes and approvals wherever Govern runs.

Questions

What automotive teams ask us first.

All questions

Does it work with our interfaces and vendor tools?

The Automotive module uses each vendor's interface through its own installed library. The bus monitor is verified on python-can's virtual interfaces; Vector, PEAK and Kvaser are kit shipped and run only against test libraries. The module is pre-release, tested on Linux only, with no CAN hardware and no real ECU.

Can it run on-premises or air-gapped?

Yes. Govern runs on your own servers, in your own cloud account or on a network with no internet access, with models you host. The controls and the audit record are the same in each option.

Is Neural Inverse certified to ISO 26262 or ISO/SAE 21434?

No. Govern gives evidence toward ISO 26262, ISO/SAE 21434 and ASPICE assessments. Tool qualification and certification stay with you and your assessor.

Can an AI agent change generated code or calibration data?

The automotive template denies agent edits to Embedded Coder output and the AUTOSAR RTE. Changes to safety components, A2L and ARXML wait for a named approver.

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