Cloud Login
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.
45,000+ devices
850+ clients
For security reasons, we do not publish customer identities or named customer logos.
Founded 2016
Danish IoT company
OBD-II · CAN · CAN-FD
Open-source Core: CM4 / Pro
See AutoPi in action
A quick overview of how AutoPi connects your vehicles to the cloud and what you can do with the data.
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 as a technical baseline
TMU CM4 and CAN-FD Pro run AutoPi Core, built on Raspberry Pi OS and developed as open-source software. Engineers can inspect the Core source and assess changes for their integration. AutoPi Mini uses different firmware; it does not provide the same Core source access or customization capabilities.
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.
Teams using Core on CM4 or Pro can review changes and maintain forks where needed. Agree responsibility for custom code, updates and ongoing maintenance as part of your deployment scope.
Delivering IoT telematics globally
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.
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.
// deployment roadmap
From proof of concept to deployment
Start with purchased proof-of-concept devices, then work with AutoPi engineers on vehicle data extraction, including reverse engineering where needed.
-
Purchase PoC hardware
Buy devices for testing on representative vehicles. Choose hardware appropriate to the vehicle interfaces and project requirements.
-
Agree signals and data destination
Define the signals, sampling needs, destination system and acceptance criteria with our engineers.
-
Validate data extraction
AutoPi engineers help test extraction and delivery, including reverse engineering where needed within the agreed scope. Record validated signals and remaining gaps.
-
Plan the rollout
Use the validation results to decide whether and how to expand, with installation, integration and support responsibilities agreed.
// deployment review
Your procurement checklist
Bring these requirements to the discussion. Confirm the agreed arrangements and terms in your proposal before committing to rollout.
- Hosting, data destination and retention
- Where data should go, hosting requirements, retention periods and deletion needs.
- Access
- Who needs device, platform and API access, and who manages permissions.
- Connectivity and region
- Deployment countries, network coverage, SIM and roaming requirements.
- Rollout, support and lifecycle
- Installation, provisioning, integration, updates, maintenance and escalation ownership; support responsibilities, lifecycle and warranty terms to be confirmed in the proposal.
// software foundation
Know your device software
TMU CM4 & CAN-FD Pro
Run open-source AutoPi Core.
AutoPi Mini
Uses different firmware; the same Core source access and customization capabilities do not apply to Mini.
Signal availability varies by vehicle. We agree engineering scope, costs, timing and acceptance criteria with you before starting the work, then use the PoC results to plan a supported rollout.
Discuss your proof of concept