OEMs don't want to build telematics — they want telematics that ships with the vehicle and looks like theirs. iMatrix licenses FC-501, the NEO-1 / Sentry-1 sensor catalog, and the iMatrix Cloud APIs so you can ship a connected vehicle in weeks, not years, under your label.
FC-501 is IP67, J1455-compliant, dual CAN, multi-GNSS. Ships in your packaging, mounts to your vehicle's existing wiring harness.
Define the signals you want in the Telematics Workbench; iMatrix CAN Management auto-generates the firmware. No custom embedded engineering required to expose proprietary CAN signals.
iMatrix Cloud as the operator console, or pipe everything to your own backend over REST, MQTT, and webhooks. Build the integration that fits your stack.
FC-501 is the embedded gateway. NEO-1 and Sentry-1 are accessory sensors your OEM can ship as-is or rebrand. They share the BLE radio and the cellular link — no extra carrier negotiation per accessory.
The gateway you embed in your vehicle line. IP67, dual CAN, multi-GNSS, optional Starlink. EdgeUplink eSIM ships pre-installed for global activation. Optional internal battery for ignition-off reporting.
Wireless temp/humidity sensor your OEM can include in cargo or specialty packages. Pairs to FC-501 over BLE. Three-year battery, OTA-updatable, ready to rebrand.
Magnetic sensor for cargo doors, panels, or operator cabinets. Drop-in for vocational and emergency vehicle programs. Same BLE radio, same uplink, no extra integration.
You provide your vehicle's CAN DBC; iMatrix CAN Management auto-generates the embedded code for FC-501. Wayne AI flags conflicts and proposes signal naming.
Logo, color palette, custom domain on iMatrix Cloud. Or ship the data into your own platform via REST / MQTT / webhook with the iMatrix API.
Ten to fifty vehicles on the line with FC-501 plus optional NEO-1 / Sentry-1. iMatrix engineering supports the integration; you own the DBC and the cloud config.
Volume FC-501 shipments under your part number. Service and OTA-firmware governance via iMatrix Cloud. Connectivity included via EdgeUplink.
Fire, ambulance, police, utility — vocational vehicles where telematics is part of the build, not a fleet retrofit.
Class 4–7 chassis-makers who want their own connected-vehicle program without building one.
Construction, agriculture, mining OEMs. Proprietary CANopen networks decoded at the edge under your brand.