--> About AutoPi | Our History
AutoPi // Our Story

Built by engineers.
Trusted by fleets worldwide.

AutoPi began as a small engineering project in 2016, built by three founders with a shared interest in vehicle electronics and software. A Kickstarter launch validated the direction - and pushed the project from prototype work into a real production roadmap.

Founded 2016 Danish IoT company OBD-II · CAN · CAN-FD Open source core
// company timeline
2016
Founded in Denmark. Kickstarter launch validates the product direction. First hardware prototypes ship.
2018
Platform scaled to support professional fleet and engineering deployments. AutoPi Cloud launched, enabling centralised device management at scale.
2021
TMU CM4 hardware generation released. CAN-FD support introduced alongside J1939 and heavy-duty vehicle profiles.
2024
CAN-FD Pro launched. Customers in 50+ countries. Docker edge compute and multi-tenant cloud management available.
// how it works

See AutoPi in action

A quick overview of how AutoPi connects your vehicles to the cloud and what you can do with the data.

Your right to extend
// customization

You ask, we customize

AutoPi provides telematics solutions that are designed to be adapted rather than locked down. Hardware, firmware, and cloud components are built to support changes in data flow, configuration, and system behavior, which is often required once a project moves beyond a pilot phase.

In many deployments, AutoPi devices act as a gateway layer between the vehicle and an existing customer backend. Data can be forwarded to external systems using defined formats and transport methods, while the AutoPi platform continues to handle device provisioning, configuration, monitoring, and operational tooling.

Engineering efforts are handled by the same teams that design and maintain the core products. This keeps changes aligned with the underlying architecture and avoids one-off solutions that cannot be maintained over time. Projects range from small adjustments in signal handling to larger changes in device behavior or cloud-side workflows.

// open source

Open source as a technical baseline

AutoPi Core is built on Raspberry Pi OS and follows an open-source development model. This choice is rooted in practical engineering considerations rather than ideology. Access to the full software stack makes it possible to inspect behavior at every layer - from system services and drivers to application-level logic.

In vehicle and machinery projects, this level of visibility matters. Real-world deployments often expose issues that are difficult to reproduce in a lab environment, such as timing differences on CAN buses, power interruptions, or interactions with OEM-specific ECUs. Open access allows these issues to be analyzed and addressed without relying on black-box components.

Customers are not tied to closed firmware images or opaque update mechanisms. They can audit changes, maintain forks when necessary, and align device behavior with internal engineering standards or compliance requirements. Community contributions from real deployment scenarios feed back into the platform continuously.

Open source software and development
// mission & vision

Delivering IoT telematics globally

Mission

Enable vehicles with advanced, customizable IoT

We will enable vehicles around the world with advanced technology and customizable solutions with one IoT platform, and consequently strengthen our customers's operations and make them more profitable.

Vision

Push the telematics industry forward

We seek to convey more innovation, efficiency, and abundance of opportunities in the world by pushing the telematics industry into our current century.

// worldwide innovations

Trusted by customers globally

Global reach, real-time insights, and high-performance solutions for your success.

// contact

Still have questions?

Get in touch with us - we're ready to answer any and all questions.

// send a message
We'll get back to you shortly

* Mandatory fields

Contact our engineers ↑