live · Fleet

For the dispatcher who hears about a skipped stop from the customer.

Proof of every delivery.

Every vehicle, driver, stop and proof in one twin, on your own servers. The tracker confirms the arrival; the driver’s phone carries the job; a stop left open is caught as the truck drives off.

See it on a truck like yours — 15 min →What you need

Truck 7 · Morning round · its twinlive

Trip

6 stops11.95 km

First arrival

tracker20:20:13

Outcome

5 done1 failed

RuleEach stop has an arrival zone; the tracker entering it is the arrival. A tap far from the vehicle is a mismatch; leaving with the stop open is an exception.

20:19:56Trip started · Truck 7, Sam Okafor
20:20:13Stop 1 arrival · confirmed by the tracker
stop 3Arrival mismatch · “Arrived” tapped far from the vehicle; the stop proceeds, flagged
stop 4Left without completing · caught as the truck drove off
stop 5Failed: no one present · the job goes to the exceptions lane
20:23:08Stop 6 late · seen coming from the ETA
20:23:22Trip ended

What the twin holds: position · driver · stops · proofs · maintenance · compliance · historydemo run · the company’s own time

1The problems

What a fleet owner actually hears.

Four sentences from the people who run vehicles. Each one is answered below, with the screen that answers it.

the customer, on the phone

“A driver says he was there. The customer says he wasn’t.”

Answered by the tracker’s arrival and the proof ↓

the dispatcher, too late

“We find out a stop was skipped when the customer calls.”

Answered by the exceptions lane ↓

the driver, in the yard

“The driver’s offline half the day and the app gives up.”

Answered by a phone that queues ↓

the fleet manager, with three logins

“Three tracker vendors, three portals.”

Answered by one board, any tracker ↓

2How HOLOIN answers each

Four problems, four screens.

Each answer below is something the product did in the demo run, shown on the screen where it did it.

Problem 1 · “A driver says he was there.”

The tracker says when the truck arrived. The phone says what happened there.

Every stop has an arrival zone. The vehicle’s tracker entering it is the arrival, timed by the device, not by a tap. The driver completes the stop with a photo, a signature and the recipient’s name; the proof is marked geo-verified only if the zone registered the arrival first. Everything lands on one timeline.

Outcome A disputed stop is settled from the timeline, not from memory.

Truck 7 · Morning round on its own page: the demo map with the truck and its round, the next stop with its ETA, and the stops — three completed, one en route, two pending. — **From a demo run:** Truck 7’s morning round on its own page: the truck and its round on the demo map, the next stop, and each stop done or to come.

Problem 2 · “We find out when the customer calls.”

A stop left open is caught as the truck drives off.

When the vehicle leaves a stop’s zone with the stop still open, the twin raises an exception and the driver’s phone asks what happened. A failed stop sends its job to the exceptions lane, where the dispatcher drags it onto any open trip. An ETA running past the window shows “at risk” ten minutes before it is late.

Outcome The exception reaches your dispatcher before the customer does.

Dispatch · exceptions lane

Truck 7 · Sam Okafor

left incompleteStop 4 · Calvessa Cold Storeprompt sent

failedStop 5 · Orvellan Retail Warehouse · no one presentre-plan

lateStop 6 · Ulvarin Depot20:23:08

From the demo run. Truck 7’s round on the board: one stop left open, one failed, one running late — each in the exceptions lane before anyone phoned.

The dispatch board’s timeline from 06:00 to 12:00 with the drivers’ column: Sam’s round on Truck 7 in progress with its stops, and Van 12’s bar beside it. — **From a demo run:** Truck 7’s morning round on the dispatch board, stop by stop.

Problem 3 · “The app gives up offline.”

The phone queues. The server counts once.

Start, arrive, complete with proof, fail, skip: each action is stamped with the phone’s time and sent at once, or queued in order when there is no signal and delivered when it returns — on Android even with the app closed; on iPhone when the app is opened. Every action carries its own id, so a replay is answered “Already received.” and written once.

Outcome Nothing a driver did is lost, and nothing is counted twice.

The driver’s phone at stop 3, Halmorvic Depot, marked Arrived: its address, and Complete, Couldn’t deliver and Skip. — **From a demo run:** the driver’s phone at stop 3 after “Arrived”: the stop, its address, and Complete, Couldn’t deliver or Skip.

Problem 4 · “Three vendors, three portals.”

One board. Whichever tracker is in the truck.

The install carries its own tracker server; a tracker is registered by its IMEI once and never has to be opened in a vendor’s console. The vehicle is the record and the tracker is a part of it: swap the tracker and the vehicle keeps its history, and the new tracker’s old trips never count against this truck.

Outcome One board, whichever hardware is in the truck.

