Trust the firmware that runs the physical world

Metalware is the first AI-native platform that finds security and reliability flaws in the embedded systems we rely on.

No source code, hardware or test harness required.

Drawing: Survey quadcopter. The firmware fc_main.bin runs on the flight controller, highlighted in the drawing. The firmware talks to the GNSS receiver (UART), the IMU (SPI), the motor ESCs (PWM), the barometer (I2C), the radio link (UART) and the gimbal (CAN).

Drawing: Survey quadcopter. The firmware fc_main.bin runs on the flight controller, highlighted in the drawing. The firmware talks to the GNSS receiver (UART), the IMU (SPI), the motor ESCs (PWM), the barometer (I2C), the radio link (UART) and the gimbal (CAN).

ISB 2025 · Top 10 startup

Read announcement

Binary input

Diagram: from the compiled binary alone, Metalware identifies the drone's chip and stands up an emulator of it, with a peripheral on the chip for each of the drone's six parts. The firmware binary runs on an emulated STM32F427 in the frame named EMULATION, with SPI1 for the IMU, I2C1 for the barometer, USART2 for the GNSS receiver, USART1 for the radio link, TIM1 for the motor ESCs and CAN1 for the gimbal; the parts themselves stay outside the emulation.

Diagram: from the compiled binary alone, Metalware identifies the drone's chip and stands up an emulator of it, with a peripheral on the chip for each of the drone's six parts. The firmware binary runs on an emulated STM32F427 in the frame named EMULATION, with SPI1 for the IMU, I2C1 for the barometer, USART2 for the GNSS receiver, USART1 for the radio link, TIM1 for the motor ESCs and CAN1 for the gimbal; the parts themselves stay outside the emulation.

Metalware analyzes compiled firmware binaries.

It automatically detects the architecture, memory map, and chip, and stands up a custom, highly instrumented emulator to enable analysis and validate findings.

Binary analysis and emulation

Advanced analysis

Diagram: twenty of Metalware's AI agents, in rows and columns, work on the drone's firmware running in the frame named EMULATION. Four two-way links run between the agents and the emulation: the agents act on it and read back the result. Each finding comes out of the emulation traced to its root cause and mapped to a CWE.

Diagram: twenty of Metalware's AI agents, in rows and columns, work on the drone's firmware running in the frame named EMULATION. Four two-way links run between the agents and the emulation: the agents act on it and read back the result. Each finding comes out of the emulation traced to its root cause and mapped to a CWE.

Metalware uses a suite of analysis techniques to find bugs, including custom AI agents that use the emulator to produce confirmed, reachable findings.

Findings are traced to their root cause, deduplicated, and mapped to a CWE.

Security testingReliability testingFindings & evidence

Automation enables scale

Diagram: by hand, the five steps for one firmware binary (reverse engineer, build environment, exercise inputs, triage, write report) run one after another across weeks of expert work. With Metalware, a stack of firmware binaries goes through one automated analysis and returns findings in 24 hours.

Diagram: by hand, the five steps for one firmware binary (reverse engineer, build environment, exercise inputs, triage, write report) run one after another across weeks of expert work. With Metalware, a stack of firmware binaries goes through one automated analysis and returns findings in 24 hours.

Metalware lets teams move from spot checks to full analysis of every binary in a fleet, in parallel.

By hand, one binary takes weeks of expert work across a chain of tools:

Rebuild the target
Ghidra or IDA, vendor datasheets
Emulate and fuzz
QEMU, custom stubs, AFL++
Sort the crashes
Debugger, spreadsheets
Report the findings
Days of writing

With Metalware, the same work runs as one automated 24-hour analysis, so a team can keep up with every version of every component.

For the entire firmware lifecycle

The build Metalware tests is the one that reaches the field. Developers build v4.6 of fc_main.bin and load it onto the drone's flight controller; integrators build it into the drone with six other parts; an aerial survey operator runs 24 drones on three versions, 3 on v4.4, 18 on v4.5 and 3 on v4.6; the hand circles v4.6, the build Metalware tested.

The build Metalware tests is the one that reaches the field. Developers build v4.6 of fc_main.bin and load it onto the drone's flight controller; integrators build it into the drone with six other parts; an aerial survey operator runs 24 drones on three versions, 3 on v4.4, 18 on v4.5 and 3 on v4.6; the hand circles v4.6, the build Metalware tested.

DevelopersFirmware developers
Test firmware as it's compiled and fix defects before delivery by integrating Metalware into your CI/CD pipeline.
IntegratorsSupply chain assurance
Assess supplier, COTS, and inherited firmware delivered without source code, before integration.
OperatorsIndustrial & critical infrastructure
Ensure your systems are secure and reliable, validate updates, and inform risk decisions with ground truth, not vendor attestation.