Traccar
Open-source GPS tracking server in Java that supports a very wide range of tracker protocols, each on its own port. Use MySQL or PostgreSQL in production rather than the built-in database, and open only the ports your devices use.
Run Traccar, a dispatch system or your courier app on a VPS with full root access. Open the ports your trackers report on, push live positions to the control room over WebSockets and keep months of trip history without paying per vehicle.
Four cores handle many open device connections and steady position writes, with 16 GB of RAM for Traccar and the database and 320 GB of disk for several months of history.
Order VPS V3Kenyan transporters, courier firms and fleet installers often start on a hosted tracking platform billed per device per month. That is fine for ten vehicles and painful for three hundred. Running an open-source server such as Traccar on your own VPS turns that per-unit charge into a fixed server cost, and lets you brand the web and mobile apps as your own.
GPS workloads are unusual. Each tracker holds a connection open and reports every few seconds while moving, often over TCP on a protocol-specific port, so the server handles thousands of small writes rather than a few heavy page loads. Position history grows every day, and dispatchers expect the map to update live. That means open firewall ports, a well-tuned database, plenty of disk and a WebSocket layer for the control room.
Couriers and last-mile delivery apps add their own load: rider apps posting location, customers following a parcel link, and order updates going out by SMS or WhatsApp. A HostingKE VPS gives you root access to run the tracking server, the dispatch API and the database side by side, and our support team can help with firewall rules and sizing when you add vehicles.
GPS devices report to an IP address and a port set during installation. Shared hosting cannot open custom TCP or UDP ports, so the units show as offline. A VPS lets you open exactly the ports your device models use.
A vehicle reporting every ten seconds while moving produces thousands of rows a day. Without a retention policy, indexes and enough disk, reports slow down and the dashboard lags behind the trucks it is meant to follow.
Dispatchers need positions to move on screen, not after a page refresh. Live updates over WebSockets need a long-running process and server memory, which a basic web hosting account will not give you.
Riders lose signal on the Thika Road underpasses or upcountry routes, then reconnect and upload a burst of queued points. Your API must accept those bursts quickly so deliveries are not marked late by mistake.
A typical Kenyan logistics stack pairs a GPS server with maps, routing and a live dispatch layer. These are the common building blocks.
Open-source GPS tracking server in Java that supports a very wide range of tracker protocols, each on its own port. Use MySQL or PostgreSQL in production rather than the built-in database, and open only the ports your devices use.
Open Source Routing Machine calculates driving routes and travel times from OpenStreetMap data. A Kenya extract is small enough to process on a VPS, but preprocessing needs extra memory, so plan RAM for that step.
OpenStreetMap geocoder that turns addresses and place names into coordinates. Importing just the Kenya extract keeps the PostgreSQL database manageable and avoids per-request charges from commercial geocoding services.
WebSocket servers that push new positions and order status to dispatch screens and customer tracking pages. Both run as long-lived processes behind Nginx, which is why they need a VPS rather than shared hosting.
Most courier firms run their own Laravel, Django or Node.js backend for orders, rider assignment, proof of delivery photos and customer notifications, with Redis queues for background jobs.
Count every tracker, rider phone and asset tag sending positions, not just vehicles out on the road today.
Treat this as a guide: real load depends on how often each device reports, how long you keep history and how many people watch the live map.
0 of 8 done. Tick them off as you go.
Trackers and rider phones drop off the network on long upcountry stretches and in some estates, then upload stored points when they reconnect. Pick devices with good offline buffering and make sure your server accepts late, out-of-order positions.
Every tracker runs on a mobile data SIM. Sensible reporting intervals, such as more frequent while moving and rarely when parked, keep monthly data bundles affordable for the fleet and also reduce the write load on your server.
Tracking a company vehicle also tracks the person driving it. Under the Data Protection Act 2019, tell drivers and riders what is recorded and why, restrict who can view history and keep it only as long as you need.
Plans from KES 2,000 a month, paid by M-Pesa or card.
Size your server