Illustration
AI FOR MACHINES · ARMOURED AND UTILITY VEHICLES
The crew asks. The vehicle answers. Nothing leaves the hull.
Ask for a route, a fault explanation or a pre-start check in plain words, and get it — on the vehicle's own computer, with no link to anywhere. Tatva turns the crew's instruction into one command, a policy outside the model checks it, and the vehicle commander approves.
IN SHORT
AgentAnywhere's AI for armoured and utility vehicles is designed to run on the vehicle's own computer with no outside connection. Tatva turns a crew member's spoken instruction into one command for navigation, diagnostics or a system check, and Sanjaya reads engine and power health and warns before a fault. Policy sits outside the model and the vehicle commander approves. Builds are design-partner work.
- Runs offline, on the machine
- Sized for constrained hardware
- Approved by the vehicle commander
THE PROBLEM
A crew has its hands full, and the link is the first thing to go.
Inside a moving vehicle the crew is reading terrain, radios and gauges at once. Finding a fault code or re-planning a route means eyes down and hands off, at exactly the wrong moment.
And the vehicle cannot depend on a connection to anywhere. Whatever helps the crew has to run inside the hull, on the hardware already there, with nothing to leak and nothing to jam.
ON THE DEVICE · OFFLINE
What runs where.
Two families, designed for the vehicle's own computer. Both work with no link at all — nothing to leak, nothing to jam.
Language to one machine command — or none.
Turns a crew instruction — “route to checkpoint two, avoid the river crossing”, “run the pre-start checks” — into one navigation, diagnostics or system-check command. Anything else returns no action.
Where · Designed for the vehicle's own computer, air-gapped. Design-partner work.
Fleet and telemetry intelligence — the warning before the failure.
Designed to read engine, transmission, power and cooling telemetry and warn the crew before a fault stops the vehicle.
Where · Designed for the vehicle, with no link out. Design-partner work.
USE CASES · WITH DESIGN PARTNERS
Use cases being built with design partners.
There is no demo for these vehicles on our demo hub yet, so we will not show you one. These are the crew use cases we are building with design partners, shown as illustrations.
Illustration
Navigation by voice
The driver asks for a route that avoids a crossing. The request becomes one navigation command, the commander approves, and the route appears on the crew display.
No demo yet · illustrative use case
Illustration
Diagnostics without the manual
“Why is the engine running hot?” The crew gets the relevant readings and the likely cause from the vehicle's own telemetry, and decides what to do.
No demo yet · illustrative use case
Illustration
System checks, spoken
“Run the pre-start checks.” The checklist runs step by step on the vehicle and each result is written to a signed record the maintainers can verify later.
No demo yet · illustrative use case
Want to be the design partner who sees it first? Tell us your machine and your mission.
Talk to us about a pilotHOW EVERY MACHINE STAYS IN HUMAN COMMAND
The model proposes. It never decides.
On this machine, the named person is the vehicle commander.
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.
- What can the crew ask the vehicle to do?
- Navigation, diagnostics and system checks: plan or change a route, explain a fault from the vehicle's own telemetry, run a checklist. Anything outside that vocabulary returns no action.
- Does it need a network connection?
- No. Tatva and Sanjaya are designed to run on the vehicle's own computer, air-gapped. Nothing the crew says leaves the vehicle.
- Who approves a command?
- The vehicle commander. The model proposes one command, a policy outside the model checks it, and the commander approves before anything changes. Every step is written to a signed record.
- Is it connected to weapons?
- No. Tatva and Sanjaya are never connected to any weapon system and are never placed in a weapons-release chain. Neither is a targeting or engagement system.
- Is there a demo?
- Not yet, and we will not show one until there is. Talk to us if you want to build these crew use cases with us.
Claims last reviewed . Demos are simulated demonstrations; each one says on screen which parts are real model output.
Bring us your armoured and utility vehicles.
There is no demo for this machine yet. If you have the machine and the mission, we would like to build the first one with you.