Secure document storage and retrieval.
Safe turns any document into a strand and gives it back exactly as it went in.
Safe is the storage API behind Digital Bank, Implexus Vault and Implexus Elephant.
Storage that gives back exactly what went in.
Safe is the storage and retrieval endpoint of the Q⁴ Data Engine. Each document is held as a strand and named by fifteen characters. It comes back bit-exact, to the people a grant allows.
- Endpoint
- Store and retrieve
- Accepts
- Any file type, any size
- Names each file with
- 15 characters
- Returns
- The original, bit-exact
- Access
- Per grant, per party
- Products built on it
- Digital Bank, Vault, Elephant
What Safe does
Six things a team can do with Safe from the first day of an evaluation.
Documents, media, databases and firmware. Any type, any size.
Every stored file gets one descriptor, whatever its size.
Regenerated where the cell is present. What comes back is what went in.
Decide who can rebuild a file, and take that right back, per party.
Each version of a document carries its own descriptor.
To confirmThe same toolkit that reaches Relay and Forge.
Two documents in. Two short lines out.
The video shows a contract and a scan become two lines of characters, then come back identical. The frame below is the illustrative result for one of them.
Built on Safe
Three Implexus products store through Safe.
Digital Bank
Implexus Vault
Implexus ElephantTechnical summary
The shape of the endpoint. Full reference on the developer site.
Interfaces and limits to confirm with engineering.
- Operations
- Store, retrieve, grant, withdrawTo confirm
- Input
- Any file type, any size
- Output
- A fifteen-character descriptor
- Retrieval
- Bit-exact regeneration where the cell is present
- Access control
- Per grant: who, how, when, how many times
- Interface
- [REST API through the SDK]To confirm
- Deployment
- [Cloud, on-premises, or both]To confirm
- SDK languages
- [Languages for the first release]To confirm
Questions about Safe
Draft answers. To confirm with product and engineering.
Is the descriptor a password?
No. A descriptor names a file. It does not open it. Opening needs the cell, which Implexus controls, and a grant that says who may open the file and for how long.
Which files can Safe hold?
Any type, at any size. [Limits for the first release: to confirm.]
What comes back when a file is retrieved?
The original, bit-exact. What comes back is what went in.
Where does Safe run?
[Deployment options, regions and hosting: to confirm with engineering.]
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.
Start a licensing conversation.
Tell us what you are storing and for whom.