Nauticus ToolKITT™ was originally built around Aquanaut®, but you’ve made a deliberate push to run it on third-party ROVs as well. What’s the thinking behind opening up the software?
Nauticus ToolKITT was never meant to be locked to a single vehicle. From day one, we designed it as a vehicle-agnostic autonomy layer, capable of handling robotic controls, sensor integration, simulation, and data analysis regardless of the hardware underneath it. Extending it to third-party ROVs is a natural expression of that architecture, and honestly, it’s a better business model for the industry as a whole.
Operators have spent years and significant capital building out their existing fleets. They shouldn’t have to replace all of that to get autonomous capability—they should be able to integrate it. That’s the difference between selling a subsea robotic vehicle and selling an autonomy platform. We’ve deliberately chosen the latter, because we think it’s where the real long-term value sits. As more of the ROV fleet worldwide adopts this kind of layer at scale, the industry stops thinking about autonomy as a hardware purchase and starts thinking about it as an upgrade path.

Your team has been running ongoing remote testing from Houston, Texas with Aquanaut deployed in Stuart, Florida. What has that operating model actually proven?
It’s proven more than the vehicle itself—it’s validated the entire concept of remote operations at a level that matters to offshore operators. Every hour we run that link between Houston and our Florida site is testing the communications architecture, the control interfaces, and the human workflows that will define how this industry executes autonomous subsea work from shore, not just from a vessel.
That distinction matters enormously. The operational cost of subsea work is dominated by getting people and vessels offshore. If we can prove, hour after hour, that a team based onshore can reliably operate and troubleshoot a vehicle hundreds of miles away, we’re not just demonstrating a vehicle capability—we’re demonstrating an entirely different cost structure for how this work gets done. That reliability record is exactly what operators need to see before they’re willing to trust autonomous deployment on a live asset.
Offshore digitization often gets discussed in the abstract—sensors, data, interfaces. What does it look like in practice on an actual mission?
It starts with data capture at the vehicle—sonar, high-resolution imagery, sensor readings across whatever the mission calls for. But the meaningful work happens in what Nauticus ToolKITT does with that information in real time. The software is classifying what it’s seeing, flagging anomalies against expected conditions, and packaging that into something an operator can act on immediately, rather than a technician sorting through hours of raw footage after the vehicle is already back on deck. That’s the true value of digitization, in my view—and that value is only realized if the distance and time between data capture and a decision being made is shortened. A beautifully organized dataset that still requires a week of manual review afterward hasn’t actually solved the operator’s problem. We built Nauticus ToolKITT to close that gap, not just document it.

You’ve recently signaled a shift toward supporting persistent ocean sensing infrastructure, beyond inspection and intervention. Is that the same technology, or something new?
It’s fundamentally the same platform, applied to a different mission profile—but that shift asks more of the underlying system than people might assume. Persistent sensing means Aquanaut and Nauticus ToolKITT operating continuously across weeks and months rather than executing a single inspection visit and returning to the surface. The core autonomy architecture doesn’t change—the decision-making, the sensor fusion, the vehicle-agnostic design all carry over directly.
What does change is the endurance and reliability bar we have to clear. A system that performs beautifully on a four-hour inspection mission has to prove something entirely different when it’s expected to maintain awareness of a stretch of seafloor for months without a single unplanned failure. That’s less a new technology problem and more a new confidence problem, and we take it just as seriously.

If you look two or three years out, what’s the single biggest barrier standing between where offshore automation is today and where it needs to be?
Trust, more than technology. The hardware and software in this space are advancing quickly—faster, frankly, than most people outside the industry realize. What moves more slowly is operator confidence: the track record required before a company is willing to hand inspection or intervention work on a critical asset over to an autonomous system with no one physically watching. That confidence isn’t built through a single technical breakthrough or a compelling demo. It’s built one successful mission at a time, one reliability record at a time, until the operator stops asking “will this work” and starts asking “when can we schedule the next one.”
We think we’re further along that path than most people assume, but I won’t pretend the industry is fully there yet. Getting the rest of the way is as much a cultural and commercial challenge as it is an engineering one. Either way, Nauticus Robotics is committed to working with customers and partners alike to realize a new operating reality that embraces these new opportunities.
This feature appeared in ON&T Magazine’s 2026 September Edition, Offshore Digitalization & Automation, to read more access the magazine here.