For recruiters
Shows end-to-end ownership: scraping, CSV design, validation, CI, dashboard polish and clear documentation.
Executive case
Built Like A Small Intelligence Product
The repo shows more than research notes: it demonstrates structured data modeling, source discipline, automation, validation, visual storytelling and commercial thinking in one compact project.
For managers
Turns noisy public information into a practical view of markets, systems, risk and opportunity.
For commercial teams
Identifies likely buyer pain around customs, yard visibility, terminal orchestration and API readiness.
Dataset
Research Coverage
A curated evidence base for understanding who operates in Zeebrugge, what systems are publicly visible and where software opportunities are likely to sit.
Signals are deliberately conservative: observed facts are separated from inferred operational stack needs, which keeps the analysis credible for business conversations.
Signal dashboard
Research Shape At A Glance
Four compact views show how the dataset is distributed by confidence, operating segment, evidence type and opportunity priority.
Confidence distribution
Segment breakdown
Terminals and RoRo
Intermodal and warehousing
Forwarding and customs
Port/data and energy
Observed vs inferred
Observed
Mixed
Inferred
Port-community systems are strongest; operational stack signals need field validation.
Opportunity priority
Yard visibility
Customs automation
ETA forecasting
Sales intelligence
API readiness
Technology signals
Where The Digital Layer Is Visible
The strongest evidence sits at the ecosystem layer, where port-community platforms, terminal workflows and customs tooling create repeatable software needs.
Port community systems
APICS, ZEDIS, NxtPort/RX-SeaPort, and IRP are the strongest verified ecosystem signals.
Terminal operations
Automotive, RoRo, and container operators likely depend on TOS, YMS, gate systems, EDI, and customer visibility.
Intermodal logistics
UK/Ireland flows create recurring needs around customs, rail planning, trailer visibility, and warehouse coordination.
Data interoperability
Clean APIs and event data are becoming a practical differentiator for shippers and logistics-tech vendors.
Drupal
Next.js
React
WordPress
Cloudflare
Google Tag Manager
Cookiebot
OneTrust
Firecrawl expansion
More Scraped Evidence, Better Stack Signals
Firecrawl search+scrape runs expanded the evidence base with official Zeebrugge pages, route-network pages, vacancy signals and terminal-system descriptions.
Terminal visibility
ETA Terminal Tool evidence now ties CSP Zeebrugge into arrival visibility, cargo-opening windows and API integration via NxtPort.
IRP integration
Inbound Release Platform evidence points to customs software integrations and Zeebrugge early-mover testing with terminal operators.
ECS in-house stack
The ECS software-developer vacancy names .NET, Angular, MS SQL Server, Azure, Docker, Kubernetes, EDA and DDD.
UECC VDTMS
UECC publicly names real-time tracking, web-based tracking, OEM integrations and a Vehicle Distribution and Terminal Management System.
CSP Navis N4
MarineLink/Navis deployment evidence upgrades CSP Zeebrugge from generic TOS inference to observed Navis N4 / Kaleris N4 evidence.
Full tech-stack view
All Stack Tags In One Place
A clean overview of the operational systems, port-community platforms, planning tools, analytics signals and visible web-channel technologies found or inferred in the research.
Observed port and data layer
APICS
ZEDIS
NxtPort
RX-SeaPort
IRP
Terminal API
APICA digital twin
Smart cameras
ETA Terminal Tool
Terminal, yard and transport systems
Navis N4
Kaleris N4
TOS
YMS
VMS
Expert Decking
PrimeRoute
Gate OCR
Crane/OCR options
Vehicle inventory
Trailer visibility
Slot booking
Rail planning
TMS
WMS
EDI/API
Customs, analytics and energy operations
Customs declaration software
Document automation
Release-status queues
Microsoft Analytics
Reporting Services
BI dashboards
Dwell-time models
ETA prediction
Demand forecasts
SCADA/OT
Nominations
Compliance reporting
Company engineering and terminal management
.NET
Angular
C#
MS SQL Server
TSQL
ASP.NET Core
Azure
Docker
Kubernetes
Event-driven architecture
Domain-driven design
VDTMS
Track-and-trace
Web-based tracking
OEM IT integration
Visible web-channel signals
Drupal
WordPress
Next.js
React
Vue
Cloudflare
Google Tag Manager
Google Analytics
Cookiebot
OneTrust
Bootstrap
jQuery
Commercial read
What A Manager Sees In One Minute
The portfolio value is the translation layer: raw public sources become target segments, system hypotheses, confidence labels and next actions.
Market shape
Zeebrugge clusters automotive, RoRo, UK-Ireland shortsea, containers, energy logistics, forwarding and customs work.
Buying triggers
Visibility gaps, release workflows, gate coordination, dwell time and integration friction point toward real software budgets.
Execution proof
The repo ships with validation, CI, visual smoke tests, reproducible scripts and source-linked datasets.
Company tech stacks
Every Company, Every Stack Signal
A company-by-company view combining observed platform evidence, inferred operational systems, visible website technology and hiring signals from the refreshed scrape.
Company
Observed / public signal
Inferred operational stack
Webtech and hiring signal
Port of Antwerp-Bruges
APICS, ZEDIS, ETA Terminal Tool, Terminal API, APICA digital twin, smart cameras, NxtPort, IRP
Port-community APIs, digital twin operations, event data sharing
Cloudflare, Drupal, Next.js, React, GTM, GA, Bootstrap
NxtPort / RX-SeaPort
NxtPort, RX-SeaPort, IRP, customs coordination
API/event platform, identity, permissions, partner connectors
WordPress, Vue; API/product/data roles to research
ECS / 2XL
Microsoft Analytics, Reporting Services, in-house apps, customer/supplier interfaces, .NET, Angular, MS SQL Server, Azure, Docker, Kubernetes
TMS, WMS, BI, rail planning, customer portals, customs integrations
Official vacancy confirms modern engineering stack, event-driven architecture and domain-driven design
NDQ Logistics
No named operational vendor
WMS, TMS, customs tooling, ferry integrations, customer visibility
WordPress, GTM, GA, Cookiebot, jQuery
International Car Operators
Customs/fiscal representation and digitalization signal
TOS, YMS, VMS, vehicle inventory, EDI/API, gate/camera systems, OEM portals
Drupal, GTM; terminal planning, IT and customs roles to research
Wallenius Wilhelmsen Zeebrugge
No specific Zeebrugge vendor in seed sources
Automotive terminal systems, global shipping EDI, customer visibility, yard management
GTM, Cookiebot; APZI cargo-handler board signal
MOSOLF Carcenter Zeebrugge
No named operational vendor
Vehicle inventory, VMS/YMS, damage inspection, OEM/customer portals, transport planning
WordPress, jQuery; PDI and yard roles to research
PSA Zeebrugge
No named operational vendor in seed source
TOS, EDI, rail/barge planning, yard/gate integrations, PCS integration
Cloudflare, Drupal, GTM, GA
CSP Zeebrugge Terminal
Navis N4 / Kaleris N4 TOS, Expert Decking, PrimeRoute, ZPMC cranes, VBS web app, TOS-connected apps, datawarehouse, BI tools, Java, JavaScript, Groovy, Python, CSS, HTML, SQL Oracle, Git
Container TOS, crane/OCR options, EDI/API, PCS integrations, terminal planning
WordPress, GTM, GA, jQuery; Navis N4 deployment plus IT Analyst Developer TOS/datawarehouse/BI signal
Fluxys LNG Terminal Zeebrugge
No named operational vendor in seed sources
SCADA/OT, nominations, scheduling, safety systems, compliance reporting, cybersecurity
React, GTM, GA, OneTrust, Bootstrap
Alltraco
AEO/customs capability
Customs declaration software, forwarding TMS, document management, customer communication tools
GTM, Bootstrap; customs declarant roles to research
Notman Logistics
No named operational vendor
Fleet planning, telematics, basic WMS, invoicing/accounting
Web scan failed with HTTP 503
Dens Ocean Shipping & Logistics
No named operational vendor
Forwarding TMS, shipping schedules, documentation, customs integrations
No visible webtech signal found
RBZ
No named operational vendor
Vessel agency software, port-call workflows, APICS/ZEDIS, documentation systems
Cloudflare, GTM, jQuery
Herfurth / M-Star Freight
No named operational vendor
Forwarding TMS, customs tooling, carrier EDI, customer portal
Vue, GTM, GA, jQuery
DFDS
Zeebrugge freight route evidence, no named operational vendor
Booking systems, EDI/API, trailer planning, driverless freight planning, customs workflows
React, GTM; Firecrawl confirms Zeebrugge-Gothenburg, Fredrikstad and Immingham route context
CLdN
Zeebrugge route network and CLdN RoRo platform evidence
Booking, RoRo terminal planning, EDI/API, Brexit/customs workflows
Next.js, React, GTM, GA, Cookiebot, OneTrust; Routescanner network evidence
C.RO Ports / C.RO Terminal
Routescanner lists C.RO Ports Zeebrugge terminal connections
RoRo TOS/YMS, gate OCR, EDI/API, customer integrations
Next.js, React, GTM, GA, Cookiebot, OneTrust
UECC
Technology-driven operations, real-time tracking, web tracking, OEM/customer IT integration, VDTMS
Automotive terminal software, voyage/vehicle visibility, EDI/API
Cloudflare, WordPress, GTM; strongest observed automotive terminal-management signal
KESS
No named operational vendor in seed sources
Shipping operations, automotive EDI, route planning, customer visibility
Bootstrap, Go Daddy Website Builder
Company stack matrix
Who Needs Which Systems
Segment
Examples
Likely systems
Confidence
Port authority and data layer
Port of Antwerp-Bruges, NxtPort / RX-SeaPort
APICS, ZEDIS, IRP, APIs, digital twin, smart cameras
High / medium
Automotive and RoRo terminals
ICO, Wallenius Wilhelmsen, MOSOLF, UECC, C.RO, KESS
TOS, YMS, vehicle inventory, gate OCR, EDI/API, OEM portals
Medium / low
Container and deepsea terminals
CSP Zeebrugge Terminal, PSA Zeebrugge
Container TOS, crane/OCR options, rail/barge planning, PCS integration
Medium
Intermodal and warehousing
ECS / 2XL, NDQ Logistics, DFDS, CLdN
TMS, WMS, BI, rail planning, ETA prediction, customs integrations
Medium / low
Forwarders, customs, agencies
Alltraco, Dens Ocean, RBZ, Herfurth / M-Star, Notman
Customs declaration software, freight TMS, document automation, APICS/ZEDIS workflows
Medium / low
Stack taxonomy
The Useful Layers To Track
Port community and data sharing
APICS, ZEDIS, NxtPort, RX-SeaPort, terminal APIs, event exchange, and permissions.
Customs and release
IRP, declarations, document automation, missing-document checks, and release status.
Terminal orchestration
TOS, YMS, gate OCR, camera integrations, vehicle inventory, and crane/OCR options.
Transport and warehouse planning
TMS, WMS, rail planning, slot booking, trailer visibility, and ETA prediction.
Analytics and forecasting
BI, dwell-time models, gate peaks, labor-demand estimates, and exception scoring.
Energy terminal operations
SCADA/OT, nominations, scheduling, safety systems, and compliance reporting.
Opportunity map
Software Ideas With A Buyer Lens
Each opportunity is framed from operational pain, buyer segment and go-to-market logic instead of being a generic feature list.
Yard visibility
Track dwell time, location, release status, and handover state for vehicles, trailers, and overflow capacity.
Customs automation
Build around IRP/NxtPort/RX-SeaPort instead of isolated document portals.
ETA and capacity forecasting
Connect vessel schedules, terminal events, gate peaks, and warehouse labor planning.
Sales intelligence
Score logistics companies by digital maturity, public tech signals, and likely pain points.
API/data readiness audit
Assess which operators can expose clean event data and where integration gaps block shippers.
Method
How The Signals Were Scored
The credibility comes from labeling what is observed, what is inferred and what still needs field validation.
Observed
A public source names the system, platform, product, or vendor directly.
Inferred
The stack is operationally likely from terminal, customs, warehouse, RoRo, rail, or forwarding activity, but no vendor is named.
Unknown
No reliable public signal was found. These entries need interviews, job-posting checks, vendor cases, or direct outreach.
Register sources in CSV with source type and notes.
Scrape text extracts with a dependency-free Python script.
Map companies to services, stack signals, confidence, and source IDs.
Validate structure locally and in GitHub Actions.