Products
The Testradamus family.
Testradamus is TraceSpeak’s AI platform for vehicle software validation. Every product runs on the same core: an understanding of your vehicle network, agents built on automotive embedded expertise, and AI that runs locally on your hardware.
Testradamus CT
Where: integration and system test, CI and HiL.
“Why did this test fail, is the verdict right, and which commit caused it?”
Explore Testradamus CT →Testradamus Fleet
Where: vehicle validation fleets, field fleets later.
“What happened, on which vehicles and software, and whose is it?”
Join early access →Testradamus Test Drive
Where: vehicle test and road testing.
“What happened on this drive, and why?”
Join early access →Testradamus Enterprise
From the driver’s voice to the ECU’s fix.
Use all three products in one project. Test Drive hears the driver in every vehicle, Fleet finds the owner across the platform, and CT finds the commit for every ECU. The fix travels back the same way, with evidence at every step.
- Three tiers, one intelligence: One intelligence. Three tiers. In every vehicle, for every platform, for every ECU.
- New issue in the car: Test Drive checks every fresh log in every car, online or offline. On V-03 it finds a new issue: the HV lamp at wake-up.
- Explained by voice: Test Drive explains the new issue to the driver as it happens, before anyone opens a log.
- Checked on request: The driver asks for a signal. Test Drive answers with the measured and the expected values.
- Compared across vehicles: Online, Test Drive compares the issue with the other vehicles through Fleet. V-01 and V-07 show the same signature; V-05 answers when it is back online.
- Issue created in Fleet: With the issue package complete, Test Drive creates the issue in Fleet. Fleet maps ISS-0142 to the software build, the hardware variant and 5 vehicles.
- Sent to the ECU’s CT: Fleet sends ISS-0142 to the CT of the top suspect, CentralGateway at Supplier A. Only the sealed issue package crosses the company boundary, never the fleet data.
- Reproduced and fixed in CT: CT reproduces the issue on the HiL, ranks the suspect commit and checks the fixed build.
- New build back to the vehicles: The signed build crosses back. Fleet rolls it out to the vehicles; V-05 gets it in the workshop.
- Fix confirmed: Test Drive confirms zero occurrences in 212 wake-ups on B 21.5-rc.5. ISS-0142 is closed, with the evidence for every step.
Enable voiceover to hear the walkthrough and driver exchange. Scenario on the simulated Vulcan T7 vehicle. Versions, counts, commit ids and vehicle ids are simulated. Dashed tags mark CTs that run in a supplier’s network.
The shared core
One intelligence behind every product.
Understands your vehicle
Built from your network descriptions (DBC, ARXML, LDF, PDX): ECUs, signals, routing, timing and the functions they serve.
Runs locally
One workstation, one GPU, no cloud. Your code and data never leave your network.
Explains with evidence
Every answer cites its checks and carries a confidence score, so your engineers can verify it quickly.
See it on a simulated vehicle.
The Demo Playground runs Testradamus CT on realistic test runs, failures included.