Krakentools

Name: Port call and berth-scheduling operational data exposed through a machine API — port call records (scheduled, expected, in-harbour and waitlisted, including cruise-specific calls), vessel master data, and the related port-community entities behind them (administrative body, organisation, cargo), i.e. the authoritative port-authority-side schedule and berth-allocation ledger that vessel-tracking feeds only infer
Creator: Krakentools

KRAKENTOOLSManage supplier listing

Port call and berth-scheduling operational data exposed through a machine API — port call records (scheduled, expected, in-harbour and waitlisted, including cruise-specific calls), vessel master data, and the related port-community entities behind them (administrative body, organisation, cargo), i.e. the authoritative port-authority-side schedule and berth-allocation ledger that vessel-tracking feeds only infer

Open buyer room →

Sample

Brickroad customers

Sample this dataset before you buy it.

Your sourcing agent asks Krakentools and files the sample in your catalog — private to you.

Start 7-day trialNothing is charged until the trial ends.

Coverage

Universe, instruments and categories.

Industry: Application SoftwareMarine
Instruments: equities
Categories: Alternative

Dataset card

Type: not stated
Format: Tabular — JSON responses from REST endpoints keyed by client code, with a documented DTO/schema layer (port call, vessel, cargo, organisation, administrative body); structured for direct machine ingestion rather than reports
Volume: Est. 1-10M port-call records cumulatively across the installed port base, each carrying berth, times, cargo, agent and vessel identifiers, plus a vessel master table of est. 10K-50K distinct visiting hulls; the API is scoped per client code, so the aggregate footprint depends on how many ports run Kraken Port
Users: ~200-1,000 named users across port authorities, agents, cruise operators and terminal operators on the Kraken platform (est. from a 38-person software vendor serving a defined port-community market, where each installation has a small number of port-authority and agent seats)
History: 8 years
Update frequency: not stated
Growth: Active — a live, publicly documented, versioned public API with an active developer onboarding path indicates the product is maintained and expanding its integration surface; the vendor itself has been through a merger/acquisition event, which usually consolidates rather than accelerates growth
Launched: Kraken software lineage dates to the early 2000s in the Norwegian cruise and shipping market (the vendor record shows a merger/acquisition history consistent with that consolidation), with the Kraken Port module and its public API est. ~2018-2022, when REST API publication became standard for port-community systems
Delivery: not stated
Entity mapping: not stated
Sample: not stated
Point-in-time: not stated
Licence: not stated

supplier index read from their site