Berth planning, port-call documents and a data exchange for container terminals.

Drag a vessel. Quayside checks the tide window, LOA and crane availability while you do. Arrow keys move the focused vessel by 30 minutes; ↑↓ change berth.Time runs down, berths across. Tap a call to open it and move it by half-hours.

02

What it replaces

A spreadsheet, a whiteboard and about forty emails per shift.

Most terminals plan the quay in a spreadsheet one person understands, a whiteboard in the operations room and a run of emails between the planner, the agents and the pilot station. The plan is correct for about forty minutes. Then an ETA slips, a crane goes down or the tide table gets read wrong, and the corrections travel by phone.

TaskBeforeWith Quayside
Where the plan livesExcel on the planner’s laptop, a copy on the whiteboardOne plan, shared with the agents and the pilot station, versioned per change
Who finds an overlapThe foreman, on the morning ofThe planner, as the block is dragged
Tide checkPrinted table, checked by hand for deep callsComputed per berth and per movement from the station feed
ETA change reaches agents2–6 hours, by email and phoneUnder a minute, by IFTSAI message and webhook
Crane planSeparate sheet, reconciled at shift changeDemand against the pool per 30 minutes, on the same board
Audit trailNoneEvery move, by whom, with the checks it passed
03

Integrations

Protocols first. Quayside speaks what the port already speaks.

No terminal changes its message standards for a planning tool. Quayside receives and sends the formats agents, lines, pilots and port community systems already use, and stores every message with the plan it changed.

ProtocolDirectionCarriesCounterpartiesCadence
EDIFACT IFTSAIIn / outVessel schedule, ETA, ETD, berth requestLines, agentsOn change
EDIFACT BAPLIEInBay plan, container moves per callLines, stowage plannersPer call
EDIFACT COARRI / CODECOOutDischarge and load confirmation, gate movesLines, forwardersPer move
AIS (NMEA 0183)InPosition, SOG, draught, destinationTerminal receiver, VTS feed2–10 s
UN/LOCODEReferencePort and terminal identifiers (NLRTM, GBFXT, MYTPP)UNECE 2024-2Twice a year
Port Community SystemsIn / outPort-call notifications, berth allocation, pilot ordersPortbase, Destin8, Valenciaport PCS, Porto sem Papel, KenTradeOn change
Tide and weatherInPredicted and observed water level, windRijkswaterstaat, UKHO, national hydrographic offices10 min
REST / webhooksOutEvery plan change as JSON, signedTOS, gate, resource planning< 1 s
04

Customers

31 terminals in 14 countries. Stories.

  • Terminal Noordkade, Rotterdam
  • Felixstowe South
  • Tanjung Pelepas Berth 7–12
  • Valencia Levante Terminal
  • Santos Tecon 3
  • Mombasa Container Terminal 2
  • Port of Gdańsk DCT
  • Antwerp Deurganck

“We used to find berth overlaps on the day. Now the planner finds them on Tuesday for Thursday, and the agents get the new ETA before they have finished their coffee.”

Joris Hendriks, Operations Manager, Terminal Noordkade, Rotterdam

“The tide check alone paid for it. One deep call held for a window is a day of quay time. We have not held one since March 2024.”

Rachel Okafor, Senior Berth Planner, Felixstowe South
05

Numbers

Measured across all terminals, last twelve months to August 2026.

MeasureValueNote
Terminals live3114 countries, 6 time zones
Port calls planned per month41,000Across all boards, August 2026
Median time from conflict flagged to plan clean6 min 40 sPlanner action, not Auto-resolve
Conflicts found before the day of the call96.3%Was 41% on the spreadsheets we replaced
Uptime, last 12 months99.97%Status page
Messages exchanged per day1.9 MEDI, AIS, PCS and webhooks
ISO 270012023Certified, audited annually

See your own quay in Quayside. A demo takes forty minutes and uses your berth list, not ours.

Book a demo See pricing Terminal plans from €1,900 a month.