enTrail

Box

The Evidence Box Beta

A dedicated machine that receives your events, seals them, and serves them back with proofs. One organisation can run several. Nothing about your evidence is shared with another customer, because nothing about it leaves your box.

What it actually is

A box is a single virtual machine running the whole pipeline: the API that accepts events, the sealer that chains and signs them, the storage they live in, and the console you look at them through. It has one hostname, of the form name.box.entrail.io.

The reason it is one machine rather than a shared service is the thing being sold. Evidence that sits in a multi-tenant store requires you to trust the operator's isolation. Evidence on a machine of your own requires you to trust arithmetic instead, and arithmetic is checkable.

A box holdsA box never holds
Your events, exactly as sentAnyone else's events
Its own signing keys, one set per environmentA password for any user
The chain, the sealed batches, and the receiptsYour platform account or its second factor
The custodian list it last verifiedAny credential that reaches beyond itself

Creating one

A box is set up for you: creating one, resizing it and setting its maintenance window are administrator actions today, not self-service. Self-service is coming. These are the properties a box has, and the one you can change yourself.

ChoiceNotes
NameOne short word, assigned rather than typed, and it becomes the hostname. Permanent: the hostname appears in receipts and in your own configuration, so renaming would invalidate references.
Reference nameYour own words, up to 60 characters, shown in the box console header so you can tell boxes apart. Yours to change, no bearing on trust, and never part of the hostname — so changing it breaks nothing.
RegionWhere the machine runs. Your plan decides which regions are offered.
SizeS, M, L or XL. It sets your retention allowance, and it can be changed — see below.

Boxes today are managed: we run the machine in our environment and you use it. Running one in your own environment is the other half of the model and is not offered yet, so plan for it rather than assume it.

The maintenance window

Every box has a weekly window: a day, and a start hour in UTC on an even hour, lasting four hours. Updates and anything requiring a restart happen inside it. The window is set by an administrator today; choosing it yourself is coming.

Events are still accepted during the window. Ingest keeps taking them and sealing catches up afterwards, so a maintenance window is not a gap in your evidence. Tell us if your quiet hours are not the default ones.

Scaling

Size is a property of the machine, not of your data, so changing it does not touch a single sealed record. Chains, keys and receipts are unaffected.

  1. Ask for a new size. It is recorded as pending; nothing happens yet.
  2. The change is applied in the next maintenance window.
  3. The box comes back the same box: same name, same hostname, same chains, same keys.

Sizing yourself from the console is coming; today it is an administrator action. One consequence worth knowing before you size down: a project keeps the retention it was given, so shrinking a box does not shorten anything already chosen or sealed.

Scaling out rather than up. If you are weighing one large box against several smaller ones, split by trust boundary rather than by load: a separate box for a subsidiary, a regulated workload, or a region with its own residency requirement. Evidence from different boxes verifies independently, which is usually what an auditor wants anyway.

What lives inside a box

Projects, and environments within them. That structure is where keys and chains actually live, and it is described in projects and environments.

Signing in

Go to your box's address. It has a login page, and that is the normal way in: bookmark name.box.entrail.io and start there. You can also open a box from the platform console, if that is where you happen to be.

  1. Open your box. It sends you to the platform to identify yourself.
  2. Sign in there with your organisation ID, username, password and a code from your authenticator. Anyone who can reach a box needs a second factor, whatever their role.
  3. You are returned to the box console, signed in.

If you are already signed in at the platform, opening a box skips straight to step three. The box itself holds no password of yours and cannot reset one — see how the platform works.

A box session lasts a fixed eight hours and does not extend while you work, so a long day means signing in again rather than a session quietly living forever. Signing out of the platform ends box sessions too.