RE4AAutomotive engineering & security tools
Language: EN · English
Request a demo
Menu

AI-assisted security engineering for the software-defined vehicle.

AI plans the tests. The bench proves them.

RE4A's AI reads your TARA and your legacy code, and proposes test plans and design documents for an engineer to approve. Verdicts are computed by rules against the ECU's own declared specification — never by a model.

Request a demoProducts

Your model or none: OpenAI Anthropic Ollama vLLM

CAN CAN-FD Automotive Ethernet SOME/IP UDS DoIP

RE4A Testing Studio — Network topology
Network topology view
ECU under testSimulated
  • 28 built-in test types, 27 armed by default

    built-in test types · 27 armed by default

  • 3.7 seconds: scan and static analysis of a 154-file ECU project

    scan and static analysis · 154-file ECU project

  • 4 model backends for Testing Studio's AI — your own OpenAI, Anthropic, Ollama or vLLM — or run with AI off

    model backends for Testing Studio's AI — or run with AI off

  • 100% on-premise: nothing leaves your network in the default configuration

    on-premise — nothing leaves your network in the default configuration

AI in RE4A

AI plans. The engineer decides. The bench proves.

  • Available today

    Drafts design-document prose; opt-in and off by default.

  • Available to demo

    Proposes test plans from your TARA; an engineer arms them.

  • Deliberately no AI

    Rule-based against the ECU's own specification; seeded and reproducible.

Your model or none — OpenAI, Anthropic, or a local Ollama or vLLM endpoint. AI is off by default, and a local model keeps requirement text on your network.

Standards and protocols it works with

  • UN R155 Annex 5
  • ISO/SAE 21434
  • GB 44495-2024
  • ASPICE SWE.2 / SWE.3
  • ISO 14229 UDS
  • ISO 13400 DoIP
  • AUTOSAR

Products

Code in, documents and evidence out. Four products, sold separately.

In production

Break the vehicle network before someone else does.

Test each ECU against its own declared PDX/ODX, with AI-proposed test plans from your TARA — available to demo.

Explore
RE4A Testing Studio — Test suite
Test suite view
Watch the bus CAN, CAN-FD and Ethernet, decoded liveAttack automatically 28 built-in test types, 27 armed by defaultEvidence each finding traceable to UN R155 Annex 5 rows

PDX/ODX-aware

  • UN R155
  • GB 44495
In production

Legacy ECU code in. ASPICE-ready documents out.

Reads legacy C/C++ with a fault-tolerant parser and writes the architecture and detailed design back out as ASPICE-ready documents.

Explore
RE4A Reverse Engineering — Scan
Reverse Engineering Scan tab
Scan · SDD · SAD · Generate the app’s own four steps3.7 s static analysis 154 files · 1,302 functions

No build system, no compiler

  • SAD · SDD · traceability.csv
  • On-premise AI assist, off by default
In production

Keep the ECU in a real vehicle state — without the whole vehicle.

Testing Studio's Simulation edition — rest-bus simulation, replay and frame injection — with Pentest or Fuzz, or on its own.

Explore

Rest-bus simulation

  • Capture and replay
  • Frame injection
Early access

From ISO/SAE 21434 TARA to an executable test plan.

A running build in early access, at the risk-assessment end of the lifecycle.

Explore
The ISO/SAE 21434 lifecycle loopTARA, then requirements, a test plan and evidence; findings loop back to the TARA. RE4ATara works at the TARA stage.Findings loop backTARARequirementsTest planEvidenceRE4ATara

ISO/SAE 21434

  • TARA to executable test plan

Why RE4A

Engineered for automotive reality.

Client and test serverThe Windows client talks to the Linux or WSL2 test server over 127.0.0.1: port 20009 for control, 20010 for streaming. The server drives the device under test.WindowsclientLinux / WSL2server127.0.0.1DUT20009 control20010 streaming

On-premise, air-gapped

0 bytes of source code leave the machine in the default configuration.

Same request, two oraclesThe crash-only oracle passes the ECU because it stayed up. The spec oracle fails it, because the answer is not declared in the PDX/ODX.Crash-onlyPASSSpec-basedFAIL

Evidence is the deliverable

Each verdict is computed against the ECU’s own PDX/ODX — not a crash signal.

  • ISO/SAE 21434
  • ASPICE SWE.2 / SWE.3

Standards and protocols

See it in motion

One scan. One test run.

An unedited walkthrough against synthetic demo data: a network scan, a testcase run, and the evidence it produces.

RE4A — Product walkthrough

The first ~24 seconds are AI-generated concept footage; the rest is a real, unedited screen capture.

Evaluate it

See it run against a real ECU — with no hardware on your side.

Rest-bus simulation around one real ECU. No hardware needed.

Request a demo
RE4A Testing Studio — Simulation
  • ECU1DUT · real
  • GatewayECUsimulated · playing
  • BodyECUsimulated · playing