Class Societies
Tumba builds autonomy and remote operations software in a way that produces evidence class societies can assess.
Simulated and recorded missions that run through the real software, automated tests in CI, and results the team can reproduce on shore.
We want to work with classification societies (class societies) on how that evidence should look. We do not certify, and our software has no class approval.
What is the challenge for classification societies?
Autonomous and remotely operated ships move the safety case from steel to software.
Goal-based rules
The MASS Code sets goals; the applicant must prove they are met.
Sea trials are not enough
Simulation must fill the gap, but only if the simulation itself is credible evidence.
Hard-to-read evidence
Requirements, tests and results often live in different tools.
Software changes often
Monthly releases need evidence that each release was tested, not only the first one.
Remote operations centres
The MASS Code brings the shore-side ROC software into scope.
Cyber resilience
IACS E26 and E27 apply to new ships contracted from 1 July 2024; CRA reporting started on 11 September 2026.
What does Tumba bring to class work?
Simulation on the real interface
Simulated missions reach the operator console by the same path as live ones.
Replay of real missions
A field event becomes a repeatable test case.
Automated tests in CI
End-to-end and visual regression suites catch a broken feature before a release.
One versioned data contract
A fixed reference for what the system exchanges.
Supervision-first design
Operator interfaces on OpenBridge that keep a person in the loop.
How can we work together?
- 1. Technical input to guidance on simulation-based and replay-based evidence.
- 2. Joint workshops with the teams that apply for approval of remote or autonomous functions.
- 3. A pilot test campaign on a real system, to show what a reproducible evidence package looks like.
Which technologies do we use?
Also: mission replay through production software, versioned JSON Schema packages, React, TypeScript, OpenBridge, Prometheus, Loki.
Which projects show this approach?
Shore-side testing for a global offshore survey company
For about 25 months, most testing happened on shore: a simulator on the vessel's own interface, replay of recorded missions and automated tests in CI. The software went live on two commercial survey vessels and one test vessel, with 55 vessel-side releases.
Scoping a sea-rescue app with a maritime technology company
Tumba scoped and built a situational awareness app for a sea-rescue vessel with camera, infrared, radar and LiDAR sensors. A short accelerator programme grew to eight months.
"I have very positive experience involving Tumba in brainstorming, scoping and prioritization."
Frequently asked questions
Does Tumba certify software or hold class approval?
No. Tumba does not certify, and our software has no class-society approval. We build and test the software that class societies assess, and we want to help define what good evidence looks like.
What does the IMO MASS Code ask of software?
The MASS Code is goal-based. It asks for risk assessment, robust system design and cybersecurity, and it covers remote operations centres. The applicant must show how the goals are met.
Can simulation count as evidence for autonomous ships?
Only if the simulation itself is credible. Our simulators use the same interface specification as the vessel, and recorded missions replay through the production software, so results can be reproduced on shore. Whether that evidence is accepted is for the class society to decide.
What are IACS UR E26 and E27?
They are IACS unified requirements on cyber resilience. E26 covers the ship, and E27 covers on-board systems and equipment. The revised versions apply to new ships contracted for construction on or after 1 July 2024.
How can a classification society work with Tumba?
Through technical input to guidance, joint workshops with the teams that apply for approval, or a pilot test campaign on a real system.
Learn more
How do we start working together?
A 30-minute conversation with our technical lead about your current autonomy and ROC work.
Contact: snoitulos.abmut@tcatnoc
Sources: IMO, IMO adopts first global Code for autonomous ships, May 2026 · IACS, UR E26 and E27 · European Commission, Cyber Resilience Act · Last updated 27 October 2026