Truck 7 and Truck 5 on the demo map, both moving, each pin with its name beside it. — **The live map in the demo.** Truck 7 and Truck 5 moving, on the demo map. Truck 7 reports through a cellular tracker, Truck 5 through a LoRaWAN one; the map colours vehicles by motion, so the tracker kinds are named here, not on it.

And the rest of the day’s work

GeofencesEnter and exit per vehicle, alert on either or both; an exit is never recorded without an entry.

Maintenance dueBy date or by the tracker’s odometer; logging a service moves the schedule on.

Fuel economyOnly from consecutive full-tank fills with odometer readings — never a guess, never mixed units.

ComplianceLicences and vehicle documents with their expiry; expiring-soon in one list.

InspectionsThe driver’s daily checklist; a failed item raises a maintenance flag, with the photo.

Driver eventsHarsh braking, acceleration and cornering as the tracker itself reports them, credited to the driver at the wheel.

ReportsTrips, utilisation, geofence dwell, maintenance due, compliance expiring — as a table or a CSV, every run logged.

YardsSlots with length and category rules; a check-in that doesn’t fit is refused with the numbers.

3The twin of a vehicle

The vehicle is the record. Everything attaches to it.

A tracker, a fuel sensor, a temperature probe in the reefer, a door contact: each is a device placed in the vehicle by its role. The twin counts a device’s readings only since it was installed there, so a tracker moved from another truck brings none of that truck’s kilometres. What isn’t measured is shown as unknown, never as zero.

On the live page, a reading is pushed to the screen as it arrives, no refresh; the driver, the parking slot, the next service and the expiring documents sit beside it.

Now

Position, speed, ignition

From the current tracker, since it was installed; moving, stopped or silent by one definition the map shares.

Who

The driver at the wheel

One active assignment at a time; licence flags beside the name.

Parts

Devices by role

Tracker, fuel, reefer temperature, door, dashcam — each with its own thresholds and status.

Lines

Alarms and rules

Speed over, geofence crossings, fuel below the line — rules you can read, switched on per company.

Work

Maintenance and compliance

Schedules, overdue, the next date; vehicle documents expired or expiring.

Then

History

Trips, stops, proofs, geofence events, the yard stays — all against the vehicle, surviving a tracker swap.

4What the twin changes in the day’s work

Fewer phone calls. Fewer arguments.

Stated as changes, not as numbers: your numbers are yours to measure, and Why it pays gives you the arithmetic.

Before

“Were you there?” is a question for the driver.
A skipped stop is discovered by the customer.
A phone with no signal loses the afternoon’s work, or sends it twice.
Each tracker vendor has a portal; the fleet lives in a spreadsheet.
Fuel economy is an average of whatever was typed in.
A tracker moved between trucks carries the wrong history with it.

With the twin

“Were you there?” is answered by the tracker’s time at the zone.
A stop left open raises an exception as the truck drives off.
Queued actions land once, in order, with the phone’s own times.
One board; the tracker is a part, the vehicle is the record.
Economy only from full-tank fills with odometer readings, or “not measurable”.
A device’s readings count for a vehicle only from the day it was installed there.

5OT and IT, in one twin

When a truck goes quiet, which link broke?

The tracker is the OT. The tracker server inside the install, and the forward from it to HOLOIN, are the IT. The twin holds the path between them, hop by hop.

A silent tracker and a stopped server look the same on a map: the dot stops moving. They are different problems with different people to call. The path check walks from the server outward — ingestion, the tracker server, the cellular link, the tracker — and names the first hop that stopped answering. A stopped server raises one alarm for the installation, not one per truck.

OT · what is measured

The vehicle’s own signals, as the tracker reports them.

Position, speed, heading, ignition
Odometer, inputs, external power and battery
Harsh events the tracker itself detects
Fuel, reefer temperature, door — sensors by role

IT · what keeps it reporting

Devices in the twin too, with their own health.

The bundled tracker server: up, its version pinned
The forward to HOLOIN: receiving, last packet
The LoRaWAN gateway at the depot: heard, silent, never seen
The path from any fix back to the server

Truck 7 · tracker · path to the server

HOLOIN · ingestion · receivingok

forward · JSON

Tracker server · bundled · upok

cellular

Tracker in Truck 7 · heard 20:20:13ok

Every hop known. When the truck goes quiet, the check says which hop stopped: the tracker, the cellular link, the tracker server or the forward.

Drawn from the demo run. At stop 3 the driver’s tap was far from the vehicle; the twin trusted the tracker and flagged the tap. The arrival is the tracker’s word, not the driver’s.

6How it’s deployed

Buy the trackers. Everything else comes inside.

One install bundle carries every server a tracker needs. You open the ports; the trackers point at your address; the vehicle appears.

