Cloud Login
// vehicle-bus logging
AutoPi CAN-FD Pro
Start here for J1939, CAN FD and vehicle-bus data logging. Confirm the vehicle network, connector and signal definitions.
Explore CAN-FD ProCar Leasing
Telemetry, access control, and lifecycle management for leasing fleets
AutoPi collects OBD-II/UDS signals, GPS, and accelerometer data from each vehicle. Devices buffer offline and sync on reconnection using signed, encrypted transport. You define loggers, thresholds, and actions; the platform records events, triggers alerts, and exports structured data for analytics and maintenance.
Typical configuration includes PID sampling at 1–10s, burst capture on faults, trip segmentation from ignition or EV state, geofence policies for depots, and keyless entry control via BLE or relay. Templates apply per OEM and model year; all updates are versioned with author, timestamp, and diff for auditability.
Fleet rules can automate responses to overspeed, idle time, or DTC repetition. Triggers execute defined actions, such as opening a service ticket or disabling keyless access, then forward alerts through REST, MQTT, or webhook endpoints. OTA updates and configurations are managed centrally with rollback and verification support.
Integration options include scheduled exports (CSV, JSON, PDF) and role-based APIs for fleet operators, service partners, and customers. This provides continuous insight into vehicle health, utilization, and driver behavior, reducing downtime and ensuring each lease cycle runs efficiently.
Contact us
Real-time Vehicle Monitoring
Track position, speed, ignition state and battery health in real time. Configure sampling and smoothing windows per vehicle class and apply edge filters to reduce bandwidth without losing fault detail.
Generate trip objects with distance, duration, idle time and stop counts. Attach evidence to events (timestamp, VIN, PID values, geohash) for support and chargeback workflows.
Predictive Maintenance
Monitor DTCs, coolant temp, oil life, 12V levels and charge cycles. Define repeat-window logic to filter transient faults. Trigger service jobs or webhook tickets on threshold breaches.
After service, validate with post-fix windows comparing metrics to baseline ranges. Close the case automatically when stability criteria are met.
Usage Optimization
Compute utilization from trip density, dwell at hubs, and booking calendars. Flag low-usage vehicles and suggest rebalancing via geofence analytics and lane KPIs.
Export utilization and overage metrics on a schedule for billing and pricing models. Results are partitioned by customer, location or vehicle group for BI ingestion.
Flexible Short-Term Leasing
Control access with keyless unlock/lock and immobilization policies tied to booking state, geofence and time window. All access events are logged with user ID, method and vehicle state for audit.
Configure grace periods, retry policies and fallback PINs for low-signal environments. Commands return result codes and logs for troubleshooting.
Vehicle Tracking
Operational tracking with rules and exports
Devices read OBD-II/UDS and GPS at configurable intervals. Edge aggregation compresses low-variance signals while preserving full-rate streams for thresholds and faults. Store-and-forward prevents data loss; buffered records sync on reconnection with ordering and deduplication.
Triggers include repeated DTCs, long idle, overspeed by road class, geofence breach and out-of-hours use. Each trigger can execute a job (diagnostic capture, lock/unlock, horn/light pulse) and notify via email, webhook or MQTT.
Configuration is template-driven per OEM/model year. OTA supports staged rollout and rollback. All changes are recorded with author, timestamp and diff for compliance.
Vehicle Management
Access control, servicing, and lifecycle states
Manage states such as In Service, Booked, Maintenance and Retired. State changes can enforce access policies, start jobs (health check, log snapshot) and route notifications to defined channels.
Keyless entry integrates with bookings: authorize a user, time window and geofence; device validates locally and executes lock/unlock with result logging. Fallback codes and retry windows cover poor connectivity cases.
Roles and nested accounts control visibility. Data access follows tenant boundaries. All remote commands, firmware pushes and configuration edits are logged with device ID, user and result code.
Something unclear?
Frequently asked questions
Answers about car leasing telematics, keyless access, utilization tracking, billing exports, data security, and integrations.
Both short-term and long-term rental models, including subscription and car-sharing fleets. Each vehicle is managed as a connected asset with telemetry, access control, and maintenance policies. Data from OBD-II, GPS, and sensors is normalized for billing, analytics, and compliance across all vehicle types.
Continuous data from the vehicle network enables predictive maintenance, usage-based pricing, and dynamic alerts. Real-time monitoring helps detect misuse, unauthorized driving, or mechanical anomalies instantly. Managers can visualize active leases, mileage accumulation, and trip states in one dashboard, improving utilization and reducing downtime.
Keyless entry uses digital credentials distributed via API or mobile app. Tokens are scoped to a driver, vehicle, time window, and optionally geofence. The in-vehicle unit validates access locally without cloud dependency. All unlock/lock attempts are logged with timestamps, device ID, and user ID for audit and fraud prevention.
Automated reports summarize trip duration, mileage, idle time, and dwell at hubs. Data can be exported daily or monthly for accounting or chargeback. Each record includes vehicle ID, user ID, timestamps, and geofence context. Reports are available as CSV, JSON, or PDF and can be sent to CRM or ERP systems via webhook.
AutoPi integrates with third-party systems through REST APIs, MQTT topics, or webhooks. Data flows bidirectionally, the platform can push live status, receive booking events, and execute remote actions like preconditioning or immobilization. Authentication and rate limits are enforced per tenant for isolation.
Geofences define virtual zones for depots, delivery points, and restricted areas. Entry and exit events can trigger automated billing, security notifications, or service scheduling. Combining geofencing with GPS and accelerometer data enables tracking of unauthorized movement or excessive idle time within a specific region.
Drivers can be identified through mobile app sessions, RFID/NFC tags, or BLE proximity tokens. Each session is associated with a lease event and vehicle. The system logs vehicle access, trip duration, and behavior metrics such as harsh acceleration or braking. This enables accurate usage attribution and personalized billing.
All communication is encrypted using TLS with device-level certificates. Each command is signed and verified to prevent tampering. Role-based access defines who can issue remote actions. Logs track every request, response, and user identity to ensure full traceability and compliance with GDPR and fleet security policies.
Predictive maintenance uses diagnostic trouble codes (DTCs), temperature trends, and voltage drops to anticipate issues before breakdown. Alerts trigger when thresholds or patterns exceed normal behavior. This minimizes service interruptions, improves uptime, and extends vehicle lifespan, key metrics for leasing profitability.
AutoPi devices combine CAN/UDS diagnostics, GPS, and edge compute for local event processing. They buffer data offline and sync to the cloud when connected. The software platform provides APIs for telemetry, OTA updates, and fleet dashboards, ensuring compatibility across mixed OEM vehicles and leasing models.
// built around your industry
Choose a starting point for Car Leasing
Let's match your vehicles and data requirements to the right hardware, then explore your integration together. AutoPi Cloud is included with every AutoPi device.
Match hardware to the data
// fleet data
AutoPi Mini
For supported EV and OBD fleet data. Check make, model, year and required parameters before ordering.
Check Mini compatibility// custom edge software
AutoPi TMU CM4
For Docker workloads and custom edge software. Confirm interfaces and any additional hardware needed.
Explore TMU CM4// delivery scope
Define what your project needs
- Included
- AutoPi Cloud, plus the selected device's documented hardware and standard software capabilities. Check the supplied accessories and connectivity plan for your chosen configuration.
- Configure
- Supported signals, sampling, trips, geofences and data delivery for the chosen device. Validate connectors, power, storage and retention limits.
- Custom development
- Missing signal decoding, external sensor integration and business-system workflows require assessment and an agreed scope.
// your proof of concept
Validate on your vehicles
We'll help you choose devices to purchase for representative vehicles, then work with you to extract the required data, including reverse engineering where needed. Together, we'll agree the signals, installation, integration work and acceptance criteria before expanding the deployment. Feasibility and scope depend on your vehicles.
Discuss your PoC
// contact
Still have questions?
Get in touch with us - we're ready to answer any and all questions.