Product
Your Infrastructure. Your Fleet Data. Your Rules.
Open VTS is an ownership-first, self-hosted GPS fleet platform you deploy on infrastructure you control. Its catalogue covers 1,639+ devices across 260+ protocols and 269+ brands, turning telemetry into live maps, route replay, geofence automation, fleet analytics, and documented APIs — without recurring per-vehicle license fees inside the purchased tier.
Who this is for
CTOs, IT directors, and operations leaders evaluating self-hosted GPS platforms — teams that need data sovereignty, deployment control, open integration options, and the ability to scale large fleets 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
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.
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.
The ownership model
You deploy the Open VTS build, database, and supporting services on infrastructure you control, including Windows, Linux, and Docker-based environments. The ownership model centers on control of your deployment, operational data, configuration, integrations, branding, and business workflows. The main platform is licensed build software rather than an automatic source-code transfer; the mobile application source is separately public/open-source under its repository license. APIs are available for ERP, CRM, TMS, BI, portals, and custom integrations without metered per-call commercial billing, while documented security and operational constraints still apply.
Capabilities
Core Operational Capabilities
Real-Time GPS Tracking
Real-time position updates from a catalogue of 1,639+ devices across 260+ protocols, subject to model, firmware, reporting interval, and network conditions. Vehicle status, speed, heading, ignition, and supported telemetry stream to live fleet maps.
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.
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.
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.
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.
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.
REST API & Webhook Integration Layer
Use documented REST endpoints, Socket.IO/SSE where documented, and webhooks to connect ERP, CRM, TMS, BI, dispatch portals, and custom systems. Open VTS does not meter integrations by API call as a commercial pricing model; security, abuse-prevention, export, upload, and operational constraints in the API reference still apply.
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.
Stored on the vendor's shared database. You get exports — they keep the original.
Stored in your customer-controlled PostgreSQL environment under your access and retention policies. Customer-selected third-party services only process data where you configure them.
$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.
Rate-limited, metered, or gated behind premium tiers.
Open integration model: use the documented APIs with ERP, CRM, TMS, BI, portals, and custom systems without metered per-call commercial billing. Documented security and operational constraints still apply.
Limited to vendor-provided connectors. Custom work requires vendor engagement.
Documented APIs, webhooks, configuration, and extensibility support custom ERP/CRM/TMS/BI workflows. The public mobile application source can be modified under its repository license; main-platform source is not included by default.
Vendor chooses datacenter, uptime SLA, and migration terms.
Run on customer-controlled Windows, Linux, or Docker-based infrastructure across cloud, dedicated, private, or on-premise environments.
Each added vehicle increases monthly spend. Bulk discounts still compound.
Enterprise licensing removes the vehicle ceiling; technical capacity then scales with compute, storage, reporting frequency, retention, integrations, and workload.
Stored on the vendor's shared database. You get exports — they keep the original.
Stored in your customer-controlled PostgreSQL environment under your access and retention policies. Customer-selected third-party services only process data where you configure them.
$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.
Rate-limited, metered, or gated behind premium tiers.
Open integration model: use the documented APIs with ERP, CRM, TMS, BI, portals, and custom systems without metered per-call commercial billing. Documented security and operational constraints still apply.
Limited to vendor-provided connectors. Custom work requires vendor engagement.
Documented APIs, webhooks, configuration, and extensibility support custom ERP/CRM/TMS/BI workflows. The public mobile application source can be modified under its repository license; main-platform source is not included by default.
Vendor chooses datacenter, uptime SLA, and migration terms.
Run on customer-controlled Windows, Linux, or Docker-based infrastructure across cloud, dedicated, private, or on-premise environments.
Each added vehicle increases monthly spend. Bulk discounts still compound.
Enterprise licensing removes the vehicle ceiling; technical capacity then scales with compute, storage, reporting frequency, retention, integrations, and workload.
Use Cases
How Serious Operators Deploy the Platform
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.
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.
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.
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.
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
In the standard self-hosted model, fleet telemetry is stored in your customer-controlled database and infrastructure under your access, backup, and retention policies. Customer-selected hosting, maps, messaging, payment services, and integrations may process relevant data where configured.
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
Extend the platform through documented APIs, webhooks, configuration, branding, and supported integration work. The Open VTS mobile application source is publicly available for modification under its repository license; the main platform is delivered as licensed deployable builds unless separately agreed.
Infrastructure-Provider Independence
Run on bare metal, cloud, private infrastructure, or Docker-based environments you control. The architecture is designed so infrastructure and operational data remain under the operator's control rather than tied to a shared SaaS tenancy.
Unrestricted Integration Throughput
No metered API-call billing and no premium integration tier for ordinary documented API/webhook access. Integrate with ERP, CRM, TMS, BI, portals, and custom systems; documented security, validation, export, upload, and abuse-prevention constraints still apply.
FAQ
Common Questions About the Platform
6questionsOpen VTS supports customer-controlled Windows, Linux, and Docker-based deployment paths. A typical evaluation/small deployment starts around 2 vCPU, 4 GB RAM, and SSD storage; production sizing depends on vehicle count, reporting frequency, retention, sensors, users, reports, and integrations. Representative load testing is recommended for large deployments.
The current Supported Devices catalogue contains 1,639+ devices across 260+ protocols and 269+ brands. Exact fields and commands depend on model, firmware, and protocol. If a required protocol is not yet integrated, Open VTS can assess an additional protocol integration rather than forcing customers into a single hardware ecosystem.
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 infrastructure you control. One-time licensing, customer-controlled data and operations, open integration surfaces, and no recurring per-vehicle license fees within your tier.