One integrated system that captures vessel data onboard, standardises it across the fleet, and delivers it through APIs. Your analytics, your reporting, your compliance tools, your third parties. One source, any consumer.
Captures vessel data at source. Standardises across vessels and systems. Stores and serves through APIs in the naming schemas your downstream systems require.
Monitors data health, investigates root causes, and takes action to restore data streams. The work that has to happen for a Foundation to stay trustworthy at fleet scale.
The Foundation is what every Raa Labs customer receives. It is the same underlying system across all operating models. What varies is the operational layer on top.
Every signal contextualised against a fleet-wide naming schema. ISO 19848, DNV VIS, JSMEA, or custom naming, served simultaneously from the same Foundation. A signal means the same thing on every vessel.
Stored in a dedicated fleet tenant in the Raa Labs cloud. Measurements, metadata, statistics, and derived values served through structured APIs. Contextualised and uncontextualised signals available. Pull into your data lake, analytics tools, reporting systems, or share with third parties.
Fleet-level visibility into your data foundation. Fleet overview showing connected vessels, data explorer for viewing and comparing raw data, tag library, expected signals overview, and platform service health visibility.
Token-based authentication governs who can reach the API. You decide which systems and people get access to your fleet's data.
Raa Labs has developed a Model Context Protocol (MCP) server for the Foundation, available to every customer. It works with major AI chat interfaces such as Claude, ChatGPT and Copilot: they query the same standardised, quality-checked data through the Foundation's APIs, and answer with tables and charts. Access controls and data ownership stay unchanged: the MCP is a new way in, not a new copy of the data. Eastern Pacific Shipping is one of the first operators using it.
Read how EPS uses it →Both deliver into the same Raa Labs fleet tenant. A fleet can mix both. The choice is made per vessel based on existing setup and what data you need.
Captures data directly from vessel systems, standardises at the source, delivers to the cloud. Handles signal capture, local processing, buffering during connectivity loss, and secure transmission. OEM-agnostic across all common industrial protocols. Standardisation happens onboard, not just in the cloud. Data buffered locally during connectivity loss, no data lost. Entire software stack managed remotely after physical install, no crew involvement for ongoing operations.
Brings data from existing onboard collectors into the Foundation at the cloud level. No new hardware. No rip and replace. Data from existing collectors is ingested, contextualised, and standardised. Consolidates data from multiple collectors and OEM clouds into one foundation. Raa Labs handles format mapping, signal identification, and contextualisation. Historical data can be backfilled. No onboard installation required.
RaaEDGE holds a Bureau Veritas Type Approval Certificate as a Cyber Ship-Shore Data Sharing System, assessed against IACS UR E27 Rev.1, “Cyber resilience of on-board systems and equipment”, and BV NR659. Its E27 documentation is designed to feed into the vessel-level UR E26 deliverables, so the platform fits into the cyber resilience work for each ship.
Bureau Veritas Type Approval Certificate no. 84267, issued July 2026. Verify on the BV website →
Cyber resilience of the ship as a whole is the responsibility of the shipyard or systems integrator and the shipowner. RaaEDGE’s E27 documentation supports those deliverables.
No lock-in. Change where your data goes and how it is used without changing the foundation underneath.
Capturing data and standardising it is not enough. At fleet scale, things happen. Sensors drift. Onboard systems change. Connectivity varies. OEMs update interfaces. Crew change configurations. Keeping the data dependable over time is its own discipline. We call it the vessel data Function.
Watch every contextualised signal across the fleet. Connection status, latency, data quality, completeness. When something degrades or stops, it is detected, not waited on.
Trace the issue to its root cause. Place it where it belongs: sensor, onboard system, connectivity, platform, OEM. Cross system boundaries. Coordinate with crew, customer IT, OEM vendors, connectivity providers. Investigation is where most of the operational work lives.
Work to restore the data stream. Coordinate the work required, whether it is a configuration change, a sensor replacement, a vendor escalation, or a crew action. Track the case through to closure.
Vessel data does not stay reliable on its own. Signals degrade, connections drop, sensors drift, configurations change. Somebody needs to watch, figure out what went wrong, and get it fixed. This is the vessel data Function. The operating model defines who does it.
Platform service health (ingestion services, processing pipelines, storage, APIs, portal, monitoring infrastructure) is Raa Labs' responsibility regardless of operating model. The choice is about the Function: who monitors data health, who acts on issues, who is accountable for keeping the data trustworthy at fleet scale.
See Our ServiceVessel data infrastructure is one integrated system that captures vessel data onboard, standardises it across the fleet, and delivers it through APIs to every team and application that relies on it: analytics, reporting, compliance tools, and third parties. Raa Labs provides it as two paired parts: the Foundation, which produces one trusted dataset across the fleet, and the Function, the operational discipline that keeps that data reliable over time.
RaaEDGE is an onboard edge computing platform. It captures data directly from vessel systems, standardises it at the source, buffers it during connectivity loss, and delivers it securely to the cloud. Cloud Connect is a cloud-to-cloud integration that brings data from existing onboard collectors into the Foundation with no new hardware and no onboard installation. Both deliver into the same Raa Labs fleet tenant, and a fleet can mix both, choosing per vessel.
Every signal is contextualised against a fleet-wide naming schema. ISO 19848, DNV VIS, JSMEA, or custom naming can be served simultaneously from the same Foundation, so a signal means the same thing on every vessel.
With RaaEDGE, data is buffered locally onboard during connectivity loss and transmitted when the connection returns, so no data is lost.
High-frequency time series are stored in a dedicated fleet tenant in the Raa Labs cloud. Measurements, metadata, statistics, and derived values are served through structured APIs, with both contextualised and uncontextualised signals available. Token-based authentication governs who can reach the API, and the Raa Labs Portal gives fleet-level visibility into the data foundation.
RaaEDGE is type approved under IACS UR E27. UR E26 applies to the ship as a whole, so it is not something a product is certified for. RaaEDGE holds a Bureau Veritas Type Approval Certificate (Cyber Ship-Shore Data Sharing System) under IACS UR E27 Rev.1, “Cyber resilience of on-board systems and equipment”, issued July 2026. UR E26 is the responsibility of the shipyard or systems integrator and the shipowner. RaaEDGE’s E27 documentation is designed to feed into those vessel-level E26 deliverables.
Only for the physical installation. After that, the entire software stack is managed remotely, with no crew involvement for ongoing operations.
AI is only as reliable as the data it works from. If the same signal means different things on different vessels, or a sensor quietly stops reporting, AI tools give confident answers built on bad data. The Foundation standardises every signal against a fleet-wide naming schema, and the Function monitors data health so degraded or missing streams are detected, not waited on. That gives AI tools, and the people using them, data they can trust.
An MCP (Model Context Protocol) is an open standard that lets AI assistants connect securely to a data source. Raa Labs has developed an MCP server for the Foundation, available to every customer and working with major AI chat interfaces such as Claude, ChatGPT and Copilot. The assistant queries the Foundation's APIs, so answers draw on the same standardised, quality-checked data, and your access controls and data ownership stay unchanged. Eastern Pacific Shipping is one of the first operators using it, asking questions such as how shaft power compared across sister vessels on a voyage.
No. Raa Labs provides the data layer, not the analytics. You can pull data into your own data lake, analytics tools, and reporting systems, or share it with third parties, and change where your data goes without changing the foundation underneath.