Skip to content

HOME WORK 01 / 04

FLEET TRACKING ON YOUR OWN SERVER

For a fleet operator whose contracts forbid vehicle data leaving the building — a mapping and reporting platform installed on the company's own server.

FIG. 04 — FLEET

01 THE PROBLEM

Every product on the fleet tracking market is cloud based: vehicle position, driver behaviour and route history all live on the vendor’s servers. Our client’s contracts did not allow that data to leave the country. On top of that, subscription cost grew linearly with the number of vehicles.

02 THE APPROACH

We built the platform to run on-premise from day one: every component comes up with Docker on the client’s own server and works without opening a single outbound connection.

On the interface side we reviewed the competing panels (Wialon, Arvento, Taxy) side by side and fixed what they get wrong: the dark theme is applied before the first paint, so a dark-theme user never sees a white flash; below 1024 pixels the sidebar collapses on its own; map tiles are darkened with a CSS filter in dark mode.

A security review and an automated backup setup were part of the job — handing over a system means handing over the way to keep it running.

03 BUILT WITH

  • TypeScript
  • React
  • Map layer
  • PostgreSQL
  • Docker
  • On-premise

04 THE OUTCOME

  1. Fleet data never leaves the company’s own server; no subscription cost

  2. A documented deployment that comes up with one Docker Compose command

  3. Security review completed, automated backups in place

  4. Interface guide and design decisions handed over in writing

02 / 04 NEXT

FIG. 05 — SMS

05 CONTACT

HAVE A JOB LIKE THIS?

Describe the problem; in the first call we work out the scope and a rough budget together.

Start a project