Skip to content

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

The EnSign registry console, showing the current work desk of a demonstration registry.

Saint Brendan is a registry that exists to be shown. It has a flag, a mark, a fee schedule, a catalogue of requirements and a register with thirty ships on it, and none of them is real — which is what makes it useful. It is where we run a registration whenever somebody asks what EnSign actually does, and it is what the recorded demonstration on the product page shows. This is that walk, written down.

It starts with the owner, not the registry.

An owner adds a vessel — a name, a type, the particulars — and starts an application: the vessel, the registry, the transaction. The moment both are chosen, the registry's own checklist appears, requirement by requirement, in the registry's own words. Not a list someone retyped from a PDF: the catalogue the registry keeps, issued to this file. Where the registry publishes limits, an advisory note says so at once — advisory only, because the registry decides and the owner can still submit.

Then the documents. The owner drops them in — all at once, if they like — and each one is sorted into the slot it belongs to and read on arrival. The certificate of class is checked against the register: does the IMO number match, does the vessel name match, is it still valid? The owner sees the answer before the registry does — AI check passed, or what needs attention — and a file that ignores a requirement cannot be sent.

What the registrar opens is finished.

On the registry's side the application lands in current work as one case: every document in its slot, every check already run, every finding already on the file. The exceptions are marked — the expired certificate, the wrong ship, the name that does not match — and nothing else is. A registrar reads the file, asks for more if the file needs it, and decides. The decision carries their name. The platform prepares; it never signs.

On the demonstration registry that decision is ready in two business days once every document has arrived complete, because there is nothing left to chase. The weeks that a registration by email loses to round trips — the missing paper, the second email, the phone call — do not happen, because nothing incomplete could have been submitted.

And the certificate comes back the same way.

When the registrar issues, the certificate of registry appears on the owner's file at a stable link, on the registry's own paper — its mark, its flag, its wording — the moment it is issued. Fees, where the registry charges them, appear on the same file and are settled with the registry. The record of who decided, when, and what they were looking at stays on the file as a record, not reconstructed later from a mailbox.

That is the whole of it: an owner who cannot send an incomplete file, a registrar who opens a complete one, and a register that stays the registry's. The film shows it in four minutes; the owner's journey lays it out step by step.

More from News

All posts →
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

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