Data sources of almost any shape
GPS trackers and IoT sensors, OEM vehicle APIs, CAN and OBD-II integrations, and raw protocol feeds over MQTT, HTTP/REST, WebSockets and TCP/UDP.
Components
Ecosystem
Navixy, distributed in Saudi Arabia by Smart Tracks.
The whole platformIoT Logic
Raw telematics arrives as numbered frames that mean nothing until something decodes, filters and routes them. IoT Logic is Navixy's no-code tool for exactly that work — assembled visually, changed in an afternoon.
GPS trackers and IoT sensors, OEM vehicle APIs, CAN and OBD-II integrations, and raw protocol feeds over MQTT, HTTP/REST, WebSockets and TCP/UDP.
Raw frames become named attributes you can read — the step that normally costs a firmware engineer and three weeks.
Conditions expressed visually and refined with expressions, so a rule like “fuel drops more than 40 litres while ignition is off” becomes a pipeline step, not a support ticket.
Fire an alert, call your own endpoint, or push a command back to the device — the automation runs on the platform, not in a script somebody has to babysit.
Deliver the finished stream to your own application, your BI stack, or a cloud platform such as AWS, Azure or Google Cloud.
When a manufacturer ships a model you want to sell, the pipeline is where you teach the platform to read it.
What it means for you
If you sell tracking, the bottleneck is rarely the map — it is the days lost every time a new device, sensor or customer rule needs custom work. IoT Logic moves that work out of your development queue and into a tool your support engineers can drive, which is the difference between quoting a new integration in weeks and quoting it in the meeting.