The iNav4U Platform
The architecture is the product.
The iNav4U Platform is not a single device, a single application, or a single feature. It is a system architecture designed to grow, adapt, and evolve with the requirements of the vessel, the mission, and the people on board.
Most marine technology bakes one idea into one product. Buy a chartplotter and you get that chartplotter — its features, its limits, its fixed interface. When your needs change, you replace it.
The iNav4U Platform is built differently. We bake in a structure, not a product — a layered platform on which many different products, missions, and user experiences can be built without rewriting the foundation. The platform we ship today is the same platform that will run on fleet vessels, autonomous platforms, and professional operations tomorrow.
The platform is iNav4U OS on the boat, iNav4U Cloud beside it, and the frontends on top. A frontend and iNav4U OS together make a product: Zora is the Zora frontend on iNav4U OS, built for recreational boats.
That's why we say:
We do things the way they are meant to be.
This page is the system-wide overview. For deeper detail, follow the links into the iNav4U OS, iNav4U Cloud, and User Interfaces sections.
The three layers
The platform separates the system into three layers — each with one job, each independently evolvable.
| Layer | What it owns |
|---|---|
| OS layer | Hardened embedded Linux on industrial-grade marine hardware. Sensors, system services, security, lifecycle, and over-the-air updates. |
| Data & logic layer | Aggregates onboard input through open marine standards. Validates and prioritizes vessel data in real time. |
| UI layer | A client of the system, not the system itself. Multiple user interfaces — one per operational mission — share the same secure base. |
| Cloud | Sits alongside the boat, never above it. Adds reach and remote services when reachable; never authoritative over the vessel. |
This separation is the architectural decision that makes everything else possible.
What "flexible" actually means
Flexibility is easy to claim and hard to deliver. Here is what it means in practice for the iNav4U Platform.
One platform, many user interfaces
The same iNav4U OS runs underneath every iNav4U frontend. Zora is in production today for recreational and commercial navigation. Navio (commercial fleets), Pelos (autonomous vessels), Tactical (professional operations), and Custom OEM interfaces are designed to run on the same secure base, communicating through the same standardized APIs. A new mission does not require a new platform — it requires a new client of an existing platform.
See User Interfaces for the full catalog.
A platform that grows with you
The iNav4U Platform is built to evolve. The clean separation between layers means new capabilities can be added to the platform without disrupting what already works, and without forcing the boat owner into a new product cycle every few years.
What "powerful" actually means
Flexibility is meaningless without substance underneath. The iNav4U Platform is built on engineering choices that make the platform credible at every scale of vessel.
- Hardware-rooted, zero-credential security — Every device has a hardware-bound identity. There are no passwords or stored tokens anywhere in the system.
- 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.
- Air-gapped by design — Fully operational offline on the vessel's local network. Internet connectivity is optional. The vessel is the system of record.
- Built on aerospace research — The OS / UI separation, the intent-driven presentation, and the "suggestions never decisions" principle are not opinions. They are the conclusions of decades of peer-reviewed human factors work on situation awareness and human-AI teaming, applied to a vessel.
These are not specifications added to a brochure. They are the consequences of building the platform the way it is meant to be built.
Built for the long game
Vessels last decades. Most marine electronics tie software progress to the hardware lifecycle, so a five-year-old chartplotter cannot run modern features without being thrown away.
The iNav4U Platform is designed differently. The clean separation between hardware, services, and user interfaces means each layer can evolve on its own schedule. The user interface can be redesigned without replacing the system. New capabilities can be added without disrupting what already works. The cloud can grow without modifying the boat.
That's what it means to build a platform instead of a product. Flexibility today, growth tomorrow, and a foundation that does not need to be replaced just because the world keeps moving.
Where to go next
- About Zora — the Boat Operating System for recreational boats
- iNav4U OS — the operating system on board: security, hardware, the research foundation
- iNav4U Cloud — what the cloud adds when a connection is available
- User Interfaces — the catalog of interfaces that run on iNav4U OS, organized by operational function
- Compatibility & partners — supported devices, protocols, and integration partners