Skip to content
wendiq

Technology

  • Fleet data isolation
  • Read-only AI
  • REST API

Location data is sensitive and fleets never stop moving. Wendiq is a fleet telematics platform designed for both — layered, isolated per fleet and secure by default.

Request technical details

Wendiq is designed as a set of layers, from the device in the vehicle to the dashboard on your screen. Each layer can grow on its own as fleets and data volumes grow.

  1. L1

    Devices

    Trackers in the vehicle

    GPS tracking devices report location, ignition, speed and mileage. Wendiq works across device brands rather than locking you into one.

    • GPS trackers
    • Ignition & speed
    • Mileage
    • Multiple brands
  2. L2

    Ingestion

    Device data pipeline

    Device messages arrive securely, are checked and de-duplicated, and are matched to the right vehicle before anything else uses them.

    • Secure intake
    • De-duplication
    • Vehicle matching
    • Safe retries
  3. L3

    Core

    Fleet state engine

    Turns raw positions into trips, stops, idle time and vehicle status, and keeps a history that can't be rewritten.

    • Trips & stops
    • Vehicle status
    • Geofences
    • Trip history
  4. L4

    Intelligence

    Analytics & AI

    Utilisation, revenue, misuse and service models run over the fleet picture. The assistant answers from your data through read-only tools.

    • Utilisation
    • Revenue
    • Misuse
    • Service forecast
  5. L5

    Experience

    Web & mobile

    A clear dashboard for owners and managers, and focused mobile screens for branch teams at handover and return.

    • Live map
    • Dashboards
    • Alerts
    • Reports

Location data is sensitive. Wendiq is designed so each fleet's data stays separate, access is limited to the people who need it, and AI can read but never act.

Fleet data isolation

  • Every fleet's data kept separate from every other
  • Access checked on every request
  • Branch-level access for teams that run one location
  • Trip and audit history that can't be rewritten

Authentication

  • Strong password hashing and password rules
  • Multi-factor authentication
  • Short-lived sessions with secure refresh
  • Lockout and rate limits on sign-in

Access control

  • Roles for owners, managers, branches and finance
  • Administrators can't grant more access than they hold
  • Sensitive changes recorded in an audit log
  • Integration credentials encrypted at rest

AI guardrails

  • The assistant only uses read-only, permission-checked tools
  • It can't change bookings, contact customers or act on vehicles
  • Every answer shows the data it came from
  • Conversations are private to the user who asked

Each control listed here is implemented in the Wendiq codebase and covered by an automated test. Security documentation is available to customers on request.

Fleet data drives pricing, disputes and buying decisions, so it has to be right. These are the practices that keep Wendiq accurate, auditable and dependable.

01

Safe device retries

Device messages carry identifiers so repeats and late arrivals never double-count a trip.

02

History you can trust

Trips, positions and audit records are added, never rewritten — by design and by database permissions.

03

Observability built in

Structured logs, health checks and metrics for device traffic, queues and background jobs.

04

Time and money done right

Times stored in UTC and shown in Gulf Standard Time; money stored as exact decimals with a currency.

05

Tested controls

Security controls are covered by automated tests, so they stay in place as the product changes.

06

Typed and linted

Static type checking, linting and formatting run on every change alongside the test suite.

Start with the data you already have. Add readers, scanners and systems as your operation grows — Wendiq keeps one consistent picture underneath.

  • GPS tracking devices

    Location, ignition, speed and mileage from the trackers in your vehicles.

    At launch

  • Vehicle & booking import

    Load your fleet list and bookings from spreadsheets.

    At launch

  • REST API

    A versioned JSON API for vehicles, trips, utilisation and alerts.

    At launch

  • Alerts & webhooks

    Send alerts to email and the tools your teams already use.

    At launch

  • Reports & exports

    Utilisation, revenue, trip and service reports.

    At launch

  • Rental & booking systems

    Bookings and rates synced directly from your rental software.

    Planned

  • Tolls & fines

    Toll and traffic-fine records matched to the vehicle and the hire.

    Planned

  • Fuel cards & accounting

    Running costs and revenue flowing into finance.

    Planned
Wendiq REST API · v1
GET /api/v1/vehicles/utilisation?class=luxury-suvAuthorization: Bearer … 200 OK{  "vehicle": "Luxury SUV · D 48213",  "branch": "Business Bay",  "utilisation_30d": 0.41,  "idle_days": 6,  "insight": {    "type": "rebalance",    "suggestion": "Move to Marina branch for weekend demand"  },  "status": "awaiting_review"}

Illustrative request and response

We're happy to go through architecture, security, device data and integrations in detail with your technical leads.

Request technical detailsView the roadmap
  • Where is every vehicle?
  • How is it being used?
  • What is it earning?