Security
Hardware-rooted. The way it's meant to be done.
Marine systems are increasingly connected. iNav4U OS treats security as a foundational design element, not a feature added later.
Most marine systems still rely on passwords, API keys, or stored tokens to identify themselves. Every one of those credentials is something that can be stolen, replayed, leaked, or forgotten.
iNav4U OS uses none of them.
Identity is rooted in the device hardware, not in a credential database. There is nothing for an attacker to steal, because there is nothing stored.
This is what we mean when we say we do things the way they are meant to be.
Hardware-rooted identity
Every iNav4U device ships with a Trusted Platform Module (TPM) chip — a dedicated cryptographic processor embedded in the hardware. The TPM is what makes the zero-credential model possible. There are no passwords, no API keys, and no stored tokens anywhere in the system.
Encrypted communications
All cloud and remote-service connections use industry-standard secure transport. HTTPS is mandatory for every external integration.
Air-gapped by design
iNav4U OS is fully operational offline on the vessel's local network. Internet connectivity is optional. All mission-critical capability runs on the boat, with no dependency on a cloud uplink.
This is a structural property, not a fallback mode. The boat does not need the internet to function.
Defense and space heritage
The current iNav4U computing platform belongs to the same product family deployed by national defense forces and on the NASA Mars Perseverance rover. The engineering tolerances required for those environments are exactly the engineering tolerances required for serious marine deployment.
If it can survive Mars, it can survive a hard offshore passage.