Skip to content
PEKVOR
All industries
Industry

Automotive

A modern car is a distributed computer on wheels, and most of its code comes from suppliers. We build the software, security, and update pipelines that keep connected vehicles safe over their entire life.

By the numbers
100M+

lines of software code run in a modern vehicle, across more than 100 electronic control units.

Source: McKinsey, Rewiring Car Electronics & Software
~400M

connected cars projected on the road by 2025, up from roughly 237 million in 2021.

Source: Statista, Connected Cars, 2024
Where it breaks

The problems specific to automotive

Not generic digital-transformation talking points. These are the failure points we see in automotive systems.

01

Securing OTA update pipelines end to end

02

Managing vulnerabilities across tier-N supplier code

03

Meeting ISO 26262 ASIL timing on shared ECUs

04

CAN bus with no message authentication

How we engineer it

Concrete approaches, not slideware

1

Signed, staged OTA with rollback and hardware-rooted secure boot

2

Software bill of materials with continuous CVE monitoring per component

3

Domain/zonal architecture with an in-vehicle gateway and message authentication

Standards we build to

Compliance is a design input

We treat these as constraints to engineer against from day one — not paperwork to bolt on before launch.

UNECE WP.29 R155vehicle cyber-security management
UNECE WP.29 R156software update management (OTA)
ISO/SAE 21434vehicle cybersecurity engineering
ISO 26262functional safety (ASIL)
AUTOSAR / ASPICE
What you get

Outcomes we hold ourselves to

  • Updates that ship safely and roll back cleanly
  • Supplier code you can actually account for
  • Type-approval evidence for R155 and R156

Let us build what is next, together

Tell us about your goals and we will recommend a practical path forward.