Neutral platform logic
OTP is designed to make vehicle data available to authorized market participants instead of locking it into one app.
Company
OTP is owned by RideLink GmbH.
RideLink operates otp.systems and is one of the first customers of the platform. That makes OTP practical from day one: the platform is shaped by real mobility products, not by a theoretical architecture diagram.
Owner and first customer
RideLink brings the product reality.
RideLink GmbH owns OTP and uses the platform idea inside its own connected mobility ecosystem. This is important for partners: OTP is not a lab concept waiting for a first use case. It already has a product owner with direct market experience in telematics hardware, trip data and connected services.
WingMan Pro EVO becomes the hardware foundation for OTP Adapter 2. RideLink's experience with connected rider products and Caranea's automated driving-logbook use case both feed into the same platform thesis: reliable vehicle data should be reusable across services.
OwnerRideLink GmbH owns and operates otp.systems.
First customerRideLink is one of the first customers applying OTP in real mobility scenarios.
Hardware pathWingMan Pro EVO is positioned as the basis for OTP Adapter 2.
Platform pathOTP creates the backend and API layer for more than one product.
Why OTP exists
Vehicle data should not be trapped in closed product silos.
The original OTP idea was simple and still holds: vehicles need an open telematics layer similar to how smartphones needed app platforms. Not every service should have to build the same device, firmware, backend and permission stack again.
Works beyond new vehicles
The adapter approach extends connected-car capabilities to existing vehicles through the OBD II interface.
Built from product needs
RideLink's telematics work keeps OTP grounded in device reliability, trip capture, user value and partner integration.
Technology heritage
OTP builds on years of vehicle communication work.
The OTP materials describe patent applications and vehicle-communication concepts around adapter identity, vehicle identity, secure data routing, diagnostic access and decentralized communication. On the public site, this should be framed as technology heritage rather than as a legal status claim.
For partners, the important message is not paperwork. It is the shape of the system: adapter, backend, data permissions and application access designed as one platform.
Adapter identityThe device is a controlled gateway, not an anonymous modem.
Vehicle identityData is connected to the vehicle context and permission model.
Application authorizationServices consume data through controlled access instead of raw device channels.
Reusable infrastructureOne platform layer can support many product verticals.
Talk directly to the owner of OTP.
RideLink can discuss the platform, the adapter roadmap and where OTP fits into your product or partnership idea.