◫
Custom dashboards
Design your own gauges, warning zones, themes and layouts for street, track, towing, off-road or workshop use.
Custom automotive software
Turn an OBD adapter into your own car app.
We build custom Android, desktop and embedded applications around OBD‑II and CAN: digital dashboards, diagnostics, telemetry, macros, data logging, geofenced workflows and vehicle-specific tools.
Androidmobile apps
Windows + Linuxdesktop tools
BLE / BT / Wi‑Fiwireless adapters
USB / UARTworkshop & embedded
Cloud APIssync & fleet backends
What we can build
One adapter. Many products.
From a focused utility for one car to a branded fleet platform, the same vehicle data layer can power very different experiences.
⌁
Diagnostics assistant
Read DTCs, freeze frames, readiness monitors and live sensor data, then turn raw codes into a task-specific diagnostic flow.
⌁
Telemetry & logging
Record OBD/CAN data with GPS, accelerometer and timestamps. Export to CSV/JSON or sync it to your own backend.
⚡
Macros & workflows
Bundle repeatable actions: connect, query modules, capture a snapshot, tag a trip, export a report or launch a predefined diagnostic sequence.
⌖
Location automations
Use the phone or gateway location to trigger app behavior when the vehicle enters or leaves a geofence.
↗
Track & performance
Combine engine parameters with GPS and motion data for lap sessions, heat monitoring, shift cues and post-drive analysis.
▦
Fleet tools
Trip classification, mileage, driver workflows, maintenance signals and health snapshots across multiple vehicles.
◉
Workshop software
Build a focused desktop utility for intake scans, before/after reports, VIN capture, logging and repeatable service processes.
⌘
Vehicle-specific apps
Add OEM-specific parameters, CAN decoding or coding/service features when documentation, hardware and vehicle validation allow it.
Adapter coverage
Built as a driver layer, not a one-dongle app.
We can target the major adapter families and connection types used by consumer, enthusiast, workshop and embedded projects. Exact support is validated against the vehicle, operating system, firmware and required protocol.
Important: “ELM327 compatible” does not guarantee identical behavior. Low-cost clones can use incomplete command sets,
small buffers or unstable firmware. Generic clone support is therefore best-effort and tested per model.
Generic ELM327-compatible adapters
The broad compatibility layer for standard OBD‑II apps and many third-party dongles.
Bluetooth Classic • Bluetooth Low Energy • Wi‑Fi • USB serial • UART / embedded ELM command-set devices
OBDLink family
High-performance adapters with strong third-party app support and, on selected models, extended vehicle networks.
OBDLink MX+ • CX • LX • EX • SX / legacy OBDLink interfaces
Vgate / vLinker family
Popular ELM-style adapters across BLE, Bluetooth and USB variants.
Vgate iCar • iCar Pro • iCar Pro 2S • vLinker MC / MC+ • FS USB / FS BT • FD / FD+ • BM • MS BT and compatible variants
Veepeak OBDCheck family
Consumer BLE / Bluetooth adapters frequently used with Android OBD applications.
OBDCheck BLE • OBDCheck BLE+ • VP11 • VP01 and compatible ELM-style models
WiCAN / WiCAN PRO
Wi‑Fi/BLE CAN gateways suited to dashboards, logging, custom software and maker/embedded projects.
WiCAN • WiCAN PRO • TCP / UDP • BLE / Wi‑Fi • raw CAN-oriented workflows
STN-based interfaces
ELM327-compatible STN command-set hardware, including existing and legacy devices built around OBD Solutions interpreters.
STN1110 • STN1170 • STN2100 • STN2120-based hardware (legacy/discontinued ICs, still relevant in deployed devices)
Raw CAN / SocketCAN interfaces
For research, custom CAN decoding and advanced Linux/desktop integrations where standard OBD PIDs are not enough.
CANable / CANtact-class • SocketCAN USB adapters • MeatPi USB-Dual CAN / Ollie-class hardware • custom CAN bridges
SAE J2534 Pass‑Thru devices
Windows integrations can be built around J2534 when the adapter exposes a compliant vendor driver/API.
J2534-1 / vendor pass-through interfaces • OEM VCI devices with accessible SDKs • workshop-focused hardware
Custom / white-label hardware
If your product uses its own BLE service, UART protocol, CAN gateway or telematics box, we can build the app and protocol driver around it.
BLE GATT • TCP/UDP • USB CDC/serial • UART • custom CAN gateway • embedded Linux / ESP32-class devices
Rules & geofencing
Make the app react to context.
Location can come from the phone or a connected gateway. Combine it with ignition state, speed, temperature, DTCs, time and trip state to create useful workflows.
When
Vehicle enters the race track geofence
Phone location enters a saved area while the vehicle is connected.
If
Vehicle is stationary or session has not started
Safety guard prevents disruptive transitions while actively driving.
Then
Open Track Dashboard + start high-rate logging
Switch the UI, create a new session, record GPS + OBD/CAN telemetry.
After
Leaving the geofence, finish and sync the session
Generate a summary and upload it when the preferred network is available.
⌖ Track Zone · 1.2 km radius
Automation readyPerformance profile activated
Logging: GPS + RPM + coolant + throttle + speed
Workshop arrival
Entering a saved service location can prepare an intake flow, identify the vehicle and prompt for a health snapshot.
Home sync
When a completed trip reaches home, tag it, close the session and sync logs over Wi‑Fi.
Commute classification
Automatically tag trips between home and work for mileage reports without changing any vehicle settings.
Parking summary
At engine-off, save the last location, trip statistics and a compact vehicle-health snapshot.
Smart alerts
Combine thresholds such as coolant temperature, voltage or DTC appearance with trip state and location context.
Custom fleet zones
Mark depots, customer sites or restricted areas and use them to drive app workflows, reporting and notifications.
How a project works
From one idea to a tested vehicle workflow.
Define the job
Vehicle models, adapter, platform, data needed, user flow and whether the project is read-only or requires validated write operations.
Build the protocol layer
Connection management, adapter commands, PID/CAN parsing, retries, logging and a clean internal vehicle-data API.
Design the experience
Dashboards, rules, reports, workflows, alerts, cloud sync and brand-specific UI.
Validate on hardware
Test the exact adapter, firmware, OS and target vehicles. Gate unsupported commands and keep safety-sensitive writes explicit.
Start with a project brief
What should your car app do?
Choose a platform, adapter class and first use case. This demo form creates a brief you can copy into your preferred project or contact workflow.