enTrail

Platform

How the platform works Beta

The platform console holds one identity for your organisation: the people, their second factors, and which boxes each may reach. A box holds none of that. It trusts a signed ticket and a signed list, and that difference is the whole design.

The beta console is live at demoplatform.entrail.io. Registration is open: create an organisation, add people, and try the sign-in described below. It is a beta environment, not production — it is for trying the system, so do not put anything in it you would need to rely on later. Evidence that has to stand up belongs on a box of your own.

Status. The console is live in beta: registration, sign-in, evidence boxes, access, activity, account, notifications and the getting-started list all work today. Where something below is not switched on yet, it says so on the line rather than in a footnote.

Why a box holds no passwords

A box is a machine that may sit in your data centre, may be offline for a week, and may be one of many. If each one kept its own passwords, then revoking a person would mean reaching every box, and a stolen box would mean stolen credentials. So boxes keep no passwords and no password resets.

Instead the platform issues signed proof that a particular person authenticated just now for a particular box, and separately publishes a signed list of who may reach it. A box verifies both offline, against a key it already holds, without asking anyone at the moment it has to decide.

Signing in, in outline

You can start at either end: open your box and it will hand you to the platform, or open a box from the platform console. Either way it is the platform that checks who you are, checks you are a custodian of that box, and gives your browser signed, single-use proof for that one box. The box verifies the signature against a key it already holds, checks the ticket is for itself and still valid, checks you appear in the list it last verified, and only then starts a session of its own.

The consequence worth planning around: revoking someone takes effect on a box within about a minute, not instantly, and a box that cannot reach us keeps honouring the last list it verified. It fails towards staying available rather than locking you out, which is a deliberate trade.

The protocol in detail is shared on request, not published. Exactly what is signed, what the box checks, how the list is versioned and what it refuses are the parts worth reviewing before you trust any of this — and the parts most useful to someone attacking it or copying it. Email info@entrail.io and we will send your security team the protocol note, and answer whatever it does not cover.

The platform keeps its own trail

Every change to people, roles and boxes is recorded as a config event, hash-chained to the one before it. The platform is held to the same standard as the product: you can ask what changed, when, and who did it, and the answer is not editable after the fact.

Read next