A note from the builder

Hi, I'm Mark.

I'm a software engineer. I'm about to take delivery of my first catamaran.

I've been looking at the marine tech I'd put on it — chartplotters, weather apps, anchor watches, electrical monitors, security tools. Each piece is fine on its own, but none of them work together, and the user experience is a long way behind what I'm used to in the rest of my software life. Some apps, like a solar planner, didn't really exist.

So I'm building what I wish existed: 32 degrees North — a complete set of marine apps that work together, with AI built in, that anyone can run on their own boat.

I spent the last decade in software supply chain security. I'm not interested in shipping a marine platform that any teenager with a Flipper Zero can walk onto. Security is part of the architecture from day one, not bolted on later.

The name

Why 32 degrees North.

32°N is a line of latitude. It is, specifically, the latitude of the northern vertex of the Bermuda Triangle — Bermuda sits at roughly 32°N, 64°W, with Miami and San Juan forming the southern corners.

A real coordinate with a real story attached: navigation, the ocean, and a touch of folklore. It is also easier to say and remember than the project's working name.

The triangle in the wordmark — 32°N▲ — is the same shape. It's not arbitrary decoration; it's the geographic anchor of the name.

How I build

The principles I'm building by.

Apple's product principles. They're the closest articulation I've found of how to actually build a coherent product. 32°N follows them.

Simplicity over complexity.

Removing things until what's left is the right thing.

Design is how it works.

Functionality first, look-and-feel second. Both matter.

End-to-end integration.

Hardware, software, services designed to work together.

Iterative refinement.

Ship narrow, then make it better. Repeat.

Privacy and security first.

Designed in, not bolted on.

A thousand no's for every yes.

Focus on doing a few things well.