Use CasesFirmware developers

Find bugs before they reach production

Metalware tests candidate builds in your CI pipeline automatically, no hardware or test harness required.

Quality at scale

Bridge the gap in embedded testing

You don't have to choose anymore. Metalware delivers the scalability of software testing with the fidelity of hardware testing.

What tests miss

How Metalware compares

Unit testsStatic analysis (SAST)Simulation / SILHardware in the loopField testing
Find bugs without writing testsNoYesNoYesNoPartly (note 1)
Finds reliability defectsNoPartly (note 2)PartlyYesPartlyYes
Tests vendor SDK and RTOS codeNoPartly (note 3)Partly (note 4)YesYesYes
Tests the binary you shipNoNoPartlyYesYesYes
Findings confirmed by running themYesNoYesYesYesYes
Reproducible in your debuggerYesNoPartlyYesPartlyNo
Root cause pinpointedPartlyYesPartlyYesNoNo
No test code to maintainNoYesNoYesNoPartly
No hardware neededYesYesYesYesNoNo
Runs on every CI buildYesYesYesYesPartlyNo
Time to resultsSecondsMinutesMinutesHoursHoursWeeks
Catches electrical and physical faultsNoNoNoNoPartlyYes
  1. Note 1: Eventually, from customers, where cost/risk is highest
  2. Note 2: Only some types of failures, typically high false-positive rates
  3. Note 3: Only if the vendor provides source
  4. Note 4: Often stubbed or mocked

Works with your pipeline

Test each build without holding up the pipeline

Integrations

  1. Step 1: Build

    Your release build produces the firmware binary as it does today.

  2. Step 2: Submit

    A CI job uploads the binary, and the analysis runs unattended.

  3. Step 3: Review

    Your team reviews the findings and fixes what it confirms before the build ships.

Every binary your pipeline produces can get its own analysis, in parallel.

What you get

Everything you need to start a fix

Root cause
Each defect explained in the code, with its defect class.
Triggers
The input or conditions that caused the defect.
Reports
PDF reports to attach to a ticket or send to a supplier.
Integrations
Replay POCs in GDB, Ghidra, or Binary Ninja.
Metalware defect in an Ethernet MQTT client: risk Critical, peripheral Ethernet_DMA, CWE-787, out-of-bounds write, with a one-line summary: mqtt_parse_incoming accepts an overlong MQTT Remaining Length encoding, so broker-supplied Ethernet data can write past the client's 128-byte receive array into its output ring buffer.

Bring a recent release build