Cloud Login
AutoPi Cloud
Device Management
for automotive data loggers and edge devices
Our device management platform provides centralized control of distributed edge deployments. Provision and configure devices at scale, roll out firmware and software updates in a controlled and secure way, and monitor device health and performance metrics in real time. With role-based access control and configurable workflows, you can standardize operations, reduce manual intervention, and keep your edge fleet current and stable in production.
AutoPi Cloud is included with all our devices.
Device Management & AutoPi Fleet
Optimize Your Operations: Configure, Adjust, Expand for Success
At AutoPi, we recognize that customers operate with different operational models and control requirements. To support this, we provide two primary cloud usage patterns: Device Management and AutoPi Fleet.
Multiple Device Management
Overview of devices
Obtain a consolidated view of all devices from a central location. Dynamic overview widgets present Total Devices, Online Now, Pending Updates, and Errors in the last 24 hours, with each widget linking directly to its corresponding filtered list for focused analysis and troubleshooting. Communication metrics display average and total reporting intervals for today and month-to-date at both fleet-wide and per-device levels, enabling you to identify connectivity gaps, detect outliers, and plan proactive maintenance before issues affect operations.
Templating
Create a centralized library of configuration blueprints on the Templates page to define and standardize device setup at scale. Each template encapsulates full device configuration, including firmware versions, network parameters, security credentials, and diagnostic profiles, so manual per-unit configuration is minimized and behavior remains consistent across the fleet.
Use advanced configuration sections to include custom Modules (Custom Code), override or extend default Services, define Triggers and Jobs for automated workflows, and configure both CAN-bus and PID Loggers for precise data acquisition. Built-in version control tracks all changes, provides side-by-side comparison of revisions, and allows safe rollback to known-good configurations when required.
Operational workflows are streamlined by creating a new template with a descriptive name, parameterizing settings, modules, and triggers according to requirements, and then assigning devices in bulk via the Devices tab. With a single “Apply” action, all associated devices receive the updated configuration, or you can stage deployments per device for phased rollouts. By controlling configuration drift and reducing ad-hoc changes, Templates help maintain uptime, simplify troubleshooting, and accelerate onboarding of additional devices.
Multi-tenant setup
Use hierarchical multi-tenant device management on the Nested Customers page to create isolated sub-accounts for different clients, projects, or business units. Each nested customer functions as an autonomous environment with its own device set and users, while global administrators retain full visibility and control from the parent account.
The permissions model enforces strict isolation: nested users can only access the devices assigned to their account, preventing cross-tenant visibility, while parent-level administrators maintain oversight across all nested customers. This structure is suited for managed service providers, OEM partners, and enterprises running segmented fleets where separation, governance, and clear boundaries are required.
Configuration is straightforward: on the Account page, select “Customers” to create a nested customer, then assign devices and add an admin user. Each tenant receives a dedicated dashboard and role set within minutes, making it possible to delegate day-to-day management while central operations remain under control.
User permissions
Centralize user and account administration on the Accounts page. Create Customers and Nested Customers to reflect your organizational structure, then add users under each account via the Users section. Configure global settings such as time zone, units, and formats at account level to keep data representation uniform across teams.
Apply fine-grained access control by assigning users to permission groups in the Permissions subsection. Choose Account Administrator for full user and account control, Full Device Access or Device Management for technical users, Nested Customer Administrator for sub-account owners, or Fleet Management for operational teams. Each group is built around specific task profiles to avoid over-privileging users.
Refine scope further by assigning Locations to users, limiting dashboards and lists to relevant sites or regions. Review and adjust permissions in the live user list, inspect last login and activity status, and manage device registrations under Manage Devices. With granular roles, location scoping, and traceable changes, you can keep access aligned with responsibilities while still enabling teams to work independently.
Deploy Docker
Deploy and manage Docker containers on devices at scale with the Docker setup guide. Define containerized services once and distribute them consistently, without local builds or manual updates. Configure your AutoPi Cloud release with versioned images, startup parameters, environment variables, and purge policies, then apply to selected devices in one operation for predictable deployments.
Pull securely from private registries by creating a Docker Registry entry with URL and credentials, allowing devices to authenticate and fetch images automatically. Group related services under Projects, then publish multi-container Releases that define image tags, labels, network modes, volumes, and restart policies. Versioned releases track hashes, deployment counts, and rollout status to support auditability and safe rollback.
Maintain operational control with remote modules: invoke commands via the execute endpoint, inspect execution results, and stream Container Logs directly into your dashboard. Releases are applied automatically when devices are idle or triggered on demand, so you can keep workloads current, diagnose container behavior, and roll out new features without physical access to the vehicle.
CAN Bus library
Use the Car Explorer OBD-II Library as a comprehensive catalog of standardized PIDs and vehicle data streams for diagnostics and telemetry. Access a wide range of supported parameters such as engine RPM, vehicle speed, temperatures, and fuel level, organized by manufacturer, protocol, and data type for efficient lookup. Documentation includes scaling, units, and response characteristics, so integration into applications is deterministic and reproducible.
Apply advanced search and filters to locate PIDs by keyword, ID, or OBD mode, then generate custom data dashboards quickly. Real-time previews allow you to verify parameter output and scaling behaviour in the browser before deployment, while code examples in Python, JavaScript, and Shell simplify integration into AutoPi scripts and external services. Data collection can be automated using prebuilt templates or tailored queries with support for ISO 15765 and CAN-FD.
Extend coverage via the Community PID Library, where custom definitions from AutoPi users are shared and versioned. Discover proprietary manufacturer PIDs, experimental measurements, or EV-specific signals and import them with a single action. Community ratings, comments, and usage statistics help you select reliable definitions, while automatic update notifications keep local collections synchronized with new contributions.
Device Management & AutoPi Fleet
Optimize Your Operations: Configure, Adjust, Expand for Success
At AutoPi, we recognize that every customer has distinct operational and data requirements. For this reason, we provide two complementary cloud usage options: Device Management and AutoPi Fleet.
Manage a specific device
Device overview
On the Device Overview page for a specific unit, you obtain a structured summary of its identity and context: device name, timestamp of last communication, associated vehicle or environment, installed firmware version, and detailed vehicle metadata (CAN bus, make, model, year, engine) are presented in the header with direct access to Settings for updates.
Below the header, real-time status indicators and communication metrics capture Online, Offline, Updating, and Error states, along with reporting intervals for the current day and month-to-date. The Events log shows recent alerts and system messages, and resource and connectivity information allows you to spot deviations early and address them before they escalate.
From the same page you can execute remote commands, schedule Services, launch Jobs, dispatch Software Updates, adjust Triggers, and refine Advanced Settings, all with one click. This consolidated control surface simplifies diagnostics, configuration management, and operational follow-up for each device.
Device dashboard
On the Device Dashboard page, you access a combined view of key metrics for one unit. The header lists device identity, firmware version, and last check-in, while live widgets show connectivity state, GPS position, signal strength, and battery level. An interactive map plots the current location with geofence overlays, and quick actions provide direct access to events, services, and updates.
Predefined widgets expose current and historical indicators such as Online Status, Communication Interval, engine data (RPM, temperature, fuel), and Trip summaries, with configurable thresholds and color encoding. Use the widget library in the sidebar to enable or disable panels, change their order, filter data by time range or parameter, and switch between maps, charts, and tabular views to match your monitoring tasks.
For custom monitoring, follow the Add a New Widget from Scratch flow: specify a widget name and data source (CAN PID, GPS, custom returner), select a visualization (gauge, line chart, list), configure filters or thresholds, and preview live data before saving. Newly created widgets appear alongside the default ones, allowing you to focus on the signals most relevant to your use case.
Data logging configuration
Use AutoPi’s logger framework to capture all essential metrics from OBD-II PIDs and raw CAN signals. Define loggers that run continuously or conditionally so events, diagnostics, and custom signals are recorded reliably, including proprietary messages and high-frequency bus data.
Create OBD-II PID loggers using the PID Logger setup guide. Choose from standardized parameters such as RPM, vehicle speed, coolant temperature, or fuel level, and configure sampling intervals, start/stop conditions, and retention rules. Real-time previews and automatic unit scaling help ensure the collected data is correctly interpreted before deployment.
For deeper integration, configure CAN signal loggers via the CAN Signal Logger manual. Decode fields from raw frames, map signals to typed outputs, apply custom parsers, and capture high-speed CAN-FD traffic with accurate timestamping. This makes it possible to monitor proprietary ECU channels or third-party devices in a consistent and structured way.
All logger types support adjustable sample rates, conditional triggers, and storage quotas. Inspect live data streams in the Cloud UI before rollout, schedule periodic uploads or continuous streaming to external storage, and use dedicated logging dashboards to track health, buffer usage, and data volumes for individual devices and for the fleet as a whole.
Integrate loggers with Templates and Dashboards for complete visibility. Attach post-processing via custom triggers or jobs that analyze captured data, generate CSV or JSON outputs, or feed third-party analytics platforms. With this setup, raw vehicle data is converted into structured information that supports predictive maintenance, compliance, and telematics reporting.
Custom jobs
Automate recurring maintenance and operational workflows with Cloud Jobs, scheduled or on-demand tasks running on devices. On the Cloud Jobs page, you define jobs to execute shell commands, invoke scripts, collect metrics, or trigger auxiliary processes without manual interaction.
Create jobs by specifying a name, target devices or groups, execution statement or script, and schedule parameters. Choose ad-hoc execution, recurring intervals (cron patterns), or activation based on events or status changes. Configure retries, timeouts, and notification preferences to maintain reliable execution across different network and power conditions.
Monitor execution with detailed job logs and status indicators in the Jobs dashboard. Each record shows next run, last result, exit code, and captured output, and can be filtered by device, status, or date. Alerts and integration hooks notify relevant teams of failures, allowing quick investigation and correction.
Integrate Jobs with Templates and Triggers for complete automation flows. Embed job definitions into configuration templates so new devices are provisioned with required tasks from day one, or bind jobs to custom triggers such as CAN thresholds or fault events to start corrective actions automatically. Cloud Jobs enable large-scale automation while keeping processes observable and controlled.
Triggers on events
Use AutoPi’s event-driven Cloud Triggers to automate reactions when defined conditions occur. Whether monitoring engine faults, CAN anomalies, geofence events, or custom returner outputs, Triggers translate raw signals into deterministic workflows that do not rely on manual supervision.
Configure each trigger by selecting a data source, such as an OBD-II PID, CAN signal, GPS coordinate, vehicle state, or external returner, and define conditions (equality, ranges, thresholds) with appropriate limits. Add time constraints or cron rules to restrict activation to defined windows like business hours or scheduled maintenance periods, helping control noise and false positives.
Choose from built-in actions such as starting a Cloud Job for diagnostics, sending email, SMS, or webhook notifications, enabling or disabling Services on-device, or executing custom Python logic. Retry strategies, backoff rules, and escalation options allow you to tune behavior for reliability and operational relevance.
Operate all triggers from the central Triggers dashboard: inspect status, next-fire time, and historical executions with result codes and payload logs. Filter by device or trigger type, clone definitions, apply in bulk to device groups, and maintain templates for repeatable deployment.
Combine Triggers with Dashboards and Templates to build closed-loop automation pipelines: visualize trigger metrics alongside device data, embed them in configuration blueprints for consistent provisioning, and chain multiple triggers to form multi-step recovery or notification procedures. This shifts device management from reactive monitoring to proactive, rule-based control.
Events
Use the Events page as a unified log of device and vehicle activity, where relevant events are persisted and timestamped. This provides an auditable timeline for each unit, supporting investigations, compliance, and operational reviews without needing multiple tools.
Monitor infrastructure-related information via the Cloud Events System feed, which records device registrations, firmware rollouts, connection changes, and service state transitions with severity indicators and optional automation hooks.
Inspect in-vehicle activity via the Cloud Events Vehicle log, capturing ignition transitions, trip start and stop, geofence entries and exits, CAN fault events, and custom returner outputs. Each event includes metadata such as GPS position, signal strength, diagnostic codes, and payloads, enabling precise reconstruction of sequences and conditions.
Filter, sort, and export events for further processing or integration. Search by device, event type, severity, or time window, and export CSV or JSON for offline use or ingestion by external dashboards. Subscribe to webhooks or email notifications for proactive monitoring, and embed event components into Dashboards to keep critical signals visible to operations teams.
Device alerts
Use the Device Alerts page to track issues such as system warnings, power loss, USB disconnects, and custom trigger events. Alerts are mapped directly to underlying event streams, so each item is traceable to its source and context, allowing you to analyze cause and effect across your device fleet.
Single Device Management
Advanced settings
Use the Advanced Settings page to control detailed device behavior, from core system parameters to peripheral integrations, so each AutoPi unit can be tuned to match its deployment scenario.
Adjust motion monitoring parameters with the Accelerometer configuration for impact detection and g-force thresholds, and configure audio capture via the Audio module by defining sampling, triggering, and storage policies.
Control device pairing, proximity features, and discovery with Bluetooth settings, and implement access and identification workflows with the RFID module, which is suitable for user or asset association.
Capture charging metrics and session details using Charging Session settings, and observe battery usage and power draw via the Power section with thresholds, warnings, and retention options.
Scale data flows with the Cloud Storage integration, or configure containerized workloads using Docker settings where image versions, startup parameters, and update policies are defined in a consistent manner.
Configure secure telemetry and command channels via the MQTT section, adjust network behavior in the Wi-Fi module, and extend diagnostics with advanced OBD parameters, including custom PIDs, sampling intervals, and quotas for vehicle data.
Maintain overall system health using System diagnostics, configure geolocation behavior in the Tracking module, manage trip metrics via Trip settings, and control firmware rollout policies under Update Release. Validation and revision tracking across all sections help you test, deploy, and roll back configurations in a controlled way.
Services
Configure onboard automation and extended logic on the Services page, where you manage built-in and custom Python services running locally on AutoPi devices. Each service definition contains trigger conditions, resource priorities, and logging options so that workflows can run consistently and with predictable resource usage.
Build tailored functionality with Custom Services and Custom Workers. Custom Services execute on demand or when triggered to implement logic, perform data transformations, or call third-party APIs, while Workers run continuously as background processes monitoring CAN data, maintaining state, or handling long-running tasks. Integrated editors, versioning, and dependency management simplify development and rollouts.
Tie services into Triggers, Cloud Jobs, and Templates to assemble complete automation. Assign services to individual devices or groups, configure retries and alerting, and use Cloud Config Alerts for escalation, providing a programmable edge environment that remains observable and manageable.
Custom services
Extend the AutoPi edge stack with Custom Services, Python components that execute locally and implement project-specific logic. They can run on demand or be triggered by other components to process telemetry, interact with external APIs, or enforce device policies, all packaged with dependency manifests and version control.
Use Custom Returners to send processed data into your own infrastructure. Configure endpoints, authentication, and payload formats so that outputs from services—such as aggregated metrics or diagnostic flags—are delivered to REST, MQTT, or storage systems in a repeatable way.
Automate condition-based executions with Custom Triggers. Combine events, PIDs, CAN signals, or returner results into compound conditions so that the appropriate service is run at the correct time, for example when anomalies are detected or thresholds are crossed.
Run persistent workloads using Custom Workers. These background processes handle continuous monitoring or high-frequency data processing, with health checks and restart strategies built in to keep them running reliably.
Combine services, returners, triggers, and workers as part of your configuration strategy via Templates or Cloud Jobs. Provision new devices with pre-defined modules, or orchestrate multi-step pipelines where processed data from one component feeds another stage.
Monitor all custom modules from the Services page, where you assign them to devices or groups, adjust priorities, review logs, and define alerting behavior. This provides a controlled environment for custom edge computing, even when deployed across large fleets.
Custom code
Develop and deploy Python scripts directly from the Cloud using the Custom Code editor, enabling project-specific logic without additional tooling. The editor supports syntax highlighting and inline documentation so data parsers, API connectors, and diagnostic helpers can be implemented efficiently.
Define dependencies in a `requirements.txt` file. The AutoPi build process packages code and libraries into versioned bundles that are deployed to devices automatically, ensuring that all instances run with identical environments.
Test and troubleshoot custom code using live log streams and error traces exposed in the Cloud UI. Standard output, exceptions, and returner payloads are visible, allowing you to verify behavior against real data before expanding deployment to more devices.
Integrate your scripts with Services, Workers, Triggers, or Jobs to compose full automation chains. Versioning in the Cloud UI allows you to compare releases, revert to earlier versions, and track changes over time, supporting safe iteration at scale.
Software updates
Administer over-the-air firmware deployment on the Software Updates page, where you define update campaigns, manage version channels, and select target devices or customer groups. This removes the need for manual flashing and helps maintain consistent software baselines.
When creating an update, select the firmware image, document release details, and choose target sets. Configure whether rollouts are immediate, scheduled, or staged across batches, and define retry and maintenance window policies to align with operational constraints.
Track each campaign’s progress with live status indicators. View completion rates, success and failure counts, and per-device logs. For any device, inspect historical update records to diagnose failures or network conditions, and fall back to previous versions where needed to protect stability.
Incorporate updates into Templates or Triggers to automate patching strategies. Use version-based triggers to ensure critical patches are deployed quickly, or only update devices that meet specific criteria, keeping security posture and firmware consistency high.
Detailed update runs
Observe each execution of a release in the Update Release Runs section, where every run corresponds to a specific rollout of a software version. You can see timestamps, targeted device counts, and aggregated status values, which gives a concise view of rollout performance.
Inspect a run to see per-device outcomes including success or failure, firmware version transitions, retry attempts, and log excerpts. Filters enable you to focus on failed cases, specific device groups, or time ranges, which speeds up problem isolation.
Use run history to refine rollout patterns: compare different batches, validate rollback behavior, and correlate success rates with maintenance windows or network load. Export run information as CSV for reporting or use webhook integration to bring status into external monitoring or BI systems.
Change history
Use the Change History tab to review configuration modifications affecting Advanced Settings, Templates, Services, and other components. Each entry records the timestamp, user, area changed, and a summary of the previous and current values so that configuration changes are transparent and auditable.
Open diff views to compare revisions side-by-side and identify precise changes to JSON, parameters, or policies. Whether the update concerns MQTT settings, PID sampling, or Docker release configuration, the exact deltas are visible and can be reverted when necessary.
Filter and export change logs for audit and reporting purposes. Search by user, period, change type, or module, then export as CSV or JSON for downstream processing. Integration with BI or ticketing systems makes it straightforward to align configuration history with incident and release management.
Capture IoT Data & CAN Data
Maximizing Data Insights and Optimization through Customization and Integration
Maximize the value of telemetry by tailoring data collection using workflows, post-processing, filters, asset and sensor integration, PIDs/CAN messages, and loggers. This enables you to optimize performance, improve observability, and align data structures with existing analytics and reporting systems.
Harness the Full Potential of your IoT Devices
Configuring post-processing, filters, and custom formatting is essential for producing structured telemetry from your IoT devices. Using AutoPi Cloud, you can select these options in a controlled way so that stored and visualized data follows the conventions your teams rely on.
Customize workflows to execute defined actions when specific patterns or thresholds are observed in the data received from your IoT devices. This supports automation of repetitive tasks and helps standardize fleet and asset management procedures.
Aggregate data from multiple sources by integrating third-party devices and sensors into the existing IoT infrastructure. By correlating these combined datasets, you obtain a more complete understanding of asset behavior and fleet performance.
Something unclear?
Frequently asked questions
AutoPi Cloud is designed for a wide range of users, including car owners looking to enhance their driving experience, fleet managers aiming to improve fleet management effiiciency, and developers interested in IoT Integrations.
Whether you're a tech-savvy individual or managing a large fleet, AutoPi Cloud offers the tools you need.
Explore our Fleet Management System solution to see how AutoPi Cloud can benefits your specific use case.
AutoPi Cloud offers an array of key features, such as real-time vehicle tracking, remote diagnostics, customizable alerts, data logging, and seamless integration with various IoT devices and platform.
These features help you monitor you vehicle's performance and keep it running smoothly.
AutoPi Cloud stands out with its user-friendly interface, extensive customization options, robust data measure, and seamless integration capabilities. Unlike other products, AutoPi Cloud provides a comprehensive solution that is both powerful and easy to use.
Read more about our unique offerings in our AutoPi Cloud Blog.
Customers often ask about compability with their specific vehicle, the installation and setup, how their data is protected, and the variety of features available.
We strive to address these concerns by providing detailed information and exceptional customer support.
Visit our FAQ page and Documentation page for more questions and troubleshooting tips.
Using AutoPi Cloud offers numerous benefits, such as enhanced vehicle safety through real-time diagnostics, improved fleet management efficiency, and customizable alerts that help you stay ahead of potential issues.
One of the standout features is our device configuration management capability, which allows customers to monitor, update, and control all their connected devices from a single platform.
Additionally, we offer extensive customization options to match your business' specific requirements, ensuring that you get the most out of our platform. Our commitment to providing exceptional support and building long-term relationships means you can rely on us to assist you every step of the way.
AutoPi Cloud improves the user experience by providing detailed insights into vehicle performance, timely alerts to prevent issues, and an intuitive platform for managing vehicle data. It helps users stay informed and in control of their vehicles, reducing stress and improving efficiency.
AutoPi Cloud is compatible with most vehicles that have an OBD-II port. It supports various operating systems and can be accessed through both web and mobile applications, making it versatile and accessible.
Check out our Documentation for detailed compatibility information.
Installation is straightforward: simply plug the AutoPi device into your vehicle's OBD-II port, create an account on the AutoPi Cloud platform, and follow the setup instructions provided. The process is designed to be quick and easy, even for those who are not tech experts.
For a step-by-step guide, visit our getting started guide.
AutoPi Cloud automatically updates to ensure you always have the latest features and security enhancements. We also provide regular maintenance tips and updates through the platform, so you’re always informed about the best practices.
Stay updated with our latest news on our Blog.
AutoPi Cloud offers flexible pricing plans to suit different needs. You can choose between a one-time purchase for a lifetime subscription or opt for a monthly subscription plan. Each plan provides access to various features, allowing you to select the best option for your requirements.
AutoPi Cloud employs advanced encryption methods and secure data storage practices to protect user data. Our privacy policy ensures that user information is handled with the utmost care, giving you peace of mind.
STILL HAVE QUESTIONS?
Get in touch with us – We're ready to answer any and all questions.