Fleet management platforms of all shapes and forms pop up on the market every now and then. Differences could be many, but most of the time these products cater to the same pool of customers and satisfy roughly 80% of standard customer needs. Coming up with a different concept requires a deep understanding of the market and advanced analytical skills to pinpoint the free niches with scalability potential.

This is what 360locate used to create Fleet Overview — a fleet-tracking web application aggregating GPS data from multiple GPS monitoring platforms via API. The list of currently supported sources includes flespiWialon360LocateTrusttrack (Ruptela), 3D Services

Let us tell you a little more about what this solution can do for you and where flespi makes a contribution.


Typically GPS tracking web applications like Fleet Overview are bound to or are a part of a specific GPS platform. In the case of Fleet Overview (and this is their key point of difference) the GPS tracking web application is independent of the GPS platform used. As long as there is an API to can connect to, Fleet Overview can pair with a platform.

Our target audience includes GPS Solution Providers, who can use Fleet Overview to enhance their existing product offering, and end customers, who can utilize Fleet Overview for their projects directly.

Fleet Overview can be used in addition to or to replace the GPS platform default. It will differentiate the GPS solution provider from the competition because it can offer a unique piece of functionality for merging data from GPS trackers connected to multiple fleet management software into a single Fleet Overview account.

At 360locate we focus on providing extra value for each customer’s telematics use case. Such an approach is highly efficient since telematics devices produce a lot of data and it’s important to cut out the noise and highlight the value.

As for technologies used, the frontend of Fleet Overview is built in Angular and the backend is built on .Net Core 2.2.


Fleet Overview has all the standard capabilities most other fleet management tools have, thus covering the points of parity to successfully compete in the market.

The standard set includes:

  • Real-time locations
  • Trip History
  • Widget Dashboard for overal analytics

The following features will be added soon.

  • Reporting / notifications
  • Native Mobile App
  • Geofencing

Cooperation with flespi

As we often point out, flespi is a backend. You need an application layer on top of it to be able to use (and sell) it as an end product. 360locate paired Fleet Overview with flespi to delegate the connectivity and communication tasks and focus on the business value for the customer.

Fleet Overview relies on flespi Gateway API to collect telemetry for visualization on the interface. Analytics API is used to compute trip activity on the fly.

What was much appreciated about flespi is the lack of unnecessary components (e.g. the frontend part) that most fleet management platforms offer along with the API.

flespi fit

When a company picks a backend platform for its projects, this is something you cannot switch away from it halfway through, so the decision should be backed with solid arguments in favor of the preferred option.


360locate has experience with flespi and Gurtam for a couple of years now. Before integrating with flespi in Fleet Overview, 360locate created a product called Fleet Health and connected it to Wialon with the help of Gurtam API. Fleet Health is also linked to Fleet Overview, meaning that users can switch from one application to the other with a single user account.

Fleet Overview gives vast opportunities to companies already operating multiple fleet management applications — aggregated dashboards, statistics, and analytics let the decision-makers see the whole picture and act accordingly.