Our Story

The problem we saw

The fleet tracking industry settled into a pattern years ago. Vendors host the platform, own the data pipeline, and charge per vehicle per month. For small operators, the entry price seems reasonable. But as fleets grow, so does the bill — and the dependency. Switching providers means losing historical data, retraining teams, and rewiring integrations. The economics reward lock-in, not quality.

We met fleet managers across three continents who described the same frustration in different words. They wanted reliable GPS tracking. They wanted to see their vehicles in real time, set geofences, pull trip reports, and monitor driver behavior. What they did not want was a pricing model that punished them for growing, or a platform that treated their operational data as someone else's asset.

What we decided to build

Open VTS is vehicle tracking software that you can self-host on your own infrastructure. Your data stays on your servers. You connect your own GPS devices — the hardware you already own or can buy at commodity prices — and the platform gives you real-time tracking, route history, geofencing, alerts, reports, and the tools a working fleet actually needs.

There is no per-vehicle fee. There is no artificial limit on how many assets you track. The cost of running Open VTS is the cost of your server and your time, and we have worked hard to make that second number as small as possible.

We also built a fully managed SaaS option for teams that do not want to handle infrastructure. Same software, same capabilities — just hosted and maintained by us. The point is that the choice belongs to you.

How we build

From the beginning, we made decisions that favored longevity over speed. We chose proven protocols for device communication. We kept the architecture modular so that individual components — the map renderer, the alert engine, the reporting layer — could evolve without disrupting the rest. We wrote documentation before we wrote marketing pages.

We ship in small increments and we listen more than we talk. Our roadmap is shaped by the people who use Open VTS every day: fleet coordinators, logistics managers, security teams, field service operators. Their workflows are the specification. Their constraints are the design brief.

Who this is for

Open VTS serves organizations that take their fleet operations seriously. That includes logistics companies moving freight across borders, municipal governments tracking public vehicles, security firms monitoring patrol routes, construction companies coordinating heavy equipment, and delivery services optimizing last-mile operations.

Our users range from ten-vehicle operations in a single city to multi-thousand-vehicle fleets spread across countries. What they share is a preference for tools that respect their intelligence, their data, and their budgets.

Where we are now

Open VTS is live, stable, and handling real workloads for real fleets. We support a wide range of GPS tracking devices across major protocols. Our platform runs on modest hardware and scales cleanly as fleet sizes grow. The documentation is comprehensive, the API is well-defined, and the deployment process is straightforward.

We are a small team. We are deliberately small. Every person working on Open VTS talks to users, reads support threads, and ships code. There are no layers between the people who build the product and the people who use it. We intend to keep it that way for as long as we can.