Technology · Integration

What an AREN integration looks like.

OEMs do not adopt models they cannot evaluate. This page describes what integration looks like today, while the on-ramp is still direct.

Runtime shape

AREN runs as a containerized inference runtime on the target SoC’s NPU or GPU partition. It is not a monolithic binary. Sensor and CAN inputs arrive through a thin adapter against the vehicle’s sensor abstraction layer. Outputs are consumed by the safety-certified arbitration layer, not by actuation directly.

Debug and trace

Every inference produces a traceable record suitable for safety review: input tensors, intermediate activations at agreed tap points, and output decisions with uncertainty estimates. Trace volume and retention are configurable per program.

Reference integrations

AREN is being validated against reference configurations for the target SoC families listed on the model card. Specific program partners are not named publicly at this time.

Evaluation model

Inbound-only for now. Serious evaluation inquiries should use the contact form with inquiry type “Partnership.” We do not publish SDK downloads, evaluation licenses, or trial signups.