About CargoScanner

A platform for containers and general cargo — rates by container type, equipment availability, depot and routing detail, and tracking that survives a transshipment.

We are pre-launch, and this page says so rather than pretending otherwise. CargoScanner has no line integration, no rate feed and no tracking source. There is no customer count to quote and no coverage map to show, so you will not find either one on this site.

The problem

Moving a container is a series of separate questions answered by separate people. What does the box cost on this lane, this month, for this commodity? Is the equipment I need actually free at that depot, or only on paper? Which routing is one leg and which is three? And once it moves, where is it — not according to the booking, but according to the last real event?

Each of those has an answer somewhere. None of them is in the same place, in the same format, at the same time. That is the gap CargoScanner is being built to close.

How we will talk about it

This app is one of a family of logistics products built from a shared template, and the template arrived with a marketing homepage full of numbers nobody had measured — carrier counts, country counts, a search latency, a customer base. All of it was removed, and the rule that replaced it is short:

  • A number on a public page is derived from a registry or a measurement, or it is not there.
  • Derived counts round down, never up.
  • Anything unbuilt is labelled unbuilt, in the future tense.
  • The status page reports what is monitored and admits what is not. It never defaults to green.
  • Every link goes somewhere. A test fetches them all and fails the build on a 404.

Where the build is

Brand, theme and layout

Accent ramp, shared design system, application shell.

Done

Honest public surface

Home, about, status and legal — no claim without a measurement behind it.

Done

Authentication

Basefyio identity over RS256 tokens verified against the realm on every request. Built and tested; deliberately not open yet — see below.

Done

Reference data

Container type codes (ISO 6346, via DCSA), SMDG line codes and the SMDG terminal list — generated from public sources, searchable on the site and at /api/v1/cargo.

Done

Schema and persistence

Numbered migrations for the account anchor, containers, bookings, quotes and tracking events. No in-memory store. This is what sign-up is waiting on.

In progress

Container rates and tracking

Needs a line or depot data source, which is a commercial decision, not a coding one.

Later

Booking and billing

Follows persistence and a payment provider decision.

Later

Why you cannot sign up yet

Authentication is finished, not stubbed. Sign-in, sign-up and token refresh all talk to our identity provider, and every request verifies the token's signature against the provider's published keys before reading anything out of it.

What is missing is one database table — the row that records that an account exists in this app. Without it, signing up would create an identity we could never recognise afterwards: you would get a confirmation email, a password in your manager, and a permanent sign-in failure. So the gate stays shut until the schema lands. The status page checks that table on every load and reports exactly what it finds.

Getting in touch

There is no support desk yet, because there is no product to support. When accounts open, this section will carry a real address for a real inbox — not a form that posts into nothing.