Fleet Scanner Opens On-Premise Deployment for GPS Tracking and 18 Fleet Modules

Vehicle positions, camera footage, customer records and supplier accounts now run inside infrastructure the fleet owns

Fleet operators can now install Fleet Scanner on their own hardware. The company has opened on-premise deployment of its GPS tracking software, removing the need to send vehicle data to a shared cloud service.

Almost all fleet tracking is sold as a hosted subscription. The operator fits devices to vehicles. Every position those devices report is then stored on servers owned by the software vendor. The tracking history, the driver records and the route data all live somewhere the operator has never seen and cannot inspect.

Self-hosted deployment reverses that. The software runs on the operator’s own servers, in a location they pick. Vehicle positions, trip history, video footage and driver records stay on hardware the operator controls.

What self-hosted GPS tracking software means

Self-hosted means the software is installed on the customer’s own servers. It is not accessed as a shared online service. The operator runs the application, holds the database and manages access.

Three things change when tracking moves on-premise.

The operator sets the retention period. Cloud tracking services keep data for a fixed window and delete it on their own schedule. On-premise, the fleet decides how long trip history is kept. That matters when a dispute or an insurance claim comes up long after the journey.

The operator controls access. Nobody outside the business can query the database. Every login is recorded on systems the fleet audits itself.

The operator is not exposed to vendor change. Price rises, acquisitions, policy updates and closures happen. None of them put the fleet’s tracking history at risk when that history sits on its own hardware.

Fleet Scanner does not certify compliance with any data protection law. It does not replace legal advice. What self-hosted deployment does is let operators show where vehicle and driver data is stored, and who can reach it.

Why GPS tracking alone stopped being enough

Tracking is usually the first fleet software a business buys. For a while, a live map answers the main question. It stops being enough once the fleet grows.

A map shows where a vehicle is. It does not show whether that vehicle is due for service. Or which customer the load belongs to. Or what the job cost, whether the last repair invoice was paid, or when the driver’s licence expires. Those answers usually sit in four or five separate tools. Each one holds its own copy of the vehicle list, and each one slowly goes out of date.

Fleet Scanner combines more than 18 connected modules in one system, with over 60 sub-sections. Tracking is the base layer rather than the whole product. Every other module reads from the same records.

Modules included in the platform

On-premise and white-label installation

The complete system installs on the operator’s own servers, in whichever data centre or region they select. No features are held back for a hosted version. Companies that resell fleet services can also present the platform under their own brand, domain and colours. Their customers see the reseller, not the software underneath.

Access control and data handling

Retention rules, backup timing and user permissions are set by the operator, not the vendor. Permissions work by role. A workshop supervisor and an accounts manager open the same system and see different things. Access logs capture who viewed which record and when. That is the kind of evidence data protection rules expect a business to produce on request.

Live vehicle tracking

Every vehicle on one live map. Past routes replay as far back as the operator’s retention setting allows. Geofences raise alerts when a vehicle enters or leaves a set area, or moves outside agreed working hours. Tracking feeds the rest of the platform too. A position recorded once reaches maintenance, dispatch, billing and reporting without being copied anywhere.

In-vehicle video and event capture

The video telematics layer sits beside the tracking data rather than in a separate portal. Every clip carries the trip, driver and vehicle it belongs to. An event can then be reviewed next to the speed and braking readings from the same second. Detected events flow into driver scoring and coaching records. Audio capture can be switched off where local consent rules require it.

Driver records and scoring

Driver management works from one profile per driver, holding licences, qualifications, training records and expiry dates. Reminders go out ahead of each renewal. Safety scores are worked out from tracking and camera data rather than typed in. Shift records, vehicle assignments and performance history stay on the same profile.

Servicing and workshop control

Vehicle maintenance is scheduled by distance covered and engine hours, not calendar dates alone. A vehicle working hard gets serviced sooner than one that mostly sits still. Work orders capture parts, labour and cost against each vehicle, building a full service history. Maintenance and trip planning share a database. So a service falling due on a vehicle already booked for a job shows up before a delivery date is agreed.

Trip planning and dispatch

Planning, allocation, live progress and completion run in one sequence. Each trip carries its own fuel use, driver, vehicle, customer and cost. Margin is measured job by job instead of guessed at month end.

Fuel use and loss detection

Fuel purchases are compared against distance covered and engine hours. Gaps that do not add up are raised for review. Each refuelling event can be checked against where the vehicle was at that moment. That is how most fuel loss gets traced.

Customers, quotes and enquiries

Customer relationship management runs inside the fleet system rather than a separate CRM, covering records, contacts, enquiries, quotations and correspondence. Those records sit next to trips and invoices. So a conversation about service quality can point to the real delivery history on that account. An enquiry runs from first contact to completed job without leaving the platform.

Suppliers, workshops and purchase orders

Vendor management runs from a single register covering workshops, parts suppliers, fuel providers, insurers and subcontractors. Each carries contact details, agreements, rate cards and renewal dates. Purchase orders and supplier invoices are recorded against both the vendor and the vehicle or job they relate to. Total spend per supplier then becomes readable. That is hard to do when purchase records sit in accounting software and vehicle records sit elsewhere.

Job costing and invoicing

Job costing, invoicing, payments and outstanding balances all link back to the trips that produced them. Operational and financial records share one database. Cost per job and cost per vehicle are read from live data instead of rebuilt from exports at month end.

Document expiry and compliance records

Document management covers registrations, insurance policies, permits, inspection certificates and driver paperwork, each stored with expiry tracking and early reminders. The platform stores and organises these records. It does not certify that an operator is compliant. It does not replace an inspection or an approval issued by a regulator.

Plain-language AI queries

The built-in AI assistant answers questions about the fleet’s own data in ordinary language, rather than requiring a report to be built. An operator can ask which vehicles idled beyond an hour yesterday. Or which drivers recorded the most harsh braking this week. Or which vehicles fall due for service before month end. The answer comes back directly.

Reporting, alerts and API access

Reports can be scheduled and emailed, so they reach the people who need them. Alerts can be tuned, so notifications nobody acts on get turned off rather than ignored. An API exchanges data with accounting packages, fuel card providers and third party hardware. It also lets operators export their own records whenever they choose.

How it can be deployed

Fleet Scanner comes in three forms. Cloud hosting suits operators who prefer not to run servers. Self-hosted deployment puts the complete system on the operator’s own hardware. White-label deployment lets resellers and service providers offer the platform under their own brand.

Self-hosted and white-label deployment are available at the Enterprise tier. Cloud pricing is quoted in local currency by market.

About Fleet Scanner

Fleet Scanner is a fleet management platform. It combines GPS tracking, video telematics, trip operations, vehicle maintenance, driver management, customer relationship management, vendor management and finance in one system. It serves transport, logistics and field service operators internationally. Deployment is available in the cloud, on-premise or white-labelled.

More information is available at fleetscanner.io