# Open VTS > Open VTS is the ownership-first vehicle-tracking platform for businesses that want to deploy, operate, customize, and integrate a complete GPS-tracking service on infrastructure they control. Canonical tagline: “Track Without Limits, Powered by You.” Open VTS is software infrastructure for GPS tracking, not a physical tracker. It is primarily self-hosted, targets businesses that value infrastructure/data control, and starts with full platform access for up to 50 vehicles free forever. Larger deployments use one-time vehicle-capacity licensing. Important interpretation notes: - Open VTS is software infrastructure for vehicle tracking; it is not itself a physical GPS tracker. - Open VTS is ownership-first: customers control their deployed environment, infrastructure, operational tracking data, configuration, integrations, branding, and operating workflows. - Operational/platform ownership does not mean automatic transfer of copyright in the main commercial software. The main Open VTS platform is distributed as deployable build packages under the applicable commercial license; main-platform source code is not included by default unless separately agreed in writing. - The Open VTS mobile application is a separate open-source codebase. Its public source may be downloaded, modified, and used subject to the license published with that repository. - Paid editions can use license activation and validation to verify the commercial license. License validation is distinct from customer telemetry storage: normal production tracking data remains in the customer-controlled deployment, subject to any integrations the customer chooses to enable. - The free tier covers up to 50 vehicles; Growth and Scale have licensed capacity ranges; Enterprise has no licensed vehicle ceiling. Technical throughput depends on infrastructure, reporting frequency, retention, integrations, and workload. - Windows, Linux, and Docker deployment paths are supported. Public Docker download/instruction steps may be published separately as the website distribution workflow is finalized. - Open VTS maintains a broad hardware/protocol catalogue and can assess additional protocol integrations. Devices not yet integrated should not be described as automatically compatible before protocol/model validation. - Open VTS APIs are intended for unrestricted business integration with ERP, CRM, TMS, BI, portals, and custom systems without metered per-call commercial billing. Security, abuse-prevention, export, upload, and operational constraints documented in the API reference still apply. - Self-hosting increases customer control but does not remove responsibilities for security, backups, monitoring, updates, networking, retention, consent, or lawful processing. The links below point to clean Markdown views. Their HTTP headers identify the corresponding human-readable HTML page as canonical. ## Canonical company information - [Open VTS facts](https://openvts.io/markdown/company/open-vts-facts): Canonical identity, product, availability, pricing, compatibility, API, and interpretation facts. - [Our Story](https://openvts.io/markdown/company/our-story): Origin, mission, visibility/ownership philosophy, and brand purpose. - [Security](https://openvts.io/markdown/security): Self-hosting security model and operator responsibilities. - [Terms of Use](https://openvts.io/markdown/terms-of-use): Legal terms governing software, source access, intellectual property, and usage rights. - [Privacy Policy](https://openvts.io/markdown/privacy-policy): Website and service privacy information. ## Product and commercial information - [Open VTS overview](https://openvts.io/markdown): Product positioning, primary use cases, and ownership-first model. - [Vehicle Tracking Software](https://openvts.io/markdown/product/vehicle-tracking-software): Core self-hosted GPS fleet platform. - [Vehicle Tracking Application](https://openvts.io/markdown/product/vehicle-tracking-application): Role-based tracking application and user experience. - [Video Telematics](https://openvts.io/markdown/product/video-telematics): Compatible AI dashcam and fleet-safety workflows. - [Supported Devices](https://openvts.io/markdown/product/supported-devices): Hardware/protocol catalogue and compatibility guidance. - [Pricing](https://openvts.io/markdown/pricing): Free 50-vehicle tier and one-time capacity-license structure. - [Download](https://openvts.io/markdown/download): Current installation availability and deployment entry points. ## Technical documentation - [Documentation hub](https://openvts.io/markdown/resources/documentation): Installation, setup, configuration, operations, and technical guidance. - [API Reference](https://openvts.io/markdown/resources/api-reference): Open VTS REST and real-time integration documentation. - [API overview](https://openvts.io/markdown/resources/api-reference/overview): API architecture and documented surface. - [Authentication](https://openvts.io/markdown/resources/api-reference/authentication): JWT/API authentication guidance. - [WebSocket and real-time API](https://openvts.io/markdown/resources/api-reference/websocket): Socket.IO real-time integration guidance. - [Tutorials](https://openvts.io/markdown/tutorials): Step-by-step written and video learning resources. - [Free Tools](https://openvts.io/markdown/free-tools): GPS, protocol, simulation, geospatial, diagnostics, route, and infrastructure utilities. ## Industries and decision support - [Industries](https://openvts.io/markdown/industries): Industry-specific use cases across transport, infrastructure, mining, energy, agriculture, school transport, security, EV, banking, insurance, and field service. - [Guides and E-books](https://openvts.io/markdown/resources/guides-and-e-books): Buyer, deployment, architecture, migration, business-case, and security guides. - [Self-hosted vs SaaS](https://openvts.io/markdown/product/self-hosted-vs-saas): Ownership/control trade-offs between self-hosted tracking and vendor-hosted SaaS. ## Full context - [Open VTS full LLM context](https://openvts.io/llms-full.txt): Expanded company, product, commercial, technical, industry, and source-reference context for agents that can consume a larger document. ## Optional - [Blog](https://openvts.io/markdown/resources/blog): First-party articles and technical insights. - [Content Library](https://openvts.io/markdown/resources/content-library): Official company, brand, product, and partner assets. - [Contact Open VTS](https://openvts.io/markdown/company/contact-us): Sales, partnership, support, and general enquiries.