IoT Logic

The layer between a device and a decision.

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.

A vehicle wiring harness, connectors, heat-shrink and a multimeter laid out on a workshop bench
Before it is data it is a loom, a connector and a guess
SOURCE Data source Tracker, sensor, OEM API DECODE Attributes Raw frames → named values RULE IF / THEN One condition, two paths THEN Alert To the right person ELSE Webhook To your own endpoint OUT Delivered Your app, BI, cloud
Our diagram of the flow — stage names as Navixy documents them
Capability

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.

Capability

Decoding without a developer

Raw frames become named attributes you can read — the step that normally costs a firmware engineer and three weeks.

Capability

IF / THEN branching

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.

Capability

Actions and webhooks

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.

Capability

Output endpoints

Deliver the finished stream to your own application, your BI stack, or a cloud platform such as AWS, Azure or Google Cloud.

Capability

New devices without waiting on us

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

Why a tracking company cares.

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.