How the system works
A tracker in the vehicle, our server, the gpsonline.tj account and an app on your phone. This page shows how they connect, what the account contains and who sees what — and the demo fleet shows it all at work.
Data path
The tracker sends one location point after another. Here is what each point passes through and who is responsible for each stage.
Tracker in the vehicle
Works out its position from satellites and sends a point. While there is no network, points wait in the tracker's memory.
What happens without a connectionMobile network
The point travels over mobile internet through the tracker's SIM card.
Our server in Dushanbe
The software platform receives the points, turns them into trips, events and reports, and stores the trip history.
software platform
Account and app
Vehicles on the map — in a browser at gpsonline.tj and on your phone.
Hover over a card to highlight its part of the diagram.
us
Releases the versions of the software the account runs on.
According to the software platform developer, September 2026.
Carries the points from the tracker to our server.
In the account
The groups follow the menu of the gpsonline.tj account. Each feature has its own page, and many of them can be tried there on the demo fleet.
Demo fleet
Trucks on the M34 and M41, deliveries around Dushanbe, machinery in Dangara, runs along the Pamir Highway. Pick a vehicle and its trip, report and maintenance plan open on the feature pages.
moving since 10:38
Sample data only: the vehicles, drivers and routes are fictional, and the roads are drawn schematically. This is not a coverage map and not client data. Country borders: geoBoundaries, ODbL licence.
Access
An employee is assigned vehicles, places and geofences, and does not see the rest. The activity log shows who signed in, when and from which address, and what they changed.
The roles here are an example. In the account you create your own users and roles and assign each person their own vehicles, places and geofences.
| Time | User | Action | IP address |
|---|---|---|---|
| 09:12 | dispatcher.sughd | signed in | 10.0.•.• |
| 09:20 | dispatcher.sughd | changed the rule “Geofence exit” | 10.0.•.• |
| 10:05 | mechanic.khorog | changed the geofence “Khorog” | 10.0.•.• |
| 11:40 | director | created an API key | 10.0.•.• |
The account issues separate access keys for integrations.
API and integrationsCompatibility
We choose and install the trackers ourselves. If your vehicles already have other trackers, send us the models and we will check whether they work with the system.
No, they are all fictional: the demo fleet's vehicles, drivers and routes follow a preset scenario. Our clients' vehicles are not shown on the website.
That is how often the demo fleet is recalculated. In the account, how often location points arrive is set in the tracker's settings.
Your account shows your own vehicles, geofences and rules. The set of sections depends on your plan, and some features depend on the hardware: for example, to see refuelling and fuel drains you need a fuel level sensor.
Request
Tell us how many vehicles you have and what you need to monitor — we will pick the hardware and open demo access.
software platform
