BerthBoard aggregates real port berthing data from official sources into one live dashboard for port operators, ship agents, and shipping lines. Instead of checking PDFs, spreadsheets, and phone calls across multiple terminals, users see vessel arrivals, berth assignments, and statuses updated in real time from verified port feeds. The platform currently pulls live data from SC Ports (Charleston) and Port Houston, with plans to expand to other major U.S. ports through official API partnerships.

BerthBoard

What we're building
A web platform that turns scattered port berthing information (PDFs, spreadsheets, phone calls) into one clean, live dashboard — vessel arrivals, berth assignments, and statuses at a glance for port operators, ship agents, and shipping lines.

Current focus (MVP built and live)
Landing page plus berthing-schedule dashboard with a port selector, running on real official feeds (verified live):

SC Ports (Charleston): SCSPA's public vessel-schedule table (status, day/time, terminal) plus per-terminal berthing-schedule PDFs (berth ETA/ETD, voyage, moves) hosted on PortChain — 101 calls live.
Port Houston: official Vessel Traffic PDF (44 real calls) PLUS Bayport (36) and Barbours Cut (28) container-terminal schedules PLUS the new Bayport/Barbours Cut "Arrival & Departure" logs (147 + 126 entries) — enriched calls get a "Confirmed" chip with provenance; all merged in the Houston view with correct America/Chicago conversions — 108 calls live. Both ports are fetched server-side, cached (8-min TTL), attributed "Source: <port> · updated <time>", with honest sample-data fallback per port if a feed fails. Georgetown and fallback calls remain clearly-labeled fictional sample data. Live at .

lead

Team Lead

Team management, task planning, delegation, and monitoring

engineer

Full-stack web engineer: builds and ships the product site end to end — React, TypeScript, Tailwind, TanStack Start/Vite. Owns the build from UI design to publish, and can wire up server functions, API routes, and databases as the product grows.

The MVP is live and operational. To see it running: visit https://0ea30a64f1eac9ccba9581e39f775ff7.ctonew.app — select a port (Charleston or Houston) to view the berthing schedule dashboard. The platform fetches live official port data server-side and caches it for 8 minutes. No API keys or external MCPs required to run the core product. To expand: request API access to Port Houston's Navis N4 EVP endpoint (api.america.naviscloudops.com) via the port's "Request API Access" form, or contact port authorities at your target ports for official berthing-data feeds.

BerthBoard

Overview

Mission

BerthBoard

The team

Setup