Simulated · CGI
AI FOR MACHINES · UNDERWATER VEHICLES
No radio reaches below the surface. The AI has to dive with the vehicle.
An untethered vehicle runs its survey alone, with only a slow acoustic link to the vessel. Small models are designed to travel with it, a person on the vessel approves every dive, and a tethered vehicle is still flown by its pilot.
IN SHORT
AgentAnywhere's AI for underwater vehicles is designed to run on the vehicle and on the support vessel, with no cloud connection. Autonomous underwater vehicles survey on their own plan, Tatva is designed to turn an operator's plain words into one command or no action, and a person on the vessel approves every inspection dive. A simulated demonstration is on our demo hub; builds on a real vehicle are design-partner work.
- Runs offline, on the machine
- Sized for constrained hardware
- Approved by the survey lead on the vessel
THE PROBLEM
Under water, the link is the first thing you lose.
Radio does not travel through sea water. An untethered vehicle surveying a pipeline or a cable route is out of reach of anything but a slow acoustic link, a few words at a time. Whatever it needs to understand, it has to understand on board.
A tethered vehicle has the opposite problem: it is flown by hand, every minute of bottom time is expensive, and it should go down only where there is something worth looking at. Someone on the vessel has to decide that, and be able to show afterwards why.
ON THE DEVICE · OFFLINE
What runs where.
Two families, designed for the vehicle and the vessel. Nothing here needs a connection to shore.
Language to one machine command — or none.
Designed to turn an operator's instruction into one command for the vehicle, or no action when it is out of scope. A tethered vehicle is never driven by Tatva: its pilot flies it by hand.
Where · Designed for the vehicle's own computer and the vessel's console, offline. Design-partner work.
Fleet and telemetry intelligence — the warning before the failure.
Designed to read battery, thruster and housing telemetry and warn the team before a fault ends a dive.
Where · Designed for the support vessel, read over the tether or on recovery. Design-partner work.
DEMOS · LIVE ON THE DEMO HUB
One demo you can open today, and what is being built.
Ocean Watch runs on our demo hub. The sea and the vehicles in it are simulated, and the page says on screen which parts are real. The other two are use cases we are scoping with design partners, shown as illustrations.
Simulated · CGI
Ocean Watch
Three untethered vehicles leave a support vessel and survey a subsea pipeline on their own plan. A sonar map flags anomalies on the line, a planner proposes where to look and keeps clear of a protected reef, a person approves, and one tethered vehicle, flown by its pilot, goes down to inspect.
The sea and vehicles are simulated and the sonar anomaly map is a concept, not a current capability. The Tatva Edge outputs are real recorded output from the drone command set.
Illustration
Tasking in plain words, before the dive
The survey lead says what to cover and what to avoid. It becomes a plan a person can read and approve on deck, and the vehicle dives with it on board.
No demo yet · illustrative use case
Illustration
Vehicle health, before the fault
Battery, thrusters and housing sensors read for the team, with a warning before a fault cuts a dive short.
No demo yet · illustrative use case
The demo hub is behind sign-in. If you don't have access yet, ask us — we'll set you up, or walk you through it live.
Request demo accessHOW EVERY MACHINE STAYS IN HUMAN COMMAND
The model proposes. It never decides.
On this machine, the named person is the survey lead on the vessel.
Policy outside the model
Rules are written and versioned outside the model and checked on every proposal. A model cannot talk its way past them.
A named person approves
Anything consequential waits for a named person. Their approval, or their refusal, is part of the record.
Signed receipts
Every proposal, check and approval is written to a signed, hash-chained receipt that can be verified offline, later, by someone else.
WHAT WE DO NOT CLAIM
The boundary, stated.
FAQ
Frequently asked questions.
- Can AI run on an underwater vehicle with no link to the surface?
- That is what small on-board models are for. Radio does not reach below the surface and an acoustic link carries only a few words at a time, so whatever the vehicle needs to understand has to be on board. Our models are designed for that; builds on a real underwater vehicle are design-partner work.
- What is the difference between an AUV and an ROV?
- An autonomous underwater vehicle is untethered: it carries a pre-programmed plan and its own navigation, and works alone. A remotely operated vehicle is on a tether and is flown in real time by a pilot on the vessel. Our demonstration shows both, and Tatva never drives the tethered one.
- Is there an underwater demo?
- Yes, a simulated one. Ocean Watch on our demo hub shows a seabed survey along a pipeline and an inspection dive that a person approves. The sea and vehicles are simulated, and the command outputs are real recorded model output from the drone command set.
- Who approves what an underwater vehicle does?
- A named person on the support vessel. The model only proposes, a policy outside the model checks each proposal, and every plan, approval and refusal is written to a signed receipt.
Claims last reviewed . Demos are simulated demonstrations; each one says on screen which parts are real model output.
Bring us your underwater vehicles.
Tell us the machine, the mission and the hardware. We'll show you the demo on your scenario, and tell you honestly what is ready and what we would build with you.