AlphaTrace is a GPS platform for fleets that work where the roads, the signal, and the fuel all go missing. Teltonika devices stream into a live map, trips, geofences, and alerts an operator can act on — plus a fuel module that shows the evidence behind every drain.
Illustrative — not customer data.
Platform record · 2026
01 What AlphaTrace does
Not a map with a login. Positions become trips, zones become rules, rules become alerts someone has to acknowledge, and every one of them is readable over an API. The fuel module is the part most operators buy it for.
P—01
Where everything is, right now
Every asset on one map with its last fix, its heading, and its state. Open a unit and the telemetry is there: speed, fuel level, battery voltage, GSM strength, and how long ago it reported.
P—02
Movement as a record
Movement is stored as trips, not a pile of points. Filter by asset and date, open one to replay the route, and export the range to CSV when somebody needs it in a spreadsheet.
P—03
Zones that mean something
Draw the pit, the depot, the customer yard, or the road you do not want used. A zone can be local to one site or shared across the org, and each one raises enter, exit, or dwell alerts.
P—04
Ten rule kinds, scanned every five minutes
Rules cover movement, fuel, and the device itself — because a tracker that has been unplugged is the alert that matters most. Email is opt-in per rule, and every alert lands in a feed that has to be acknowledged.
P—05 Module
Evidence, not suspicion
Drains and refills are detected from the level curve, and each event opens an evidence view: the litres, the window, the position, and the chart around it. That is the difference between believing fuel is walking and being able to show it.
P—06
Structure that matches the operation
Assets belong to sites and to colour-coded groups, and both filter the map, the lists, and the alert rules. Units carry their device and SIM details, so the hardware inventory stops being a spreadsheet somebody forgot to update.
P—07
Ask the fleet a question
Ask in plain language and the assistant runs tools over your own data — assets, trips, alerts — rather than guessing. Conversations persist, so an answer can be checked later instead of retold.
P—08
Your data, in your systems
Everything the dashboard shows is available over HTTP: assets, positions, latest fixes, trips, zones, groups, alerts, and fuel events. Keys are scoped and rate limited, with documentation inside the app.
/api/v1 endpoints02 How it works
Four moving parts, and no middleware zoo between them. A device streams binary frames over TCP; ingest decodes and stores them; the database decides who may see what; and every surface — map, alerts, API — reads the same rows.
03 Field reality
AlphaTrace was built around fleets in Central Africa: long distances, thin coverage, fuel that disappears, and crews spread over sites that must not see each other's data. Those constraints shaped the product rather than being patched over it.
F—01
Coverage
F—02
Fuel
F—03
Access
04 Hardware & rollout
AlphaTrace runs on Teltonika FMC-series trackers. If you already have them fitted, they can be repointed rather than replaced; if you do not, we supply and configure them.
Vehicle types, what each one can expose about fuel, which sites matter, and who is allowed to see what. Existing hardware is inventoried before anything is bought.
You receive A device and module plan against your fleet, with a price.
Trackers are fitted and configured over FOTA to report to our ingest. Fuel sources — CAN adapter, OBD, analogue sender, or BLE probe — are wired and calibrated per vehicle type.
You receive Units reporting live, each with its device and SIM recorded.
Sites, groups, and geofences are drawn to match how the fleet actually works, then alert rules are set on top of them. Members are invited with a role and their sites.
You receive A configured org: zones, rules, groups, and scoped users.
The platform runs in production and we operate the ingest. Rules get tuned once real traffic shows which ones fire too often and which never fire at all.
You receive A live dashboard, working alerts, and API keys if you want the data elsewhere.
05 Access & control
Tracking data is sensitive: it says where people were and when. The boundary is enforced where the data lives, so it cannot be lost by a missed check in a screen.
Row-level security in Postgres. One organisation cannot read another's positions, trips, alerts, or fuel events, whatever the request path.
A member can be limited to specific sites. The limit is applied in the same policies that enforce tenancy — it holds on the map, in exports, and through the API.
Owner, admin, manager, operator, and viewer. Fleet edits, member management, and API keys sit behind the roles that should hold them.
Keys carry the same scope as the member context they belong to, and are rate limited. A key for a customer portal cannot read the rest of the fleet.
Ingest and database both run in Frankfurt (eu-central-1). Positions are written once, in UTC, and displayed in each site's own timezone.
The data is yours. The REST API returns it in full, and the schema is documented — leaving is a task, not a negotiation.
Ask how any of these is implemented and you will get shown the policy, not a diagram of one.
06 Questions
Teltonika FMC-series trackers, streaming Codec 8 and 8E over TCP. Variable-length IO is kept intact, so BLE fuel probes, EYE sensors, and driver-ID readers arrive attached to the position they belong to. If you already run Teltonika hardware, it can be pointed at our ingest and start reporting without being replaced.
The device keeps recording and forwards its backlog when it reconnects, so the trip fills itself in instead of disappearing. A signal-lost rule tells you when a unit stops reporting, and an offline rule tells you when it has been quiet longer than you allow.
Through whatever the vehicle exposes: a CAN adapter, an OBD reading, an analogue sender, or a BLE probe. AlphaTrace detects drains and refills from the level curve and opens an evidence view around each event — the litres, the time window, and the position — so a suspicion becomes a document.
Postgres 17 with PostGIS in Frankfurt, and the ingest service runs in Frankfurt too. Tenant isolation is row-level security inside the database, and each member can be scoped to specific sites, so a site supervisor sees their own site and nothing else.
Yes. A public REST API at /api/v1 covers assets,
positions, latest fixes, trips, zones, groups, alerts, and fuel
events. Keys are scoped, rate limited, and documented inside the
dashboard.
Per asset, per month, with fuel monitoring priced as a separate module. Tell us the fleet size, the vehicle types, and whether devices are already fitted, and you get a quote rather than a call to arrange a quote.
07 Request a demo
Tell us the fleet size, the vehicle types, and whether trackers are already fitted. You will get a walkthrough of the live platform and a price for your fleet — from the person who built it, within one business day. Every asset, every litre, accounted for.