IoT device gateway

GPS trackers, straight to Kafka

Wire connects tracker fleets to your data platform: TCP ingestion, Avro on Kafka and remote commands, with every device protocol as a plugin.

Why Wire

One hardened core for every device family.

Any protocol

Each vendor protocol is a separately versioned plugin.

Every frame kept

Raw frames are stored before decoding, rejects go to a DLQ, history can be replayed.

Bots stay out

Only identified, known devices are recorded and acknowledged.

Features

Protocol plugins

Discovered at runtime through Python entry points.

Hardened TCP

Framing, auto ACK, noise rejection, device allowlist, connection limits.

Raw vault + DLQ

Exact frame bytes and rejects with diagnostics, readable for any time window.

Kafka + Avro

Schema Registry, at-least-once: commit after every publish succeeds.

Scalable commands

Delivered by whichever replica holds the device, with reply correlation and retry.

Config presets

Read, check and apply device settings; only changed fields are sent.

Device Manager

Web UI and REST/WebSocket API, plus Web Serial for cable setup.

CLI

Commands over Kafka or serial, topics, raw dumps, live connections.

How it works

Each stage is a separate process that scales on its own.

  1. Trackers TCP / serial
  2. tcpserver identify, frame, ACK
  3. raw frames exact frame bytes
  4. reportdecoder decode + validate
  5. reports Avro records
  6. producer map to your contract
  7. Your topic e.g. a GPS data lake

Commands flow back the same way, with device replies published to Kafka.

Built on
  • Apache Kafka
  • Apache Avro

Device Manager

Configure and control your fleet from the browser.

  • Commands and presets for every protocol
  • Live raw log, DLQ and replies
  • Web Serial for devices on a cable
Wire Device Manager: command form for an AVT130 device

Integrations

Protocol plugins available today:

New device family? Add one ProtocolPlugin.

Contact

Tell us which trackers you run and where the data should go.