Open VTS vehicle tracking software logo

Product

Your Infrastructure. Your Fleet Data. Your Rules.

Open VTS is a self-hosted GPS fleet platform you deploy on your own servers. It processes raw device data from 200+ tracker models into live maps, route replay, geofence automation, fleet analytics, and a documented API — with zero per-vehicle fees, full source access, and no third-party data dependencies.

Who this is for

CTOs, IT directors, and operations leaders evaluating self-hosted GPS platforms — teams that need data sovereignty, source-level control, and the ability to scale thousands of vehicles without per-unit SaaS pricing.

What this is

The self-hosted GPS platform you deploy, own, and control

Positioning

What Self-Hosted Tracking Actually Means

01

The platform layer

Open VTS is server-side tracking infrastructure. It accepts raw GPS packets over Teltonika, GT06, OSMAND, H02, and other standard protocols, normalizes them into structured fleet data, and exposes that data through real-time maps, geofence engines, alert pipelines, analytics aggregations, and a documented REST API — all running on hardware under your control.

02

The infrastructure problem

SaaS tracking platforms host your fleet data on shared infrastructure, charge per vehicle per month, and restrict API access to paid tiers. When you need a custom integration, a bulk data export, or a compliance audit trail, you are negotiating with a vendor instead of querying your own database. The platform that holds your fleet intelligence is not your asset — it is their subscription.

03

The ownership model

You receive the source code, your own PostgreSQL database, and a Docker deployment that runs anywhere — bare metal, private cloud, or hybrid infrastructure. There are no per-vehicle charges, no API call limits, no vendor-held data, and no contractual dependency on a third party's infrastructure decisions. The platform is yours. Modify it, extend it, white-label it for your own clients, or integrate it into your existing operations stack.

Capabilities

Core Operational Capabilities

Real-Time GPS Tracking

Sub-second position updates from 200+ compatible GPS devices rendered on live fleet maps. Vehicle status, speed, heading, and ignition state stream continuously to the platform. Cluster views handle thousands of assets without degrading interface responsiveness.

02

Route Replay & Trip History

Reconstruct any vehicle's journey with minute-level precision. Filter by date range, geofence intersection, or idle duration. Overlay speed profiles, stop patterns, and deviation from planned routes. Export complete trip data for external BI tools or regulatory submissions.

03

Geofence Engine & Zone Automation

Define polygon, circular, or corridor geofences around job sites, depots, customer locations, or restricted zones. Trigger server-side events on entry, exit, or dwell-time thresholds. Chain geofence events into webhooks and downstream automation without writing custom code.

04

Alert & Notification Pipeline

Configurable alerts for speeding, unauthorized movement, geofence violations, excessive idle time, low battery, and device disconnect. Alerts route to specific users by role, push to mobile applications, and fire webhooks for ingestion by dispatch or compliance systems.

05

Fleet Analytics & Scheduled Reporting

Aggregated utilization rates, idle breakdowns, distance summaries, fuel-consumption estimates, and trip-count metrics computed server-side. Schedule automated PDF or CSV reports for stakeholders, or pull any metric via the REST API for custom dashboards.

06

Multi-Tenant Architecture

Partition a single deployment into isolated tenant spaces — each with independent vehicle data, user access policies, branding, and reporting. Designed for GPS tracking providers, fleet management companies, and enterprises managing multiple business units on one infrastructure.

07

REST API & Webhook Integration Layer

Every operational data point — vehicles, trips, geofences, alerts, tenants — is accessible through documented REST endpoints. Webhooks push events to your ERP, TMS, dispatch system, or any HTTP receiver. Build bi-directional data flows without rate limits or metered billing.

Ownership Advantage

Why Ownership Beats Subscription

Every fleet tracking decision comes down to a structural question: who controls the infrastructure your operations depend on? Here is how ownership changes the equation.

Typical SaaSOpen VTS
Fleet data

Stored on the vendor's shared database. You get exports — they keep the original.

Stored in your PostgreSQL database, on your servers. No third-party copies exist.

Per-vehicle cost

$15–$40 per vehicle per month. Costs scale linearly with fleet size.

One-time license. Add vehicles without incremental cost. Zero recurring per-unit fees.

API access

Rate-limited, metered, or gated behind premium tiers.

Unrestricted. Every data point accessible at whatever frequency your integrations require.

Custom integrations

Limited to vendor-provided connectors. Custom work requires vendor engagement.

Full source access. Build protocol adapters, analytics modules, or ERP bridges yourself.

Hosting control

