Gaugeworks · live telemetry

See the signal
before the story.

Gaugeworks turns raw instrument feeds into charts your whole floor reads the same way — ingested, deduplicated, and drawn in the same breath.

Signals per minute

streaming
Signals per minute: 14 points, from 31/min to 70/min
6363k
signals an hour
140140ms
ingest to chart

Gaugeworks · with receipts

Every mark brought a number.

Each of these agreed to publish a measurement, not just a logo. They chose which one.

  • NORTH BASIN

    7474

    minutes back per morning

  • KETTLE POINT

    9191%

    reshuffles not re-keyed

  • MILLRACE

    44

    yards on one record

  • DRY DOCK 2

    33×

    faster shift close

  • COLD STORE CO

    00

    missed sequence windows since May

  • TWO BRIDGES

    3838%

    fewer radio calls at shift change

Measured by the yard, not by us, over their own first six months. We publish whatever they send, including the flat ones.

Gaugeworks · the run ledger

The grid is the product. Sort it.

Forty-eight runs, virtualized, sortable, selectable to the whole set — the same ledger instrument your app would ship.

00OF 48 SELECTED

Crew
State

Gaugeworks · morning cut times

Every yard, and the direction it is heading.

The number is today. The line is the last eight mornings — which is where a yard tells you it is in trouble, well before the number does.

  • North basin

    Two crews · crane shared

    4141min to cut

    North basin, last 8 mornings: 8 points, from 41 min to 58 min

    clean

  • Kettle point

    One crew · tide-bound

    3333min to cut

    Kettle point, last 8 mornings: 8 points, from 33 min to 39 min

    clean

  • Relay floor

    Four crews · continuous

    7878min to cut

    Relay floor, last 8 mornings: 8 points, from 51 min to 78 min

    slow

  • Dry dock 2

    Project cargo · by exception

    2626min to cut

    Dry dock 2, last 8 mornings: 8 points, from 26 min to 31 min

    clean

  • Cold store

    One crew · sequence locked

    00min to cut

    Cold store, last 8 mornings: 8 points, from 0 min to 46 min

    failed

Gaugeworks · mornings cut, by trade

Watch the order change.

Three years of boards, by cargo type. Step through them and the ranking rearranges itself.

1
Container6,350 boards
2
Bulk4,610 boards
3
Project2,470 boards
4
Ro-ro2,020 boards
5
Cold880 boards

Container took the lead. Project cargo is now bigger than ro-ro was two years ago.

Gaugeworks · what actually moves

Which way the data goes.

Every connection below states its direction and its payload. If a row says two-way, both halves are live — we do not count a nightly export as an integration.

  • Terminal operating system

    System of record

    Two-way

    in
    Berths, moves, and holds, every 60s
    out
    Confirmed plan and crew assignment

  • Payroll

    Finance

    Writes only

    out
    Signed hours, per shift, once nightly

  • Weather service

    Conditions

    Reads only

    in
    Wind and swell for the planning window

  • Maintenance logbeta

    Assets

    Two-way

    in
    Crane and gear availability
    out
    Faults raised from the board

  • Identity provider

    Access

    Reads only

    in
    Who may sign a plan

Sync intervals are floors, not averages. Anything slower than stated is an incident, and you will hear about it from us first.

Gaugeworks · where it sits

Your data, by kind and by country.

One row per thing we hold. If a row says nobody, it means nobody — including us, without a ticket you opened.

  • Boards and plans

    Rests in · Frankfurt (eu-central)

    Kept · Indefinitely, yours to delete

    Seen by · Nobody

  • Crew names and shifts

    Rests in · Frankfurt (eu-central)

    Kept · 24 months after a yard closes

    Seen by · Nobody

  • Support attachments

    Rests in · Frankfurt (eu-central)

    Kept · 90 days

    Seen by · Support, on your ticket

  • Billing records

    Rests in · Ireland (eu-west)

    Kept · 7 years, by law

    Seen by · Payment processor

  • Error traces

    Rests in · Frankfurt (eu-central)

    Kept · 30 days

    Seen by · On-call engineer

Everyone we hand data to

  • Managed Postgres

    Primary store · EU

  • Object storage

    Exports and attachments · EU

  • Payment processor

    Billing only · EU / US

  • Email delivery

    Transactional mail · EU

Thirty days' notice before anything joins this list, by email, whether or not it affects you.

Gaugeworks · pricing

Measure your bill before it exists.

Set the caliper to the runs you expect this month. The bands are progressive — each span is priced at its own rate, so the average cost per run falls as volume grows.

Expected volume

40,00040,000runs / month

Monthly total

$115115

0k – 10k
0.4¢ / run
10k – 50k
0.25¢ / run
50k – 200k
0.12¢ / run
  • Every pipeline feature
  • Unlimited seats
  • 30-day run history
  • No charge for retries
No minimum

Gaugeworks · the part you are stuck on

You are probably thinking one of these.

“The crews will not use it.”
They use it or they do not — you will know inside a week, and the free yard costs you nothing if the answer is no.
“We tried something like this in 2019.”
Probably an office tool pointed at a yard. This one starts at the gate; if it does not survive gloves and glare, it has failed on its own terms.
“We do not have time to roll anything out.”
One yard, one afternoon, no migration. The whiteboard stays up as long as you want it to.
“What if we want out?”
Export everything whenever you like, keep the files, and stop paying from the settings page. No call, no retention offer.
or talk to someone who ran a shift