A terabyte. Fifteen characters.
For teams that move very large files: one descriptor, whatever the size.
Size stops being the problem.
Implexus Elephant holds very large files as strands. A film master, an imaging archive or a full backup is named by the same fifteen characters as a one-page letter.
- For
- Teams that move very large files
- Sizes
- Megabytes to petabytes
- Descriptor
- 15 characters at every size
- Travels
- Anywhere text does
- Rebuilt
- Bit-exact, where the cell is
- Built on
- Safe
The same fifteen characters at every size
Sizes are examples. Process lengths are illustrative. Independent validation is in progress.
Moving a very large file
- Drives shipped by courier
- Transfers watched and restarted
- A copy left at every hop
- Fifteen characters sent
- The file rebuilt at the other end
- One original, opened per grant
Where very large files live
MediaFilm masters and raw footage.
HealthImaging archives.
DataDatasets and backups.
Use cases are examples, to confirm with product.
Questions about Elephant
Draft answers. To confirm with product and engineering.
Is there a size limit?
[Limits for the first release: to confirm with engineering.]
How long does a very large file take?
We do not publish process times. Lengths shown on this site are illustrative until independent validation is complete.
How is it licensed?
With the engine: a licence to start, then a royalty per device that ships with the engine inside. No rates are published.
Where it sits
Safe, Relay and Forge are the API layer under every Implexus product.
Store and retrieve. Bit-exact.
Transmit between people, systems and devices.
Build and launch on Safe and Relay.
Start a licensing conversation.
Tell us how large, and how often.