Episode 1: The search starts here. Power or sail?

GlassBridge

The vessel,
clearly.

GlassBridge is the local-first, touch-first Yacht OS being built in the YachtNot lab: one precise view across navigation context, engines, power, tanks, alarms, cameras, audio and source health, with authenticated remote access kept read-only.

GlassBridgeOnPoint marine systems
GlassBridge Bridge screen showing navigation, engines, power, tanks, alarms and source health
Touch-first helm interfaceLocal-first · authenticated read-only cloud

The problem

Too many screens. Too many apps. Too little context.

Many yachts separate navigation, propulsion, batteries, charging, tanks, cameras, music, environmental data and alarms across unrelated interfaces. GlassBridge brings the monitored picture together without creating a new single point of failure.

YachtNot lab status: GlassBridge is an active monitoring and advisory platform. It is not a certified navigation, collision-avoidance, engine-control, fire, bilge or life-safety system.
  • Critical systems remain independentThe interface does not replace proven marine controls or certified instruments.
  • Local-first aboardThe onboard appliance remains useful when internet access is limited or absent.
  • Source quality stays visibleSource, age, stale, missing, error and simulated states are shown rather than hidden.

Primary surfaces

What GlassBridge brings into view.

Power & energy

Batteries, shore input, generator state, charging and electrical quality.

Tanks & environment

Fresh water, waste, fuel where available, temperatures, humidity and environmental sensors.

Cameras & security

A calm view of authorised onboard cameras without exposing blind spots or sensitive topology.

Audio & comfort

Audio zones, selected comfort systems and the everyday interfaces owners actually use.

Alarms & quality

Good, stale, missing, error and simulated data states—so silence is never mistaken for health.

Marine data later

Engine and navigation information only after the correct networks, permissions and safety boundaries exist.

Architecture boundary

Sources to screen—without pretending the screen is the source.

The interface sits above real systems. It does not replace them.

01

Onboard sources

Approved integrations supply vessel observations with origin, quality and age.

02

Local appliance

The touch-first helm experience runs aboard and remains useful without internet access.

03

Read-only cloud

Authenticated remote views receive observations without cloud acknowledgement or command paths.

04

Consistent surfaces

Bridge, Navigation, Engines, Power, SmartYacht, Audio, Cameras, Vessel and System share one shell.

The lab build

Real hardware before the real yacht.

The current YachtNot lab brings together Victron power monitoring, secured UniFi infrastructure and cameras, Sonos, environmental observations, local servers, storage and Yacht Assistant. Each screen keeps the origin and age of monitored data visible.

  • Bench-test integrationsValidate reconnects, stale-data handling, alarms and degraded states.
  • Protect sensitive informationNo passwords, serial numbers, IP addresses, camera blind spots or exact topology are published.
  • Keep remote access read-onlyThe cloud view receives observations without creating remote acknowledgement or marine-command paths.
GlassBridge navigation presentation with source-aware context and no route activation
Navigation context in the GlassBridge visual languageSource aware · no route activation

We are building the smart yacht before buying the yacht.

Follow the local-first lab build, the vessel integration and every decision in between.