One control layer.Any vehicle.
SOMA OS is Android for EVs: one open control layer that runs on any vehicle hardware. Closed stacks power a few brands. SOMA OS powers everyone else.
SOMA OS is the hardware-agnostic Vehicle Control Unit layer. Write your vehicle software once and run it on any silicon, so every program stops paying the integration tax.
- Hardware
- Agnostic
- Any VCU, any silicon vendor
- Integration
- Once
- Not per program, per chip
- Stack
- Portable
- Software outlives the hardware
Every vehicle program pays the integration tax.
Built for the commercial EV manufacturers who can't afford to build vehicle software from scratch, and who are too small for the incumbent vendors to serve.
Every supplier change costs millions in rewrites and months of lost program time. It hits constantly, and it has ended companies that couldn't absorb it.
Rebuilt every program
Each vehicle program re-implements the same low-level bridge between control software and whatever silicon was sourced. The work is thrown away when the hardware changes.
Locked to the vendor
Software written against one VCU is captive to it. Switching silicon means re-validating the stack from the bottom up, so teams stay on hardware they have outgrown.
Paid in time
Integration sits on the critical path. Months of bring-up and re-validation land before a single feature ships, on every program, indefinitely.
A control layer that decouples software from silicon.
SOMA OS is the operating system layer for electric vehicles: write your vehicle software once, run it on any hardware. The integration is solved in the layer, not rebuilt in every program.
SOMA OS sits between your control software and the vehicle's hardware. Above it, one stable API. Below it, an abstraction that adapts to any VCU. The integration is solved once, in the layer, instead of rebuilt in every program.
Solved in the layer, once.
Four properties make the software portable. Each is owned by SOMA OS, not by the program that ships on top of it.
- API
One control API
Application teams write against a single, stable interface for torque, motion, energy, and safety. It does not change when the silicon does.
- HAL
Hardware abstraction
A thin adaptation layer maps that API onto each Vehicle Control Unit. Supporting new silicon is a port, not a rewrite of the stack above.
- RT
Deterministic runtime
Real-time scheduling and resource guarantees live in the layer, so timing behavior stays consistent across chips with different cores and peripherals.
- VAL
Portable validation
Validate the control stack once against the layer. Re-targeting hardware re-validates the port, not the entire program from the bottom up.
The open layer for EV powertrains. Hardware-agnostic. Licensed by everyone. Closed stacks own a few brands. SOMA OS powers the rest.
Investing, building, or evaluating SOMA OS?
We share technical detail and program specifics directly. Reach out and we'll follow up with what's relevant to you.