The leasing company sees every asset in the portfolio: where it is now, how far it has driven and how many hours it has worked, whether it has left the permitted region and whether it moves while parked. The lessee works in the same portal with their own login and sees only their vehicles.
Four questions a leasing company asks about every asset in its portfolio.
Live map, tracks and stops for any day. If a tracker stops reporting, a notification goes out by email, Telegram, Viber or in the portal.
Geofences with entry and exit alerts. Region or country borders can be imported from KML, KMZ or GeoJSON, with an alert as soon as the vehicle crosses them.
Guard mode draws a circle around the vehicle. Leaving the circle or switching on the ignition raises an alarm with sound in the portal and a messenger alert. With Globus sensors it also covers shock, doors and tilt.
Mileage by day, engine hours and CAN odometer, trips, idling. The data for estimating wear and residual value.
Features that cover day-to-day work with a leasing portfolio.
The lessor sees the whole portfolio, the lessee only their vehicles and only the allowed features: access to vehicles, groups and about 25 permissions.
A link to the vehicle location and track stays valid until the date you set and can have a password. Handy for a bank, an insurer or a security team.
Service schedules, reminders and service history with attachments: you can see whether the lessee looks after the equipment.
When the contract ends, the vehicle moves to a new client: the previous client's access and alerts are removed, the history stays.
REST API with documentation and event webhooks: geofence entry and exit, alarms, lost connection. Data flows into your CRM or accounting system.
Refuels and drains from a fuel level sensor or CAN data, with an alert on a suspicious drain.
Lost connection shows up in notifications right away. The backup channel takes coordinates from the driver's phone via Telegram, and in GPS jamming zones the route is recovered from the CAN odometer and the road graph.
For each geofence you can set commands the server sends to the tracker on entry or exit: for example, switch on an output when the vehicle leaves the permitted region, or change the reporting interval. On compatible trackers the account owner can also switch the control output manually from the portal. What the output actually drives, for example a starter blocking relay, depends on the installation wiring.
Scheduled email delivery of PDF reports, export to PDF and Excel. The portfolio can be split into groups by lessee or region.
Teltonika, Globus, Bitrek, Ruptela, trackers with the Wialon IPS protocol and several more protocols, 100+ models in total. Trackers already installed connect by changing the server address.
Each lessee gets their own login with only their vehicles and only the features you allow.
Set the region borders as a geofence or import them from KML or GeoJSON and turn on the exit alert and, if needed, a command to the tracker. The alert arrives by email, Telegram, Viber or in the portal.
Trip and sensor history stays on the platform. The vehicle moves to a new client, and the previous client's access and alerts are removed.
Yes. The REST API with Swagger documentation returns vehicles, telemetry, tracks, reports and invoices, and webhooks send geofence, alarm and lost connection events.
Partner integrators in your region or your equipment supplier do the installation. If trackers are already in place, you only point them to the cloudGPS server.
Tell us how many assets the portfolio has and which trackers are already installed, and we will suggest a connection plan.