Skip to main content

// signal acquired · self-hosted fleet tracking · built on Traccar

I led the team behind the platform that watches fleets move.

Tornet GPS is a self-hosted fleet-tracking product built on Traccar’s open-source engine. I led and managed the team that turned it into a commercial product for fleets across the region — I owned the product direction; the engineering is my team’s.

Visit Tornet GPS
  • Product Strategy & Lead
  • Engineering Management
  • Team Leadership

// the scroll is the journey

Every trip, replayed.

The platform replays where any vehicle has been — a designed view of a Traccar-powered capability. // illustrative route · no real coordinates

An illustrative trip replay — about 42.6 km over 38 minutes, with 3 stops. The route and readouts are designed, not real telemetry.

// under the hood — what the team I led built on Traccar

Where the product meets the engine.

The team I led extended Traccar with a thin layer of product code — the seams that make Tornet GPS a product, not just a download.

  • // api · pagination

    Pagination subsystem

    The team extended Traccar's storage layer with count-aware DB paging — exposed through ~5 paginated endpoints (devices, positions, events, summary, stops/trips).

  • // reports · daily

    Daily & email reports

    A daily/combined report plus background "slow" summary reports, delivered by email from an HTML template.

  • // auth · access

    Verification & access guard

    Email verification on registration, and a calendar-window guard that restricts position retrieval to user-defined time windows.

  • // app-updates

    App-update endpoint

    A mobile app-update resource keeps the native clients current — one of the real new seams on top of the stock API.

  • // notifications

    Notification map-links

    Firebase per-event channels, map links inside alerts, and reverse-geocode toggles across 3 new config keys.

The tracking engine itself — 200+ protocols, 2000+ device models, trip and stop replay, geofencing, the reports engine, and the React web app — is Traccar, open source under Apache 2.0. Credited, never claimed. I led and managed the team that built the product layer on top of that engine, and owned its direction.

The Traccar web client behind Tornet GPS — server and account settings.
The Traccar web app behind Tornet GPS — settings & account administration.
The Traccar web client behind Tornet GPS — a summary report view, with device names, plates, and addresses masked.
The same Traccar web app — a summary report. Names, plates & addresses masked.
The custom Tornet GPS marketing landing page I designed — the product's front door.
The custom marketing landing page — the one front-end I designed myself.
the Traccar web app — live fleet tracking
The same Traccar web app — live fleet tracking. Device names, the on-map label & the popup odometer are masked.

// A note on the screenshots: the real screens have device names, plates, odometer, and addresses masked. The trip-replay above is fully designed — no customer data.

// the work, by the numbers

What the fork added — and what the platform already gave.

Two honest tallies. On the left, what the team I led shipped on top of Traccar. On the right, the reach of the Traccar platform itself — credited, never claimed.

4
net-new backend subsystems
7
API endpoints added~5 paginated + 2 new
3
new config keys
18
merged PRs on the fork
200+
device protocolsthe platform supports — Traccar
2000+
device modelsthe platform supports — Traccar

I led the team that built Tornet GPS, and owned its product direction.