--> Get in Touch with AutoPi Experts for Help and Support
AutoPi // Support

We're here to help.
Get back on the road faster.

Troubleshooting, technical guidance, and direct access to our experts. Whether you're setting up a new device or resolving an issue - our support resources are designed to help you quickly.

Response
Within 24h on business days
Docs
Guides, APIs & tutorials
Community
Forums & shared solutions
Expert team
Direct access to engineers
// contact

Need personalized assistance?

Submit a support ticket and our team will get back to you within 24 hours on business days.

// support@autopi.io

AutoPi Support

For technical questions, device issues, or platform help - reach us directly by email.

Email support@autopi.io
For a new deployment, discuss engineering scope and support responsibilities below.
// documentation

Explore our documentation

Comprehensive guides for device setup, fleet management, cloud integrations, and API access.

// hardware

AutoPi CAN-FD Pro

Step-by-step guide to set up and configure your AutoPi CAN-FD Pro device.

Getting started →
// hardware

AutoPi Mini

Step-by-step guide to set up and get started with the AutoPi Mini.

Getting started →
// hardware

AutoPi TMU CM4

Step-by-step guide to set up and configure the AutoPi TMU CM4.

Getting started →
// heavy duty

Heavy Duty Vehicles

Getting started with J1939 support for heavy machinery using AutoPi devices.

Getting started →
// developer

AutoPi API

A quick introduction to our APIs and how to get access and start building.

Getting started →
// platform

AutoPi Cloud

Step-by-step guide to get started with the AutoPi Cloud platform.

Getting started →

// 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.

  1. Purchase PoC hardware

    Buy devices for testing on representative vehicles. Choose hardware appropriate to the vehicle interfaces and project requirements.

  2. Agree signals and data destination

    Define the signals, sampling needs, destination system and acceptance criteria with our engineers.

  3. 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.

  4. 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
Contact our engineers ↑