Build telematics for fleets, apps, and agents

    One platform underneath it all — from devices and OEM feeds to SQL and MCP.

    Navixy connects devices and cloud data through IoT Logic, with fleet tracking, IoT Query analytics and mobile events.
    Foxconn
    Shopee
    Nestlé
    Amazon
    DHL
    Toyota
    Xerox
    Foxconn
    Shopee
    Nestlé
    Amazon
    DHL
    Toyota
    Xerox

    1,000,000+ assets on the platform

    THE NAVIXY PLATFORM

    Fleet and asset intelligence. Built around your business.

    Track vehicles and assets, automate operations, and turn telemetry into better decisions.

    • Visibility

      See what’s happening

      Know where vehicles, assets and teams are, and spot events that need attention.

      Location Intelligence
    • Automation

      Automate everyday work

      Turn incoming data into alerts and workflows that fit your operation.

      IoT Logic
    • Insight

      Understand performance

      Understand utilization, investigate costs and find opportunities in live and historical data.

      IoT Query

    Use ready-made applications, launch under your brand, or connect Navixy to your existing systems.

    What teams build on it

    Four kinds of product built on the same platform. Pick the one closest to yours.

    One map for everything that moves.

    The view a dispatcher works from, and the one your customers log in to see.

    • Live position and trip history
    • Geofences, POIs, and custom map layers
    • Two-way commands to the device
    Learn more
    One map for everything that moves.

    Point your agent at the platform

    An MCP server and Agent Gateway expose Navixy to AI agents. They read telemetry, assemble IoT Logic flows, and build reports on IoT Query — through the same API your team uses.

    An MCP client asks the server which tools it has, calls tracker_states, and gets back one record per tracker. Abridged, with illustrative values.

    Terminal
    Agent chat
    YOU
    Set up a dispatcher alert when a truck enters a geofence, and show fleet uptime by depot.
    AGENT
    Checked a week of telemetry. Assembled a flow: the dispatcher gets notified when a truck enters a geofence. And built a fleet uptime report by depot.
    PLATFORM
    30,412 rows · flow created · query executed
    Flow · IoT Logic
    flows/
    fuel-watch.json
    iot-logic/
    pipeline.ts
    queries/
    The exact flow the agent assembled and verified in chat.
    // geofence-alert.json
    {
      "trigger": "geofence.enter",
      "filter": "vehicle.type == 'truck'",
      "action": "notify.dispatcher"
    }
    The report the agent built on IoT Query SQL panels.
    -- fleet-uptime.sql
    SELECT depot,
           avg(engine_hours / period_hours) AS uptime
    FROM telemetry.daily
    WHERE vehicle_type = 'truck'
    GROUP BY depot
    ORDER BY uptime DESC;
    North Depot98.2%
    Central97.4%
    South95.1%
    Verified in these clients. Any MCP client that supports Streamable HTTP or SSE with OAuth can connect.

    Hardware changes. Your product doesn't.

    When a new device or protocol ships, we add support on our side. Your schema and code stay the same.

    Devices

    • Vehicle trackers
    • Asset and personal trackers
    • Cameras and dashcams
    • Sensors and peripherals
    • Industrial IoT
    • Gateways

    OEM and external systems

    • Factory OEM feeds
    • ELD
    • Telematics platforms
    • Video platforms
    • Cloud IoT platforms

    Staff

    • Field workers' smartphones

    Decode & normalize

    protocols · networks · formats

    Normalized record

    message_time
    2026-07-31T14:02:11Z
    device_id
    857378374927451
    location.latitude
    41.843207
    location.longitude
    -87.663548
    location.speed
    62km/h
    fuel_level_1
    71fuel sensor 1
    hardware_key
    D-2841driver key
    event_id
    241harsh braking

    Everything in the interface is available through the API.

    Draw a zone in the interface. Query it through the API. Both work on the same objects — Navixy handles the location logic, so your backend doesn’t have to.

    Warehouse 4

    Circle · 150 m radius

    In zone since 14:02

    POST/v2/zone/search_location
    Authorization: NVX <api-key>

    { "location": { "lat": 41.843207,
                    "lng": -87.663548 } }

    200 OK

    { "success": true,
      "list": [ { "id": 4062,
                  "label": "Warehouse 4" } ] }

    The companies who build with Navixy

    The brand, the pricing, and the customer relationship stay yours. We look after the infrastructure underneath — and we don't compete for your customers.

    1,200+

    telematics providers on the platform

    30,000+

    projects delivered since 2005

    130+

    countries

    98%

    support satisfaction

    99.9%

    platform uptime

    Anthony, CEO and Co-founder
    Track-n-Route
    “Navixy gives us flexibility and robustness to provide a complete all-in-one solution to any business, regardless of their sphere and location.”
    Bodo Erken, CEO
    Trackerrando
    “We have been offering Navixy as a solution to our customers for over 5 years. The associated advantages such as user-friendliness, stability and fast service response are the guarantee of our success.”
    Danny, Chief Technical Officer
    ThaiSoft
    “Our overall experience with Navixy has been great. The features and the support helped our company expand in many ways, and we look forward to working with them for years to come.”
    • SOC 2 Type II
    • GDPR and CCPA
    • TLS 1.2/1.3, AES-256
    • Data regions: US, EU, Saudi Arabia
    • Security & trust

    Extend the platform without waiting for us

    Ready-made apps from Navixy and partner developers, plus an SDK to build and publish your own. If a capability isn't in the core, that's not a dead end.

    Visit Marketplace

    What we're working on

    Engineering notes, protocol deep dives, and what we're learning from the field.

    Explore blog