$ cd ../services

Verifiable storage

Hash Vault

Prove the file never changed.

In Hash Vault every object is stored under the checksum of its own contents. If a single byte changes, the address changes, so you can show anyone that the file you hold today is exactly the file you stored on day one.

$ cloudeee vault verify ./contracts

~/services/hash-vault
MATCHsha256:9f2c41ab...e1a7

$ cloudeee hash-vault --features

What you get.

  • F-01

    Content-addressed storage

    A file's address is the hash of its contents. Identical files share one address, and altered files can never pass as the original.

  • F-02

    Verified on every read

    The checksum is recomputed whenever a file is read, so corruption is caught at the moment it would matter.

  • F-03

    Write-once objects

    Stored objects are immutable. Updating a document creates a new object and leaves the original untouched.

  • F-04

    Retention locks

    Apply an optional lock period so records cannot be deleted before the date you choose, even by an administrator.

  • F-05

    Scheduled integrity scans

    A background scan re-checks stored objects against their checksums and flags any mismatch for repair from another copy.

  • F-06

    Exportable proof

    Download a JSON manifest listing file names, hashes and timestamps to hand to an auditor, a client or your own records team.

$ cloudeee hash-vault --how

Four steps, zero fuss.

  1. Step 01

    Upload to a vault

    Send files from the dashboard, API or CLI into a vault. Encryption in transit and at rest applies from the first byte.

  2. Step 02

    Hash is recorded

    Cloudeee computes the SHA-256 checksum, stores the object under it and writes the hash into your manifest.

  3. Step 03

    Verify any time

    Run verify on a file or a whole folder. Matching hashes confirm the contents are identical to what was stored.

  4. Step 04

    Export the report

    Generate a manifest of hashes and timestamps as evidence that your records have not been altered.

$ cat specs.txt

The specs.

~/services/hash-vault/specs.txt
Hash Vault specifications
Hash algorithmSHA-256
ImmutabilityWrite-once with optional retention lock
DeduplicationIdentical content stored once per workspace
Integrity scansScheduled, daily by default
Report formatJSON manifest
RetentionConfigurable lock period

$ man hash-vault

Quick answers.

Q01What if I need to correct a document?
> Upload the corrected version as a new object. It gets its own hash, and the original stays in the vault so the history remains complete.
Q02Does a retention lock stop me from deleting files?
> While a lock is active, locked objects cannot be deleted or altered. When the lock period ends, normal delete permissions apply again.
Q03Is a matching hash legal proof?
> A matching checksum is strong technical evidence that contents are identical. Whether it satisfies a specific legal requirement depends on your situation, so check with your own advisors.

$ cloudeee signup --free

Start with Hash Vault.

Create a free account, get 20 GB of encrypted storage and try it in minutes.