Vehicle as Code - executable specification
RemotiveTopology orchestrates virtual, hybrid, and physical vehicle nodes - a stack-neutral integration layer that lets OEM and Tier 1 teams develop and validate SDV software long before silicon and test benches exist. Execute at vehicle level from day one, including the nodes that matter most: AD/ADAS, infotainment, and the full E/E communication fabric.
.gif)
The harness for Software Defined Vehicle
RemotiveTopology turns your existing E/E architecture into a running environment supporting testing, prototyping and development processes from day one to SOP. Explore live communication, test software virtually, and connect real hardware - all from the same platform. Everything is described in standardized text files. This simplifies version control, eliminates tool silos, and ensures every team member works from the same source of truth. Describe the architecture. Define what to instantiate and how. Run vehicle-level test cases - from SIL on a laptop to a full HIL rig.
Mix physical & virtual components
RemotiveTopology supports hybrid environments where physical components interact with simulations over production-grade communication (CAN, LIN, Ethernet). This includes SecOC/E2E protection, correct IP/MAC addresses, and VLANs. Virtual components run in containers and can be swapped for hardware when needed.
Hybrid HIL demo including ECU from National Instruments and physical rear lights. Move faster, test earlier, and integrate continuously - from day one. Virtual integration testing scales as components mature, without rewriting your tests.
Use your ARXML, DBC, FIBEX
RemotiveTopology uses your existing platform definition (ARXML, DBC, FIBEX etc) to understand what ECUs exist and how they communicate. The tooling also provides sensible defaults which allows for minimal configuration to create a runnable environment. With RemotiveStudio you can easily visualize and explore your ARXML/DBC files.
Smooth Continous Integration (CI)
RemotiveTopology is based on standard Linux development tools and adapts to your way of working. This means it can be run on any CI solution (eg GitHub actions, Jenkins, or Zuul) or any cloud provider (eg AWS, Azure or GCP). To create shared HIL rigs for CI pipelines simply use standard solutions such as GitHub action self-hosted runners.
SIL first, HIL when ready: Pipelines run tests in a virtual environment first, and only move to physical hardware when the build is stable. This ensures scarce HIL rigs are used efficiently.
Same tools everywhere: Developers use identical tools and test frameworks locally and in CI, making errors easy to replicate and resolve.
RemotiveTopology brings proven CI pipeline practices from modern software engineering into automotive. By maximizing the use of abundant software environments before scarce HIL resources, teams can validate and integrate earlier, reduce bottlenecks, and deliver better software faster.
Cost-efficient journey, avoiding SOP bottlenecks
Integrating RemotiveTopology scales testing with standardized hardware at lower cost, while enabling streamlined workflows in an open ecosystem. Using virtual integration testing, teams can validate integration scenarios before hardware is available. Shifting most of the stack to scalable SIL setups reduces setup time and effort, reserving expensive HIL rigs for tests where they add real value. By reusing the same tests across SIL, CI, and HIL, teams avoid duplication and repeated rebuilds.
Lower hardware costs: run the majority of tests virtually before reserving rigs.
Faster cycles: parallel SIL instances give quick feedback and reduce queue times.
One flow, less waste: keep the same test logic from developer laptops to HIL rigs, eliminating silos and late surprises.
With RemotiveTopology as the overall framework for consistency, HIL becomes a confirmation step, not a bottleneck, saving critical time as SOP approaches.
Get started
Explore documentation – Platform and instance setup
Review product page
Examples in GitHub
Request a demo
RemotiveTopology supports modern, modular, cross-team testing - from early software to advanced architectures. Whether you're prototyping next-gen ECUs or validating a central computing system, your team moves faster with one unified test flow.
Jump straight into action
Head over to the installation guide to set up RemotiveTopology in minutes. For practical examples and usage patterns, check out our GitHub repository.
for 30 days
Top use cases - smooth SIL to HIL workflows
Use RemotiveLabs tooling to bridge software and hardware testing —
from virtual prototypes to full HIL rigs.
Whether it’s hybrid setups, cloud-first AI development, or a software-first vehicle development platform you're after here are examples to show how teams scale faster and avoid late-stage surprises.
Lightweight setups combine virtual ECUs with selected hardware nodes for flexible and cost-efficient testing.
NXP uses a developer-centric workflow to train AI models using RemotiveCloud. The same setup then runs on hardware - within minutes.
The hybrid rig with Kvaser/EMC supports automated testing where virtual ECUs execute full vehicle architectures and hardware nodes are connected only where physical validation is required.
.jpg)
Bridge physical test systems with virtual environments. Validate embedded software earlier - with synchronized signals and shared test logic across virtual and physical setups.
Blog posts related to hybrid HIL
Join the automotive rebels that #getstuffdone with RemotiveLabs!
