Cloud Login
// fleet data
AutoPi Mini
Verify supported EV/OBD vehicles and parameters for standard fleet data.
Explore MiniDevice Configuration Management
Centralized configuration for in-vehicle devices
Treat every AutoPi unit as a managed node in your infrastructure. Define configuration once in AutoPi Cloud, apply it to projects, tenants, and fleets, and let the platform propagate changes over-the-air while keeping per-device overrides under control.
Network profiles, CAN/CAN-FD decoders, logging policies, GPIO mappings, keyless rules, and custom services are stored as versioned templates with history and audit trail. Changes are diffed, validated, and rolled out in a controlled way, so you always know which config was active on which device at a given time.
Use the web UI or APIs to integrate configuration with your CI/CD and internal tools, avoid config drift between engineering and production, and keep large deployments consistent without SSHing into individual vehicles.
Contact Us
Feature Highlights
Code More, Manage Less:
Smart Device Control
Use AutoPi Cloud as a control plane for your in-vehicle devices. Onboard hardware, assign it to projects and tenants, attach configuration templates, and push changes over-the-air while keeping full visibility into status, health, and active config on every unit.
Streamlined Device Configuration Management
Represent fleets, projects, and customers as structured device groups with shared templates. Apply network, logging, CAN, and application settings centrally and let devices synchronize on their next check-in, instead of managing each unit by hand.
Register devices via serial/ID or pre-provisioning and attach them to tenants, projects, and fleets. Build hierarchies that reflect your business (customer → site → vehicle), so configuration, access rights, and policies inherit in a predictable way.
Locate devices by VIN, tags, customer, software version, online status, last check-in, or configuration profile. Use the result set for bulk operations such as assigning templates, launching OTA jobs, or changing ownership.
See current config, active templates, last applied changes, and device health from one view. Access is governed by role-based permissions, so operators, integrators, and end customers only see and control the devices they are responsible for.
Trigger a configuration sync, reboot, service restart, or diagnostic command directly from the device view. Changes are queued in the cloud and executed by the device on next contact, with logs and status returned for verification.
Use templates and inheritance instead of per-device configuration. Adjust logging, CAN mappings, network settings, or applications once at fleet or tenant level and let AutoPi propagate the changes, reducing config drift as you move from pilots to thousands of deployed units.
Configure Devices Swiftly
Apply network, logging, and application settings in seconds. Devices pull updates automatically, reducing manual setup work and keeping configurations consistent across the fleet.
Explore OBD & CAN Data Easily
Inspect real-time telemetry, fault codes, network health, and CAN traffic directly from the cloud. Validate setups quickly when rolling out new functionality or custom integrations.
Deploy at Scale
Push configuration templates to hundreds or thousands of devices. Gain full rollout visibility, including status, logs, and applied-change history per device.
Simplify Your Setup
Use template inheritance to avoid duplicated configs and minimize drift. Manage complex fleets with predictable, clean configuration structures that scale with your business.
Feature Details
Simplify Your Device Management
Use AutoPi Cloud as the single source of truth for configuration. Model tenants, projects, and fleets, attach versioned templates, and let devices synchronize over-the-air. Track what changed, when it changed, and which devices picked it up, without connecting to individual units.
Template-Driven Configuration
Define network, logging, CAN/CAN-FD mappings, keyless rules, and custom services as reusable templates. Apply them at tenant, project, or fleet level and let inheritance handle the rest. Per-device overrides are supported, but remain visible so they do not drift out of control.
Live Inventory & Health
See which configuration and software version is active on each device, when it last checked in, and whether pending changes are still in queue. Use this view to verify rollouts, debug issues, or identify devices that deviate from the expected baseline.
Signal & Logging Profiles
Attach CAN, OBD-II, and other signal profiles to projects instead of hard-coding them per device. Control sampling rates, triggers, and logging rules centrally so that changes to a profile automatically propagate to all devices that depend on it.
Secure Control Plane
Configuration changes are sent over TLS using device certificates and signed commands. Devices only accept updates from the AutoPi backend they are provisioned against, and all changes are recorded with user, time, and scope for audit purposes.
APIs & Automation Hooks
Manage configuration via REST APIs and webhooks as well as the UI. Integrate device provisioning, template updates, and rollout promotion into your CI/CD pipeline so fleet configuration follows the same process as your software releases.
Linked OTA & Configuration
Coordinate software and configuration changes in one place. Roll out new releases together with updated templates, verify device state, and, if needed, roll back both application and configuration to the last known-good combination.
Core Feature
Flexible Configuration & Management
Keep configuration, access, and operations in one place. Use APIs and templates to integrate with your own tooling, enforce security boundaries, and keep large deployments predictable as they scale.
API-First Management
Interact with devices, templates, and fleets through documented REST endpoints. Provision hardware, assign tenants, and push configuration from your own portals or CI/CD jobs instead of relying on manual dashboards for day-to-day work.
Config as Data
Store configuration as structured data, not ad-hoc scripts. This makes it easier to version, diff, review, and reuse across customers and projects, and to mirror the same structure inside your own systems if needed.
Rollout & Feedback Loops
Combine configuration updates with telemetry and logs to build closed feedback loops: push a change, observe its effect on a subset of devices, then promote, adjust, or roll back based on measured results instead of guesswork.
Role-Based Access & Scopes
Separate duties between integrators, support teams, and end customers. Use roles and scopes to control who can view devices, push configuration, trigger commands, or manage tenants, and log every sensitive action.
Signed Commands & TLS
All device communication goes over TLS, backed by device certificates and signed messages. This prevents unauthorized infrastructure from issuing commands and keeps configuration updates and telemetry protected in transit.
Audit & Change History
Track who changed what and when across devices, templates, and tenants. Change history and event logs make it straightforward to reconstruct the state of a device at a specific point in time for debugging or compliance.
Operational Views for Different Roles
Give operations, engineering, and support teams views that match their tasks: fleet overview for managers, per-device drill-down for engineers, and filtered subsets for customer support or partners.
Bulk Actions & Safe Defaults
Run bulk operations on selected devices while still keeping safeguards in place. Preview the impact of template changes, limit updates to subsets, and use staged rollouts to avoid large-scale misconfiguration.
Clear Inheritance & Overrides
Visualize which settings come from which level (tenant, project, fleet, device) so engineers understand why a device behaves a certain way. Overrides are explicit, making it easy to clean up legacy exceptions as deployments mature.
Something unclear?
Frequently asked questions
Device configuration management means controlling all AutoPi device settings, policies, and
behaviors centrally in AutoPi Cloud, instead of configuring each device manually. It covers
networking, logging, CAN/OBD-II mappings, applications, and more across the entire fleet.
Configuration is organized in logical layers such as tenant, project, fleet, and device.
Templates can be attached at each level, and devices inherit configuration from higher levels,
with clear visibility into what comes from where.
Yes. Device provisioning, template assignment, configuration changes, and rollouts can all be
driven via REST APIs, so you can integrate AutoPi with your own portals, backends, or CI/CD
pipelines.
Yes. Network profiles, logging policies, CAN/CAN-FD signal sets, and other settings are stored
as reusable templates. These can be applied at different hierarchy levels, with inheritance and
overrides handled by the platform.
Per-device overrides are supported but always shown explicitly, so you can see where a device
differs from its template. This avoids hidden drift and makes it easy to clean up exceptions
later.
Yes. AutoPi Cloud shows active templates, overrides, software version, last check-in, and
pending changes per device, so you know exactly which configuration is running in the field.
OTA software updates and configuration changes are coordinated through the same control plane.
You can roll out new releases together with updated templates, and roll back both if needed to a
known-good combination.
Typical centrally managed settings include modem and WiFi parameters, VPN and routing,
logging/telemetry policies, CAN and OBD-II mappings, edge applications, keyless rules, alert
thresholds, and various device services.
Yes. CAN, CAN-FD, J1939, and OBD-II profiles can be defined once and attached to projects or
fleets. Sampling rates, filters, and logging rules can be controlled from AutoPi Cloud instead
of being hard-coded per device.
Yes. You can filter devices (for example by tenant, version, or tag) and apply template changes,
OTA jobs, or commands to the selected set. Rollout status and per-device results are tracked in
the cloud.
Configuration is delivered over TLS using device certificates and signed commands. Devices only
accept changes from the AutoPi backend they are provisioned to, and all operations are logged
with user, time, and scope.
Yes. Role-based access control (RBAC) lets you separate integrator, internal operations, and
customer roles. End customers can be limited to their own tenants, devices, and a subset of
configuration and commands.
Changes are queued in AutoPi Cloud and delivered the next time the device connects. Status
information shows which devices have applied the new configuration and which are still pending.
Yes. Because configuration, templates, and rollouts are API-driven, you can integrate them with
your CI/CD to promote configurations alongside software releases and enforce review and approval
workflows.
Yes. Change history and audit logs make it possible to see which user or API client changed
configuration, when it was done, and which devices were affected, supporting debugging and
compliance.
Device configuration management is a platform capability and works across the AutoPi hardware
range, including AutoPi TMU CM4, AutoPi Mini, and CAN-FD based units, within the constraints of
each hardware variant.
Configuration determines what data is collected, how often, and where it is streamed. By
centralizing logging and signal profiles, you can adjust real-time data behavior for entire
fleets without touching individual vehicles.
Typical workflows include cloning templates and setups between tenants, projects, or test and
production environments, so proven configurations can be reused instead of rebuilt from scratch.
You need AutoPi hardware, access to AutoPi Cloud, and at least one tenant or project. From
there, you can start registering devices, defining templates, and rolling out configuration via
the UI or API.
Developer documentation is available at
docs.autopi.io, including guides for device management,
cloud APIs, and configuration examples that you can adapt to your own projects.
// your proof of concept
Build a PoC for Intuitive Device Configuration Management
Let's find the right hardware for your vehicles, validate the data you need and plan the integration together.
Choose by integration requirements
// vehicle-bus logging
AutoPi CAN-FD Pro
Evaluate J1939, CAN FD and vehicle-bus data logging.
Explore CAN-FD Pro// custom edge software
AutoPi TMU CM4
Develop Docker workloads and custom edge software.
Explore TMU CM4Confirm vehicle power, connectors, adapters and any required external sensors. An accessible connector does not guarantee that every requested signal is available.
Compare device capabilities// project scope
Separate standard capabilities from project work
- Included
- The selected device's documented hardware and standard software capabilities. Confirm supplied accessories and Cloud access terms for your order.
- Configure
- Supported signals, sampling, trip and geofence rules, data delivery and retention for the selected device and platform.
- Custom development
- Proprietary signal decoding, custom applications, external sensor integration and ERP/TMS workflows require an agreed scope.
// from testing to rollout
Explore what's possible on your vehicles
We'll help you choose devices to purchase for representative vehicles, then work with you to extract the data you need, including reverse engineering where needed. Together, we'll agree the scope and acceptance criteria, validate the captured signals and integration, then decide on rollout.
Discuss your PoC
// contact
Still have questions?
Get in touch with us - we're ready to answer any and all questions.