Vendor chooses datacenter, uptime SLA, and migration terms.

Run on any Linux host — AWS, Azure, Hetzner, on-premise. Move Docker containers, not contracts.

Scaling path

Each added vehicle increases monthly spend. Bulk discounts still compound.

Same deployment serves 50 or 5,000 vehicles. Scaling cost is infrastructure only.

Use Cases

How Serious Operators Deploy the Platform

01

On-Premise Fleet Intelligence

Organizations with data-sovereignty requirements deploy Open VTS on internal servers, keeping every GPS packet within their network perimeter. Fleet intelligence stays inside the building — no third-party cloud dependency, no external data exposure.

02

Geofence-Driven Operations Automation

A delivery vehicle enters a loading dock geofence — a webhook fires to the dispatch system, updating the status board. It exceeds the dwell-time threshold — a compliance ticket generates automatically. Geofence logic becomes part of the operational pipeline, not a monitoring afterthought.

03

Historical Route Auditing & Dispute Resolution

An insurance claim requires proof of route compliance. A customer disputes a delivery timeline. A regulatory audit demands trip records for a specific corridor. Pull exact vehicle paths by date, vehicle, or geofence intersection — directly from your database, on your terms.

04

Enterprise System Integration (ERP, TMS, BI)

Push vehicle location events, trip completions, and geofence crossings into SAP, Oracle, or custom TMS using the webhook layer. Feed fleet metrics into Power BI, Tableau, or Grafana through the REST API. No vendor-gated connectors — build what your architecture requires.

05

White-Label Fleet Tracking for Resellers

GPS tracking providers and fleet SaaS companies stand up branded portals for their own customers. Each client gets an isolated tenant with independent data, access controls, and branded interfaces — all running on a single Open VTS deployment under your management.

Outcomes

What Changes When You Own the Stack

Architectural Data Sovereignty

Fleet data lives in your PostgreSQL database, on your servers, under your backup and retention policies. No shared tenancy, no vendor read-access, no third-party copies of your operational intelligence.

Predictable Capital Economics

One-time licensing replaces compounding per-vehicle SaaS invoices. Your ongoing costs are infrastructure hosting and optional support renewal — both under your direct control and visible before you commit.

Source-Level Extensibility

Access and modify every line of server code. Build custom protocol adapters, analytics modules, reporting pipelines, or integration layers that no commercial SaaS vendor will ever prioritize on their roadmap.

Infrastructure-Provider Independence

Run on bare metal, private cloud, or hybrid infrastructure. Migrate between hosting providers by moving Docker containers — not by renegotiating vendor contracts or waiting for data-export approvals.

Unrestricted Integration Throughput

No API rate limits, no metered billing per call, no premium tiers for webhook access. Consume every data point your hardware generates at whatever frequency your downstream systems demand.

FAQ

Common Questions About the Platform

6questions

A Linux host with 4+ GB RAM, 2+ CPU cores, and Docker installed. This runs comfortably on AWS EC2, Azure VMs, Hetzner, DigitalOcean, or on-premise hardware. Larger fleets (1,000+ vehicles) benefit from 8+ GB RAM and SSD-backed storage for the PostgreSQL database.

Open VTS supports 200+ models from Teltonika, Queclink, Concox, CalAmp, Ruptela, and others transmitting over GT06, Teltonika, OSMAND, and H02 protocols. The full compatibility list is maintained on the Supported Devices page.

SaaS platforms typically charge $15–$40 per vehicle per month — a 200-vehicle fleet costs $3,000–$8,000/month. Open VTS charges a one-time license fee starting at $0 for up to 50 vehicles, scaling to $6,990 for unlimited vehicles. There are no recurring per-vehicle charges.

Yes. The REST API provides full read/write access to vehicles, trips, geofences, and alerts. Webhooks push events to any HTTP endpoint in near-real-time. Common integrations include SAP, Oracle TMS, Power BI, Tableau, Grafana, and custom dispatch systems.

Yes. A single deployment hosts multiple tenants, each with isolated vehicle data, independent user access controls, custom branding, and separate reporting. This is the architecture used by GPS tracking providers and fleet management companies serving their own client base.

Year 1 includes deployment assistance, bug fixes, and platform updates. From Year 2, optional support renewal is 18–22% of the original license fee and covers continued updates and priority assistance. Community documentation and forums remain free regardless.

Next Step

Ready to Own Your Tracking Infrastructure?

Deploy Open VTS on your servers. One-time licensing, full source access, zero per-vehicle fees. No vendor lock-in.