Web Analytics
Skip to content

Zora — Recreational & Commercial Navigation ​

Zora is the Boat Operating System for recreational boats: the Zora frontend running on iNav4U OS. About Zora covers the product. This page is about the frontend, which turns vessel data and capabilities into an easy, configurable “bridge” experience: clear situational awareness, fast interaction, and screens that match how you operate.

If you’re looking for hands-on usage (“where do I tap?”), go to the Zora Help Guide.

How Zora organizes the boat ​

Zora groups onboard information and workflows into screen groups (each with multiple screens):

  • Navigation — charts, AIS, route context, weather overlays, collision/safety awareness
  • Journal — logbook/journey context, events, notes, history-based insight
  • Systems — vessel health, power/energy, alarms, monitoring, connected equipment
  • Custom — build your own bridge layout for your boat and your role

Screens, widgets, and your “bridge layout” ​

A Zora screen is composed of widgets (charts, lists, instruments, system panels, etc.). This lets you:

  • Arrange the information you need for your boat and the current situation
  • Build dedicated layouts (e.g. docking, night passages, offshore watch, engineering checks)
  • Keep the UI consistent across different monitor sizes and orientations

For customization walkthroughs, see the Screens & customizing guide.

How it fits into the iNav4U platform ​

  • Cloud (iNav4U Cloud) provides updates and services when available.
  • Operating system (iNav4U OS) manages data ingestion, reliability, security, and standardized APIs.
  • Frontend (Zora) turns those APIs into operational screens and interactions.

This separation is why Zora can evolve quickly without compromising the underlying system stability.

Positioning vs chartplotters ​

Traditional chartplotters are strong navigation instruments, but they tend to become "one more silo" as you add systems and apps.

Zora’s goal is to provide a unified operational interface across navigation + systems + history/logging, while still benefiting from iNav4U’s platform approach. The design follows the same principle as the aviation Primary Flight Display (PFD) — a single, integrated, intent-driven view rather than a collection of independent instruments. For the literature this principle is built on, see the iNav4U Research Foundation. For the broader product comparison, see iNav4U vs Chartplotters.

Where to go next ​