A file collapsing to a strand and rebuilt on the far side
Use case: Deliver large files

Deliver the file without sending the file.

The file stays in the cell. Its descriptor, fifteen characters, crosses the channel, and the file is regenerated bit-exact where the cell is present, for the people a grant allows.

Media and streaming, Data centre and edge

Deliver large files

Delivery, without the copy.

Today a large file is copied end to end every time it moves: to a partner, to a second site, to a screen. With the engine the file is imploded once and named by fifteen characters. The descriptor travels on any channel that carries text, and the far end regenerates the file where the cell is present.

The use case at a glance
For
Studios, broadcasters, archives and data centres
What travels
The descriptor: fifteen characters
What stays put
The file, held as a strand in the cell
Products
Relay, Safe, Implexus Elephant, Digital Bank

What changes when the copy stops travelling

Today
  • Every delivery is a full copy, end to end.
  • Every copy is one more place the file can leak.
  • A large file waits on every link it crosses.
With the engine
  • The descriptor crosses; the file is regenerated where the cell is present.
  • Opening needs the cell and a grant, checked at Decode.
  • What comes back is bit-exact: the same file, at the same size.
How it works

Watch one delivery, step by step.

Five files leave a hard drive and are rebuilt on a screen. Scroll inside the demo or press Play; turn on CC for the narration.

  1. 01Implosion

    Each file is cut into pieces, fingerprinted and folded into one root, named by fifteen characters.

  2. 02Transmission

    Only the descriptor crosses the channel. The files stay where they are.

  3. 03Regeneration

    The grant and the receiving device are checked before anything opens. A copy on the wrong device stays shut. The file is rebuilt where the cell is present and checked bit-exact against its root.

Demo with illustrative files and values. The receiving cell holds the strands, or is sent the ones it lacks.

Film canisters beside a modern hard drive
In practice

A finished master reaches three partners.

  1. 01First

    The master is imploded once, in the studio's cell.

  2. 02Then

    Each partner receives its descriptor and a grant with its own terms.

  3. 03Finally

    Each partner regenerates the master where the cell is present. The grant ends on the agreed date.

Example scenario, not a customer deployment.

What holds, every time

Opening is checked

Decode confirms the right to open, and for how long, before anything is rebuilt.

Bit-exact

The rebuilt file matches the original bit for bit, at its original size.

Any channel that carries text

The descriptor is fifteen characters. It travels wherever text does.

Markets where it appliesUse cases are examples of where the engine applies, not current deployments.Media and streamingData centre and edge
The words on this pageDescriptor, strand, cell, grant: one meaning each.LexiconTransmission

Questions about deliver large files

Draft answers. To confirm with product and engineering.

Does the file itself never move?

The descriptor is what crosses the channel. The receiving cell must hold the file's strands; any it lacks are sent once. [How strands first reach a new cell: to confirm with engineering.]

Is the descriptor a secret?

No. It names a file; it does not open it. Opening needs the cell and a grant.

How long does a delivery take?

We do not publish process times. Lengths in the demo are illustrative.

Build delivery on the engine.

Start with an evaluation licence and the SDK, then ship under a product licence.