Types of EV Architecture: From Skateboard to Software-Defined

Choosing an EV architecture is choosing your cost curve, variant flexibility, and software future for the next decade. A campus cargo cart and a long-haul truck need different answers — yet teams often borrow passenger-car vocabulary without mapping it to commercial reality. This guide clarifies the main architecture types and when each fits OEMs, assemblers, and fleet operators.

1. ICE conversion / adapted platforms

The fastest path to "electric" for some programmes is swapping an ICE powertrain for a motor and pack inside an existing body and chassis. It preserves tooling and supplier relationships. Trade-offs are structural: packaging compromises, suboptimal weight distribution, limited battery volume, and a vehicle network that was never designed for high-voltage diagnostics or OTA. Viable for niche volumes or interim fleets — rarely the long-term platform.

2. Dedicated skateboard platforms

A skateboard integrates battery, motors, suspension, and often thermal systems into a flat rolling chassis. Bodies (passenger, cargo, shuttle) bolt on top. This is the dominant modern EV pattern for purpose-built products: better packaging, lower centre of gravity, and cleaner high-voltage integration. ODMs like Triox specialise here because one skateboard can spawn many white-label bodies.

3. Modular / scalable platform families

Modular architectures define interfaces — battery module pitch, motor mounts, ECU connectors, CAN/Ethernet maps — so wheelbase, kWh, and payload change without a new programme. This is how commercial ODMs serve campus, last-mile, and light industrial duty cycles from one engineering backbone. The discipline is interface control: if modules leak coupling, "modular" becomes marketing.

• Fixed structural hard points with configurable length and track.
• Battery packs as field-replaceable or duty-cycle-selected modules.
• Shared electrical architecture across variants for common diagnostics.
• PLM-managed option codes so manufacturing and PDI know exact config per VIN.

4. Cell-to-pack and cell-to-chassis

Battery architecture is a sub-type with outsized impact. Module-based packs are serviceable and flexible. Cell-to-pack removes module housings for energy density. Cell-to-chassis embeds cells into the vehicle structure for maximum packaging efficiency — at the cost of service complexity and higher tooling investment. Commercial light EVs often prefer modular packs for depot swap and repair economics; passenger flagships push cell-to-chassis for range.

5. Electrical / E/E architecture types

Separately from the mechanical skateboard, vehicles differ in electronics topology:

1. Distributed ECUs — one box per function; simple historically, poor for software velocity.
2. Domain controllers — consolidated compute for powertrain, body, ADAS, cabin.
3. Zonal controllers — I/O by vehicle zone plus central HPC; shorter harness, Ethernet backbone.
4. Software-defined stack — domains/zones plus OTA, signed software BOM, and cloud twin.

6. Software-defined vs hardware-defined vehicles

A hardware-defined EV ships features frozen in firmware images that rarely change. A software-defined EV treats functions as updatable products: calibrations, fleet policies, diagnostics, and new capabilities after sale. Most programmes sit on a spectrum. For B2B fleets, even a partial SDV (OTA + twin + remote diagnostics) often beats a cheaper but mute vehicle on five-year TCO.

Which architecture for which buyer?

Triox Mobility's TEV and OpenEV programmes are built as modular, software-defined skateboard platforms — so partners choose body and brand without rebuilding the electrical and structural core for every SKU.