ETAS lives in one of the least visible but increasingly important parts of automotive engineering: the software inside the vehicle.
A wholly owned subsidiary of Robert Bosch GmbH, ETAS develops software and tools for automotive embedded systems, ECU development, measurement and calibration, diagnostics, AUTOSAR, middleware, cybersecurity and software-defined vehicle platforms. The company reports approximately 2,700 employees across 39 locations in 14 countries and €542 million in 2025 sales.
For engineers evaluating automotive software, ETAS is particularly important because its tools sit directly between the software engineers writing vehicle functions and the physical ECUs, networks and vehicles those functions must eventually control.

As vehicles become software-defined, that position becomes increasingly significant.
What Does ETAS Software Do?
ETAS tools support several stages of embedded automotive software development.
Depending on the product, engineers can use ETAS software to:
- Develop ECU software
- Configure AUTOSAR platforms
- Measure signals from ECUs and vehicle networks
- Calibrate ECU parameters
- Perform diagnostics
- Analyze measurement data
- Automate ECU calibration and testing
- Develop and validate software before physical hardware is available
- Manage cybersecurity across vehicle development and operation
- Build software platforms for software-defined vehicles
ETAS describes its current business around basic software, measurement and calibration, middleware, diagnostics, cybersecurity and automotive software platforms.
That makes ETAS somewhat difficult to place into a single software category.
It belongs under Verification & Test.
It belongs under Embedded Software Development.
And increasingly, ETAS belongs squarely in the conversation around software-defined vehicles.
ETAS INCA
If one ETAS product is most likely to be familiar to automotive calibration engineers, it is INCA.
INCA is a software environment for:
- ECU measurement
- Calibration
- Diagnostics
- Data acquisition
- Vehicle-bus monitoring
- ECU flashing
- Test-bench integration
- Measurement-data recording
Engineers can use INCA during simulation, on test benches and in actual vehicles. ETAS says the software supports ECUs from different manufacturers and established ASAM interfaces used in automotive development.
Calibration is one of those engineering activities that can sound deceptively simple.
An ECU may contain thousands of parameters controlling how vehicle functions behave.
Those parameters can govern things such as:
- Torque delivery
- Battery management
- Thermal behavior
- Charging
- Electric-motor control
- Transmission behavior
- Emissions
- Fuel injection
- Driver-assistance functions
- Diagnostics
Engineers need to change those values, measure what happens and repeat the process—often thousands of times.
INCA provides the environment for performing that work.
Why ECU Calibration Still Matters in Electric Vehicles
It would be easy to associate calibration software primarily with combustion engines.
That would be a mistake.
Electric vehicles eliminate many traditional engine parameters, but they introduce entirely different control problems.
EV engineers still have to calibrate:
- Electric-motor behavior
- Inverter control
- Battery charging and discharge limits
- Regenerative braking
- Thermal-management systems
- Battery protection strategies
- Torque delivery
- Energy-management functions
- Vehicle drive modes
A modern EV remains an enormously complex control system.
The power source changed.
The need to make dozens of interacting control systems behave properly did not.
INCA-FLOW
INCA-FLOW extends the calibration environment by allowing engineers to automate calibration and testing procedures graphically rather than requiring extensive custom programming.
ETAS says workflows created in INCA-FLOW can be used across vehicles, test benches, Hardware-in-the-Loop systems and co-simulation environments.
This is important because calibration work can become extremely repetitive.
Instead of an engineer manually running the same procedure again and again while changing parameters, automation allows the process to be reproduced consistently.
That can improve both speed and repeatability.
ETAS RTA-CAR and AUTOSAR
ETAS also plays an important role deeper inside automotive embedded software.
RTA-CAR is the company’s AUTOSAR Classic platform.
AUTOSAR—Automotive Open System Architecture—is an industry standard intended to create common software architectures and interfaces for automotive ECUs.
RTA-CAR provides software components that engineers can use as the foundation for ECU applications rather than developing every underlying software capability independently.
ETAS says RTA-CAR has been deployed in approximately 4 billion production ECUs and is used by more than 350 customers worldwide.
That number illustrates why companies such as ETAS matter even though consumers rarely hear their names.
A driver may never know that ETAS software exists.
Yet software derived from ETAS technology may be operating inside an ECU controlling some portion of the vehicle.
What Is AUTOSAR Classic?
Traditional vehicles commonly distribute functions across many individual ECUs.
One controller may handle doors.
Another may control a seat.
Another may manage powertrain functions.
Another may operate braking or body electronics.
AUTOSAR Classic provides a standardized software architecture for many of these deeply embedded, real-time controllers.
ETAS RTA-CAR helps automotive companies configure and deploy that software foundation.
As automotive architectures move toward centralized computing and zonal architecture, AUTOSAR Classic will not necessarily disappear.
Instead, traditional ECUs and newer centralized computers may coexist for many years.
That makes tools capable of bridging generations of vehicle architecture particularly important.
ETAS and Software-Defined Vehicles
This is where ETAS becomes particularly interesting for the future of automotive engineering.
ETAS has repositioned much of its portfolio around the software-defined vehicle.
The company now offers a Vehicle Software Platform Suite intended to provide reusable vehicle software foundations across different vehicle programs and hardware architectures. In 2026, ETAS announced an initial implementation incorporating Eclipse S-CORE, an open-source middleware initiative aimed at future automotive software platforms.
ETAS is also a founding member of the Eclipse Software Defined Vehicle Working Group and helped initiate the S-CORE project.
That represents a major change in automotive software philosophy.
Historically, automakers and suppliers frequently developed software stacks around individual ECUs, suppliers and vehicle programs.
The SDV model increasingly demands:
Reusable software platforms that can span vehicles, hardware generations and model programs.
That is exactly the problem ETAS is positioning itself to solve.
See also:
What Is a Software-Defined Vehicle—and Why Is It Changing Automotive Engineering?
and
What Is Zonal Architecture?
ETAS Vehicle Software Platform Suite
The ETAS Vehicle Software Platform Suite is designed to provide standardized platform software that can support automotive applications across different computing environments.
Rather than forcing every automaker or supplier to recreate underlying infrastructure for every new vehicle, the idea is to create a reusable foundation upon which vehicle functions can be developed.
ETAS says its approach combines open-source technologies, open standards and production-grade automotive software.
That distinction is important.
Open-source software can speed innovation enormously.
But automotive production software must also meet demanding requirements for:
- Functional safety
- Cybersecurity
- Deterministic behavior
- Long vehicle lifecycles
- Hardware compatibility
- Regulatory compliance
The interesting engineering challenge is therefore not simply:
Can automotive companies use open-source software?
It is:
How do they turn open-source innovation into software trustworthy enough to operate inside millions of vehicles?
ETAS is trying to occupy that bridge.
ETAS and Automotive Cybersecurity
Software-defined vehicles create another unavoidable problem:
A vehicle containing more software and connectivity also creates more opportunities for attack.
ETAS has therefore built a significant cybersecurity portfolio.
The company’s security offerings cover areas such as:
- Vehicle cybersecurity
- Embedded security
- Key management
- Secure software updates
- Authentication
- Security testing
- Vehicle Security Operations Centers
- Threat detection
- Cybersecurity lifecycle management
ETAS integrated the former ESCRYPT cybersecurity business into the ETAS brand beginning in 2023.
One example is the ETAS Production Key Platform, which manages cryptographic keys and certificates used for secure ECU provisioning, onboard communication, software signing, authentication and OTA updates. ETAS positions it for compliance with automotive cybersecurity standards and regulations including ISO 21434 and UNECE R155.
This becomes particularly important for software-defined vehicles.
If vehicle functionality can change through over-the-air software updates, an automaker must be able to prove that:
The software actually came from an authorized source.
A compromised software-update mechanism could potentially become a vehicle-wide security vulnerability.
ETAS Measurement Data Analysis
Modern automotive development generates enormous amounts of data.
Road tests, ECU measurements, simulations and test benches can produce thousands or millions of signals.
ETAS offers several tools for working with that information.
The ETAS Analytics Toolbox, or EATB, can automatically search, analyze, visualize and report large volumes of measurement data. It can be used for ECU development, test-bench work and road-test analysis.
INCA also includes measurement-data workflows and can work with ETAS MDA for analyzing recorded test data.
This is another increasingly important part of automotive engineering.
Creating data is no longer difficult.
Finding the useful engineering information hiding inside the data is the harder problem.
ETAS and MIL, SIL and HIL Testing
ETAS tools also participate in the broader automotive verification process.
Vehicle software can be evaluated across:
Model-in-the-Loop (MIL)
Test the control algorithm as a model.
Software-in-the-Loop (SIL)
Compile and test the actual software in a simulated environment.
Hardware-in-the-Loop (HIL)
Run software on real electronic hardware while simulating the vehicle around it.
Vehicle testing
Finally validate the behavior in the physical vehicle.
ETAS INCA and INCA-FLOW can operate across simulation, test benches, HIL environments and physical vehicles, helping engineers carry calibration and measurement workflows through multiple stages of development.
For a deeper explanation, see:
Automotive MIL vs. SIL vs. HIL: How Engineers Test a Car Before the Car Exists
EHANDBOOK-NAVIGATOR
One of the more approachable ETAS products is EHANDBOOK-NAVIGATOR.
The tool provides interactive documentation for ECU software.
Instead of engineers searching through static documents trying to understand how a function works, EHANDBOOK can present software functions, models and relationships interactively.
It can also connect directly with an INCA experiment so engineers can relate measured or calibrated parameters to the corresponding software-function documentation.
This may sound like a relatively minor capability compared with ECU software platforms or calibration tools.
But increasingly complex vehicle software creates a serious documentation problem.
Engineers must understand not merely what a parameter is called, but:
What function does it belong to?
What other functions depend on it?
What happens when it changes?
That becomes harder as vehicle software grows.
Does ETAS Offer a Free Trial?
Yes — ETAS does provide software evaluation options.
ETAS operates an online licensing and trial portal that explicitly offers product evaluation, stating that users can evaluate ETAS software for free before deciding whether to purchase.
However, trial availability and procedures appear to vary by product.
One particularly clear example is EHANDBOOK-NAVIGATOR, for which ETAS offers the full software version free for a limited evaluation period. Users register for access to the ETAS License & Download Portal and obtain a trial license.
For more specialized products such as INCA, RTA-CAR, enterprise cybersecurity systems or the Vehicle Software Platform Suite, evaluation may require engagement with ETAS rather than a simple anonymous download.
For EngineeringSoftwareTrials readers, that means:
ETAS does support software evaluation—but do not assume every product follows the same self-service trial process.
What Should You Evaluate During an ETAS Trial?
ETAS products often become deeply embedded in an automotive development workflow.
That makes integration just as important as individual product features.
For INCA and calibration tools, evaluate:
- ECU compatibility
- Measurement performance
- Calibration workflow
- Test-bench integration
- Vehicle-network support
- Data-management capabilities
- ASAM support
- Automation
- Measurement-data analysis
- Learning curve
For AUTOSAR and embedded-software products, evaluate:
- Supported microcontrollers
- AUTOSAR compliance
- Memory footprint
- Runtime performance
- Functional-safety requirements
- Cybersecurity requirements
- CI/CD integration
- Configuration workflow
- Build performance
- Existing OEM requirements
For SDV platform software, evaluate:
- Hardware independence
- Middleware architecture
- Software portability
- Container support
- Open-source dependencies
- Functional-safety strategy
- Cybersecurity
- OTA compatibility
- Application lifecycle management
- Long-term vendor support
And perhaps most importantly:
Can your engineering team understand and maintain the resulting system without becoming permanently dependent on consultants?
Automotive software platforms can live inside vehicle programs for many years.
Ease of maintenance deserves nearly as much attention as initial deployment.
Who Should Consider ETAS?
ETAS is particularly relevant to:
- Automotive OEMs
- Tier 1 suppliers
- ECU developers
- Embedded-software teams
- Calibration engineers
- Powertrain engineers
- EV controls teams
- AUTOSAR developers
- SDV platform teams
- Automotive cybersecurity teams
- Test and validation organizations
- Vehicle diagnostics teams
It is much less relevant to engineers primarily looking for CAD, traditional FEA or standalone CFD.
ETAS lives primarily in the vehicle’s electronic and software nervous system.
ETAS vs. Vector, dSPACE and MathWorks
ETAS overlaps with several vendors already included in our automotive software coverage.
Vector is particularly strong in vehicle networks, ECU software, CAN communication, diagnostics and embedded development.
dSPACE is particularly strong in rapid control prototyping, HIL testing and real-time simulation.
MathWorks dominates model-based design and control-algorithm development through MATLAB and Simulink.
ETAS is especially strong in ECU measurement and calibration, AUTOSAR basic software, embedded platforms and automotive cybersecurity.
There is substantial overlap.
Large automotive organizations may use products from all four vendors.
That is important when evaluating automotive software:
This is rarely a winner-take-all software category.
Automotive toolchains tend to be ecosystems.
The real question is often not:
Which vendor replaces everything else?
It is:
Which tools should own which parts of the development workflow—and how well do they exchange models, data and test results?
The EngineeringSoftwareTrials Verdict
ETAS becomes more interesting the more software moves toward the center of automotive engineering.
Twenty years ago, many engineers could reasonably think of ECU calibration and embedded software as specialized activities downstream from the “real” vehicle engineering.
That distinction is disappearing.
A modern vehicle’s behavior increasingly depends on software governing:
- Acceleration
- Braking
- Steering
- Battery behavior
- Charging
- Driver assistance
- Thermal management
- Comfort
- Connectivity
- Diagnostics
And software-defined vehicles push that evolution even further.
ETAS operates squarely inside that transformation.
Its traditional strength in ECU measurement and calibration gives the company deep roots in existing automotive development, while its investments in AUTOSAR, middleware, open-source SDV platforms and cybersecurity point toward the next generation of vehicles.
For engineering organizations evaluating ETAS, the biggest question may therefore be larger than whether one software tool performs a particular task well.
It is:
How much of your future vehicle software architecture do you want one vendor helping to define?
That is worth evaluating very carefully.
Trial Availability
Free trial/evaluation available: Yes, for at least some ETAS products.
Clear self-service example: EHANDBOOK-NAVIGATOR offers a free limited-time evaluation.
Broader evaluation program: ETAS provides free product-evaluation licensing through its licensing portal, although the process varies by product.
Best fit: ECU software development, automotive calibration, measurement, AUTOSAR, embedded platforms, SDV development and automotive cybersecurity.
EST recommendation: Strongly worth evaluating for organizations developing the electronic and software architecture of modern vehicles.
