Skip to main content
CONPDS TRACKER

Integration Guide — Output Formats & Integration Paths

Tracker is subscription software. It publishes container numbers and size and type codes as JSON, for example over MQTT. Your developer subscribes and builds the workflow. This guide covers that hand-off, the other published paths, and where ConPDS Autogate is the alternative.

Open JSON · MQTT · REST API · Direct database · Any DMS / TOS / WMS

Open JSON Output via MQTT

Every confirmed recognition result is published as a JSON object, for example to the MQTT broker. The result includes the container number, the size and type code, the camera, the time, and the confidence. Any MQTT subscriber receives that result.
No proprietary format, no vendor lock-in. Any system that can subscribe to an MQTT topic can consume Tracker's output — a depot management system, terminal operating system, warehouse management system, a custom webhook, or a direct database write.
Recognition results published as JSON, for example over MQTT
Your developer subscribes and builds the workflow: a gate, a DMS or TOS update, an email notification, or an archive of the OCR pictures in a database or on a filesystem
REST and database paths on this page are examples, not a connector catalogue
If ConPDS builds that workflow, it is a separate engagement — not part of the Tracker subscription

Three Integration Paths — Standard Protocols, No Middleware

Path 01 · Primary

MQTT Subscription

Subscribe to MQTT topics per camera or camera group
Under suitable deployment conditions, up to 99% accuracy with processing as low as about 30ms before publication
Any MQTT client library in any programming language
Ideal for real-time gate automation, alert systems, and event-driven workflows
Path 02 · API

REST API Integration

Query OCR results via REST endpoints
Standard HTTP/JSON — integrates with any web service
Authentication via Certificate, API key, Basic Auth, or URL Auth
Ideal for polling-based integrations and dashboard systems
Path 03 · Database

Direct Database Integration

Write OCR results directly to your SQL or NoSQL database
No middleware layer required — Tracker writes to your schema
Suitable for facilities with existing database-driven workflows

On-Premise Infrastructure — Any Camera, Any Facility Size

Runs on your hardware — Windows 10+ / Linux Ubuntu 20+ — OCR and video stay on-premise; optional Checker cloud photo send when configured
Connects simultaneously to multiple concurrent IP camera RTSP streams — 5 at a small depot, 50 across a large terminal, same software throughout
Streams organised into camera groups — a group can represent a gate lane, a yard zone, a crane position, or any logical unit the facility defines
GPU-accelerated processing — Nvidia CUDA or Intel HD; processing capacity scales with hardware as camera count grows
Centralised OCR engine — update Tracker once and every connected camera stream benefits immediately, with no manual firmware upload or per-camera reconfiguration required
For full hardware and camera specifications, see the Tracker Technical Specifications.

What Do You Want to Build on Tracker's OCR Output?

Tracker publishes container numbers as open JSON via MQTT — what happens next is your choice. Two paths are available.

Open Platform · Any DMS · Any Workflow

Build Your Own Integration

Tracker's MQTT output is the data. Your developer subscribes and builds what happens next — a gate, a DMS or TOS update, an email notification, or an archive of the OCR pictures. REST and database paths below are examples. If ConPDS builds that workflow, it is a separate engagement, not part of the subscription.

Any MQTT Subscriber JSON published per camera or camera group — consumed by DMS, TOS, WMS, REST APIs, SQL databases, or any custom application.
No Management System Dependency Works independently of any DMS, TOS, or WMS — DepotMaster, EOS, AEMS, or systems you've built yourself. Integrate with whatever you run, or with nothing at all.
Custom Integration & Workflow Development Tracker's job ends at the MQTT publish — what happens next is business logic built on top of that data. ConPDS's team can help design and build custom integrations, routing rules, and automated workflows as a separate engagement.
Pre-Built Solution · DepotMaster Depots Only

ConPDS Autogate — Ready to Deploy

ConPDS Autogate is the complete gate automation programme built on Tracker — Autogate + Tracker + DepotMaster. ConPDS charges a one-time project fee for initial implementation and an annual per-gate subscription for supplied electronics, software, and ongoing support. Your local infrastructure contractor builds gate, kiosk, power, and network infrastructure to ConPDS specifications. Tracker's OCR output becomes barrier decisions and self-service driver interaction.

Requires DepotMaster. Autogate is not an OCR layer for whichever DMS you already run — depots not already on DepotMaster migrate as part of the programme. If your operation uses a different DMS, the open platform path on the left is your starting point.
ConPDS owns the automation outcome Project fee for initial deployment and commissioning; recurring subscription per gate for supplied electronics, software, and ongoing support.
Observed at live deployments Gate events that previously took several minutes now complete in seconds — from truck approaching cameras to barrier opening on a confirmed DepotMaster match.
See ConPDS Autogate →
Customers across Europe, Africa, Australia & the Middle East
Alisan Den Hartogh Aktas APM Terminals Autamarocchi CCIS Contrepair Cut Coal Eimskip Eurobox Gruppospinelli HRS Isotank Central James Group International Medlog Namops Logistics Porpet QTerminals Kramer Rotterdam Rhespa Europe SDT Marine & Cargo Washmed Werra Kombi Terminal Zuidnatie Zwennis Containers
Read real customer outcomes →

Ready to Integrate ConPDS Tracker?

Tell us about your current systems, integration requirements, and what you want to build on Tracker's OCR output — we will provide a tailored integration plan and answer technical questions within one business day.

Read the technical specifications →
No obligations — reply within 1 business day

Related Resources

ConPDS Tracker

Full product overview — how container OCR works, benefits, use cases, and the Tracker ecosystem.

explore the Tracker platform →

Tracker Technical Specifications

OCR performance benchmarks, camera requirements, hardware specifications, and on-premise architecture details.

see technical specifications →

ConPDS Autogate

Complete gate automation programme — ConPDS project fee plus annual per-gate subscription for supplied electronics, software, and ongoing support. Requires DepotMaster.

see the full gate solution →

Autogate System Architecture

Core gate components, GPU server specifications, and every software microservice deployed at each automated container gate.

see the Autogate architecture →

What Is Container Operational Evidence?

The complete category overview — what it is, how it works, and how it integrates with OCR and depot systems.

Read the platform overview →