Skip to content

Direction

Why we are building EnSign

The world's fleet is registered by email. We are building what should have replaced it years ago — and this is the whole of the argument.

Aurelith · · 3 min read

Roughly sixty thousand merchant ships are on the water, and every one of them is on somebody's register. A flag is the law a ship sails under, the inspection regime it answers to, and the authority that stands behind its certificates — one of the most consequential decisions an owner makes.

And it is administered, almost everywhere, by email. An owner writes in. Somebody retypes a list of requirements. Documents arrive as attachments over days or weeks and are checked against a checklist held in a person's head. Something is missing, and the whole exchange begins again.

Nobody in this industry is doing anything wrong.

The registries know exactly what they need. The owners are not withholding it. What is missing is the thing in between — and no such thing has ever been built.

That is what we are building. Not a faster mailbox: one ecosystem for the whole of flag registration. A portal where an owner sees the flag's own requirements and cannot submit a file that ignores them. A console where a registry's officers work every application, document and finding in one place. A public directory where flags are compared on their published record. All three against one register, which stays the registry's.

Two things hold at every point in it. The machine never decides. EnSign reads, compares and proposes, and shows its reasoning; a named registrar approves, rejects and issues. And the register stays the registry's — a complete copy in a standard format, on request, written into the agreement rather than promised on a website.

What happens next.

EnSign opens to registries in September 2026 and to shipowners in October. Until then, we would rather show it running than describe it: there is a recorded demonstration on the product page, and a public directory of thirty flags built from published Paris MoU data — both there to be checked, not believed. Seeing it against a registry's own rules is an hour, and it commits nobody to anything.

More from News

All posts →
The EnSign registry console, showing the current work desk of a demonstration registry.
Building EnSign

What a registration looks like on EnSign

A walk through one registration on our demonstration registry — from an owner's checklist to a certificate on the registry's own paper — and what never happens in between.

Aurelith · · 4 min read

Industry

Paris MoU standings, explained

White, Grey and Black; the excess factor; the thirty-inspection floor. What the standings in our directory mean, where they come from, and why we show them verbatim.

Aurelith · · 4 min read

For registries

See it on your own registry.

Bring your checklist and one real file. An hour, on your rules, and it commits you to nothing.

Book a demo

For shipowners

Choose your flag.

Thirty flags on their published record, and one account to file with any of them. Registration opens October 2026.

Open the directory