Maritime intelligence platform
Smart Ship Broking — Maritime Data Platform
A high-volume maritime data service that makes vessel information, movement history, geographic searches, and export workflows usable from the main Smart Ship platform.
At the heart of Smart Ship Broking is a large-scale maritime dataset covering more than 170,000 vessels, over 2.4 billion recorded positions, and five years of movement history. The platform turns this volume of raw data into searchable vessel profiles, route insights, and geographic intelligence that brokers can use to understand activity and make better-informed decisions.
View final productsmartshipbroking.co.ukWhat the service enables
- 01Technical and operational vessel profiles together with movement history by IMO number and date range
- 02Route suggestions between origins and destinations using stored ports, routes, and waypoints
- 03Vessel discovery inside user-defined geographic polygons and operational areas
- 04Background processing for large searches with progress, estimated completion time, and downloadable results
- 05JSON and Excel outputs that make maritime datasets usable in other operational and analytical workflows
- 06Controlled execution and monitoring of long-running data collection commands, including recovery of interrupted work
How it works
The main frontend sends an authorized request to a REST API. Laravel validates the request, records its state in MySQL, and sends expensive work to dedicated Redis queues. Workers process the maritime data without blocking the interface and place completed JSON or Excel files in private storage. The service also connects to the main Smart Ship platform for user identity and credit decisions, while keeping those responsibilities outside the data-processing layer.
Engineering highlights
- Separate queues isolate vessel-history searches from long-running collection and monitoring commands
- Scheduled recovery and monitoring keep recurring data workflows observable and restart incomplete work when appropriate
- Private result files are delivered only through the application flow, with ownership and completion checks applied before download
- A dedicated internal bridge can expose selected vessel and history data to downstream analytical systems without tightly coupling them to the transactional database
- Versioned database migrations and automated tests make important search, route, export, and monitoring behavior repeatable
- The map interface combines Leaflet and OpenStreetMap with the API documentation prepared for the wider product frontend