You supply

One Linux server with Dockeryours, or one we run for you in the country you choose
The trackersany model listed below, or your own if its protocol is one the tracker server speaks
The ports your IT opensone per tracker protocol; the install guide lists them

Inside the install

The tracker serverreceives the trackers’ protocols and forwards each fix; registered once by IMEI, never opened by hand
The LoRaWAN network serverfor LoRaWAN trackers and the sensors in the vehicle, through your own gateway
The driver’s appserved from the same address, installs from the browser, works offline
The database, the backups, the web entryone compose file, one address

Kept running by the install itself

One scriptready in 2 min 42 s on the acceptance box (run 39194860273)
Nightly backup, monthly restore drilla failed one is an alarm in the product
Upgrade in placesame volumes, registrations and readings intact, proven on every release
No telemetrythe bundled servers’ phone-home is off; CI fails if any container reaches out

The servers this kind of asset uses, each shown only when its acceptance run passed; statuses from the facts file.

7Without HOLOIN

Five systems, or one.

The same fleet, run the usual way. No names: the categories are what matters.

Bought separately

A tracker portal per vendor — positions on their servers, one login each, a subscription per device.
A dispatch tool — jobs and trips, unaware of where the truck actually is.
A driver app — from a third vendor, with its own account for each driver.
A maintenance and compliance spreadsheet — kept by whoever remembers.
A monitoring tool for the servers — if anyone watches the servers at all.

Five contracts, five logins, no path from one to the other. When the truck goes quiet, nobody can say why.

In HOLOIN

The tracker server is inside — positions on your server, one login for everyone.
Dispatch reads the tracker — the arrival is the zone, the exception is the drive-off.
The driver’s phone is the same product — same install, same account, offline by design.
Maintenance, compliance, fuel, inspections — on the vehicle’s twin, from the tracker’s odometer and the driver’s checklist.
The path check — the tracker, the server and the forward are devices too; one alarm names the hop.

One installation, one database you own, one price counted in devices.

8What it costs

Counted in devices. Never in people.

One licence per installation, per year, by device tier. A tracker is a device; a driver’s phone, a dispatcher’s login and a manager’s report are not. Add drivers, dispatchers and technicians without a change to the bill.

The whole grid, every tier and every pack, is on Pricing — published, with what counts as a device and what is included.

US$7,000a year

A fleet of 70 vehicles, one tracker each — the 100-device tier, from the published grid.

The platformUS$2,500
The Fleet packUS$4,500
Dispatchers, drivers, techniciansincluded
The tracker server, the radio server, the driver appincluded

9Secure, and kept running

Your server. Your drivers’ data. Nothing phones home.

Not a policy page: each of these is a property of the software you can check on your own server.

One installation, yours

Installed from a bundle that carries everything it needs. Never a shared cloud: one installation per customer, or one your integrator runs for you, each client a company of its own.

PostgreSQL you own

Every position, proof and record in a database you administer. A nightly backup you can restore anywhere, drilled monthly.

Drivers’ data, handled

Export a driver’s record in one file; erase it on request and the vehicle history stays. Every access to a driver’s record is logged.

Nothing phones home

No telemetry in the product, none in the bundled servers. Proved with the network sealed on every release.

Your rules stay yours

Lines, rules, schedules and what the twin learned are text and arithmetic in your database; they leave with you.

An audit log that can’t be edited

Every change, by whom, from where — append-only in the database itself, for seven years, even for the database’s own administrator.

10The four questions

What you actually want to know.

Do I have to install anything?

No. We run HOLOIN for you on a dedicated server in the country you choose, never shared with another company, and you can take it with you. If you have your own servers, install it there instead; same product.

What do I need?

Trackers from the list above (or any the tracker server speaks), a SIM in each, and the ports opened for their protocol. For LoRaWAN trackers and vehicle sensors, one gateway at the depot. The driver’s phone needs a browser.

What does it cost?

Per installation, per year, by device tier: from US$4,000 a year for the platform and one vertical, up to 100 devices; the Fleet pack as above. The whole grid is on Pricing. No per-seat fees.

Who do I call?

Hours, channel and response time: on request. Every installation can produce a support bundle on demand, a readable archive with no personal data or secrets, which your IT team can check before it goes to us.

11The way in

See it running on your trucks.

I run the fleet

Fifteen minutes on Truck 7’s morning round: the arrival the tracker confirmed, the tap it didn’t, the stop left open, the exception on the board, the proof on the phone. Your trackers if you bring their IMEIs.

See it on a truck like yours — 15 min →Get demo access →

I install systems for fleets

One installation per client. The tracker server inside, the ports in the install guide, pricing per installation.

Start a partner conversation →