Built for operations that cannot stop.

Yard, gate and equipment in one operational view: position, movement, throughput and exceptions, in real time, while the terminal is working.

NEVER STOPSThe gateTrucks in and outThe yardWhere the boxes sitThe cranesWhat moves themOne live pictureof every container,every move,and anything gone wrongand it is never switched offThe teamon shiftRunning right now.

No screenshot is published for this platform. It runs in a live terminal environment and we have no frame we can show that is both real and free of a client’s operational data. We will walk through it under NDA rather than publish a mockup of it.

Three pictures of one operation

The gate, the yard and the equipment have to agree with each other minute by minute. Tracked separately, the answer to where a container is depends on who you ask and how recently they looked.

There is no maintenance window. Ships arrive, gates move and equipment works around the clock, so the software has to be correct while all of that is happening rather than between shifts.

One operational view

Position, movement, throughput and exceptions across yard, gate and equipment, in real time and against one record. Coordination happens against one picture instead of three.

Correctness under continuous write pressure, with no quiet period to deploy into. Every release goes out while the operation is running, which means every release has to be reversible.

What it does today.

Everything listed is something the software does now. Nothing on this page is a roadmap item, and there is no roadmap on it either.

  1. Yard

    Where things are and where they are going, kept current while the yard is working.

  2. Gate

    Arrival and departure captured as events at the moment they happen rather than keyed in afterwards.

  3. Equipment

    Machines and moves coordinated against the same record the gate and the yard are reading.

  4. Cargo movement

    Position and movement tracked as a continuous record rather than as a series of snapshots.

  5. Exceptions

    The moves that did not go to plan surfaced as first-class work rather than found later in a report.

  6. Operational reporting

    Throughput and exceptions from the same record the operation is being run from.

  7. Integrations

    The systems and equipment already on site, treated as things that fail rather than as interfaces that return.

How it is put together.

Correctness under continuous write pressure is the whole engineering problem. Being right at rest is easy; being right while events arrive faster than anyone can observe them is what the architecture is for.

The architecture, the integration map and the data model are covered in technical review under NDA rather than on a public page. The shape of the system is described here; the detail is a conversation, not a download.

What actually gets attacked.

A terminal system’s worst outcome is not a breach, it is a stop. Availability dominates: releases are reversible, failure modes are designed for rather than discovered, and no change reaches production without a named person approving it who can be asked why.

Ownership, handover and AI governance covers what a procurement or security reviewer usually asks next.

Engagements built on this platform.

LogisticsLive container terminal

A container terminal operator

Real-time yard, gate and equipment visibility in one operational view, under continuous operational demand.

ChallengeYard, gate and equipment were three separate pictures of the same operation, and none of them was current.
ConstraintNo maintenance window. It has to stay correct while ships are moving.
StatusIn production

Technology

Backend
PythonDjangoFastAPINode.js
Data
PostgreSQLMySQLRedisData modelling
Cloud
AWSDockerCI/CDInfrastructure as code
Operations
Metrics and tracingAlertingLog aggregationRelease automation

Questions we get asked.

What buyers of this platform ask before a demo.

How do you deploy into a terminal with no maintenance window?

Reversibly. A release that cannot be rolled back is a commitment made on behalf of everybody downstream, and in a terminal that means on behalf of ships already alongside.

Why is there no screenshot?

Because every frame we have carries a client’s operational data, and the only alternative offered to us was a generated mockup. We would rather show nothing than show something that was never on a screen.

You do not need to arrive with a perfect technical specification.

Start with the problem. Tell us what is slowing the business down, what you want to build, or where the current system is failing. We will tell you the shortest path forward, including when that path is not us.

Start your build