Skip to content
Skip to content

Bring your own storage

We don't sell you storage.
You already have it

Connect GitHub, GitLab, Hugging Face or Telegram. Your encrypted chunks live in accounts you control. No lock-in, ever.

Start freeRead the docs
Connected storage
Encrypted before upload
Telegram
50 MB / file
GitHub
850 MB / repo
GitLab
9 GB / repo
Hugging Face
90 GB / account
chunk-01chunk-02chunk-03→ stored as build-cache in a repo you own

Where your files live

Connect what you already pay for

Four platforms, each with its own generous limits. Mix and match: the more you connect, the more room you have.

  • Telegram

    50 MB / fileMany small chunks, spread wide.

  • GitHub

    850 MB / repoThe default. Spin up as many repos as you like.

  • GitLab

    9 GB / repoRoomier repos for heavier vaults.

  • Hugging Face

    90 GB / accountBuilt for large files, serious headroom.

Capacities are approximate, per-repo or per-file platform limits and can change at the providers' discretion. zcrypt works within whatever each platform currently allows.

  • Split, encrypted, disguised

    Each file is encrypted on your device, then split into ~10 MB chunks stored as ordinary build-cache objects in a repo you own. Across your whole library, files spread over the accounts you've connected.

  • Automatic repo rotation

    When a repo nears its platform's ceiling, zcrypt rotates to a fresh one on its own. Your usable space grows without you lifting a finger.

  • Space that grows

    Connect more accounts, get more room. There's no zcrypt-sold quota to bump against: your capacity is whatever you already have.

  • Disguised on arrival

    Chunks are stored looking like ordinary build-cache files: unremarkable artifacts in a code repo, not obvious encrypted blobs.

  • Your infrastructure

    The bytes sit in accounts you control and can walk away with. zcrypt orchestrates; it doesn't hold your storage hostage.

  • No lock-in

    Disconnect a platform or leave entirely, your accounts are yours. Open source, so the mechanics are never a black box.

Your data, your infrastructure

Nothing to be locked into

Most cloud storage rents you space on the provider's servers, on the provider's terms. zcrypt flips that: it's an encryption and orchestration layer over storage you already own. Everything is encrypted on your device first, then chunks are disguised as ordinary build-cache files in repos you own: your library spread across the accounts you connect. Walk away whenever you like: the accounts, and the bytes in them, were always yours.

  • Encrypted on your device before any upload
  • Chunks disguised as routine build-cache artifacts
  • Stored in repos across accounts you control
  • Disconnect or leave anytime, no captive data
How the repo pool rotates
// how a file lands in your storage
1 encrypt on device. AES-256-GCM
2 split into chunks
3 disguise as build-cache-*.bin
4 upload to a repo you own
5 repo near limit? rotate → fresh repo
✓ your accounts. your bytes. no zcrypt-sold quota.

Related

Get started today

Storage you own, encryption you trust

Free and open source. Connect an account you already have and start in under a minute.

Start free