
Device software with a change record your auditors can follow.
For firmware and software teams under IEC 62304. Agents never read patient data, and controlled items wait for a named approver.
- Standards
- IEC 62304 · ISO 14971
- Firmware tools
- Arm GCC, Arm Compiler 6, IAR, J-Link, ST-LINK
- Agent policy
- Medical sector template
- Models
- Approved by your organisation, or self-hosted
- Deployment
- Self-hosted, your cloud or air-gapped
What your team gets
Your quality system, with AI inside its rules.
Govern features are in use today. Domain modules are pre-release; their state is listed under Tools and formats.
Who uses it
For the engineers who change the device and the people who release it.
Tools and formats
What the Embedded module handles, and how far it is verified.
The module drives the compilers and probes your team already uses. It turns on by itself in a trusted workspace with a firmware project.
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.
- ProposeAn engineer or agent drafts a change to device software.
- VerifyYour qualified tools build, check and test it.
- ApproveA push to main or a release branch waits for a named approver.
- RecordChange, results and approval kept together in the audit record.
Standards
Evidence for your quality system. The clearance is yours.
Neural Inverse provides evidence toward these standards. Certification stays with your organisation and assessor.
Products used
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.