Command Palette

Search for a command to run…

ZarynZaryn
Zaryn documentation

How it works

Content addressing, the object model, IPFS and provenance.

For architects and security reviewers: how zev stores and signs history, how commits become IPFS objects anyone can resolve, and how Zaryn keeps them available.

For Companies and security teamsFor Developers and AI teams
Start the tutorial →
Learning path

How Zaryn works, step by step

A guided tour of Zaryn's design, from one idea (name data by its content) to the whole system: the pieces, a commit's journey, chunked large files, proofs of storage, provenance and the transparency log, pinning and replication, and what is and isn't built. Pictures first, every step explained.

⏱ About 25 minutes◔ For the curious, architects and security reviewers
  1. Stage 1Understand
    1. One idea: name data by its content
    2. The pieces
    3. What lives where
  2. Stage 2Follow a commit
    1. A commit, made offline
    2. Push: two names, written down
    3. Big files: only what changed
    4. Pull and clone: checked on arrival
  3. Stage 3Trust
    1. What can't be changed quietly
    2. Proof that your data is really kept
    3. From an artifact back to its commit
    4. The transparency log
  4. Stage 4Keep it available
    1. Pinning and replication
    2. Copies that repair themselves
  5. Stage 5Honest limits
    1. Honest limits

What you can do

  • Understand what makes a commit verifiable
  • See how data is stored, chunked and pinned
  • Review the system before you adopt it

Every guide in How it works

How Zaryn works, step by step

A guided tour of Zaryn's design, from one idea (name data by its content) to the whole system: the pieces, a commit's journey, chunked large files, proofs of storage, provenance and the transparency log, pinning and replication, and what is and isn't built. Pictures first, every step explained.

Other products for you

Code hosting and version controlRepositories, branches, pull requests, CI and evals on zev.CI, evals and releasesEvery push built and tested in a locked-down container, and gates that keep main working.Packages and mirrorsA registry for npm, PyPI, Cargo, Zig and containers, and mirrors of the public ones.Files, storage and encryptionShare files by link, prove they are intact, keep private work encrypted.Private networks and proxyA WireGuard mesh for your machines, and Zaryn on a filtered internet.Plans, billing and legalWhat is free, Premium, paying, and the terms you agree to.