# Zaryn > Zaryn hosts zev repositories. zev is a version control system for code, data and models: content-addressed storage, verified storage, private networks, CI and an API. All docs in one file: https://zaryn.xyz/llms-full.txt ## Packages - [Rust packages (crates)](https://zaryn.xyz/docs/en/packages-rust): Publish a Rust crate to Zaryn with cargo, use it from another project, keep it private, and fix the usual errors. Every step explained. - [Zig packages](https://zaryn.xyz/docs/en/packages-zig): Publish a Zig package and get the exact hash zig fetch will compute, check a package before publishing, use any Zaryn repository as a dependency, and fix build.zig.zon errors. Every step explained. - [Mirrors for pypi.org, npm, crates.io, Rust, Zig and their compilers](https://zaryn.xyz/docs/en/package-mirrors): Make pip, uv, npm, cargo, rustup and zig download through Zaryn when pypi.org, npmjs.com, crates.io, GitHub or ziglang.org are slow or unreachable. Every file is checked against a hash your tools already know, so the mirror can't change anything. - [npm packages (JavaScript, TypeScript)](https://zaryn.xyz/docs/en/packages-npm): Publish a JavaScript or TypeScript package to Zaryn with npm, install it with npm, pnpm or yarn, and keep it private. Every step explained. - [Python packages (pip, uv, Poetry)](https://zaryn.xyz/docs/en/packages-pypi): Install Python packages through Zaryn with pip, uv or Poetry, publish your own, install Python itself, and keep private packages private. One index for your projects and pypi.org, safe from look-alike packages. Every step explained. - [Container images](https://zaryn.xyz/docs/en/packages-containers): Push Docker or OCI images to Zaryn, pull them anywhere including Kubernetes, and store Helm charts and other OCI artifacts. Every step explained. - [Any file (release downloads)](https://zaryn.xyz/docs/en/packages-files): Publish program downloads, archives or datasets as versioned files with a fixed address, and download them with curl. Every step explained. - [Packages, explained](https://zaryn.xyz/docs/en/packages): What a package is, what a registry does, and how Zaryn hosts packages for Rust, Zig, JavaScript, Python and containers, in plain words. Start here if you have never published one. ## Zaryn features - [Path Explain and probes](https://zaryn.xyz/docs/en/network-paths): Why can't A reach B? Zaryn follows the traffic hop by hop through your devices' routes, ACLs and firewalls, names the device and the rule that stops it, and gives the fix in that device's commands. Probes check what matters every minute. - [Digital twin: test a change before you make it](https://zaryn.xyz/docs/en/network-twin): See what a config change would do to your network before anyone types it. Which traffic stops, starts or takes another way and why, every routing table entry that changes, and the single points of failure it creates. On the site page, from the command line, and on every pull request. - [Storing and sharing files](https://zaryn.xyz/docs/en/storing-files): Put a file on Zaryn and get a link anyone can open. How much space you have, what "public" means here, and how to remove a file. - [Private networks](https://zaryn.xyz/docs/en/private-networks): Connect your laptops, servers, CI runners and apps into one private network, so they reach each other directly and securely, wherever they are. - [Network sites (routers and switches)](https://zaryn.xyz/docs/en/network-sites): See your routers and switches live. Every config backed up and checked against the approved one, a map of how devices connect, and an address plan with its conflicts. Cisco, Huawei, MikroTik, FRRouting and VyOS. - [Encrypted repositories](https://zaryn.xyz/docs/en/encrypted-repositories): Encrypt a private repository's files on your own devices, so Zaryn stores only data it can't read. - [Evals and lineage](https://zaryn.xyz/docs/en/evals-and-lineage): Know before you open a pull request whether your change made anything worse (tests, coverage, speed, build time, bundle, binary or firmware size, frame times, model scores), and when what it came from changed. - [Verified storage](https://zaryn.xyz/docs/en/verified-storage): Check with cryptographic proofs, instead of taking anyone's word for it, that Zaryn really stores everything you pushed. - [Advisories and lineage](https://zaryn.xyz/docs/en/advisories): Declare commits compromised and find everything built on them. - [Billing and Zaryn credits](https://zaryn.xyz/docs/en/billing-and-credits): How paying works: Zaryn credits, USDC and Premium. ## Start here - [What Zaryn can do](https://zaryn.xyz/docs/en/what-zaryn-can-do): Every Zaryn service in plain words, where to find it on the site, what's free, and the guide that shows you how. Start here if you're new. - [Quick start](https://zaryn.xyz/docs/en/quickstart): From nothing to your first project on Zaryn in about five minutes. Every command is explained as you go. - [Why zev exists](https://zaryn.xyz/docs/en/why-zev): The problems zev was built to solve, and how it differs from git. ## Getting started - [Installation](https://zaryn.xyz/docs/en/installation): Install zev on Linux, macOS or Windows with one command, or from your package manager. Then keep it updated. - [Your first repository, step by step](https://zaryn.xyz/docs/en/first-repository): Create a repository, save versions, look at history, and undo mistakes, with every idea explained. - [Share your work on Zaryn](https://zaryn.xyz/docs/en/pushing-and-pulling): Sign in, put a project on Zaryn, clone someone else's, and keep everyone in sync with push and pull. - [Words you'll see](https://zaryn.xyz/docs/en/glossary): Plain explanations of the words used in zev, Zaryn and these docs, from A to Z. ## Guides - [How do I…?](https://zaryn.xyz/docs/en/how-do-i): Short answers to the things people most often need to do. Find yours in the list on the right, or press / to search. - [Branches and merging](https://zaryn.xyz/docs/en/branches): Work on new ideas without touching your main code, then bring them back in. Includes fixing merge conflicts, step by step. - [When something goes wrong](https://zaryn.xyz/docs/en/troubleshooting): zev's messages, what they mean, and what to do. Search for the words of the message you got. - [Proxy and VPN (zev proxy, zev vpn)](https://zaryn.xyz/docs/en/proxy): When Zaryn or other sites are blocked, use your own VLESS, VMess, Trojan, Shadowsocks, Hysteria2 or WireGuard servers for zev, every app, or the whole computer (a VPN). ## Command reference - [All commands](https://zaryn.xyz/docs/en/commands): Every zev command, with the ones you'll use every day first. Each entry says what it does, how to type it, and shows examples. - [Collaboration from the Terminal](https://zaryn.xyz/docs/en/cli-collaboration): Issues, pull requests, forks and reviews, all from the terminal. - [Scripting and AI Agents](https://zaryn.xyz/docs/en/automation-and-agents): Use zev from scripts, CI, servers and AI agents: tokens, JSON output and the MCP server. ## Core concepts - [What is zev](https://zaryn.xyz/docs/en/what-is-zev): What zev and Zaryn are, what they are made of, and what they can do. - [Content-addressed storage](https://zaryn.xyz/docs/en/content-addressing): Every object is named by the hash of what's in it: why that makes storage safe and deduplicated. - [Content-defined chunking](https://zaryn.xyz/docs/en/chunking): How zev splits files into chunks by content, so a small edit stores only what changed. - [Semantic (AST) diffing](https://zaryn.xyz/docs/en/semantic-diff): zev sdiff compares Zig code by function (added, removed, signature or body changed) from the compiler's own parser, not lines of text. - [Memoized CI](https://zaryn.xyz/docs/en/memoized-ci): CI that skips work it has done before: steps are cached by the hash of their inputs. - [IPLD and provenance](https://zaryn.xyz/docs/en/ipld-provenance): Each commit mirrored as an IPLD block with its own CID, for provenance you can check outside zev. ## Architecture - [System overview](https://zaryn.xyz/docs/en/system-overview): How zev, the Zaryn API, storage and CI fit together. - [The object model](https://zaryn.xyz/docs/en/object-model): Blobs, trees, commits and refs: the objects zev stores and how they link. - [Pinning and IPFS Cluster](https://zaryn.xyz/docs/en/pinning-and-cluster): How zev keeps content available: pinning to IPFS (standard CIDs) and replicating across nodes with IPFS Cluster. ## Legal - [Terms of Service](https://zaryn.xyz/docs/en/terms): The agreement between you and Zaryn for using the service. - [Privacy Policy](https://zaryn.xyz/docs/en/privacy): What Zaryn collects, why, how long it's kept and your choices. - [Acceptable Use Policy](https://zaryn.xyz/docs/en/acceptable-use): What you may and may not host or do on Zaryn.