Version control,
anchored to the real network.
Every commit is a standards-compliant IPFS CID: content-addressed, signed, and resolvable from any node on Earth. No walled garden, just history anyone can verify.
- Code hosting and version control
- CI, evals and releases
- Packages and mirrors
- Files, storage and encryption
- Network automation
- Network design repositories
- Virtualization
- Private networks and proxy
Every repository is browsable without an account. Sign in only when you're ready to push.
Content-addressed
Every commit is a real IPFS CID. Resolve it from any node, pin it anywhere, and it stays the same bytes forever.
learn more →Signed & auditable
History is content-addressed and commits can be signed; every pin is recorded in a public, append-only transparency log you can verify yourself.
learn more →Searchable by meaning
Semantic search over history finds "fixed the race condition" even when the message says something else.
learn more →Networks as code
Topology repos get real graph analysis: single points of failure, routing, max-flow, and structural diffs per PR.
learn more →One platform, a product for each team
Software teams, network engineers, infrastructure teams and companies each get their own part of Zaryn, with its own guides. Use one, or all of them together.
For Developers and AI teams
Repositories, branches, pull requests, CI and evals on zev.
Code hosting and version control docs →Every push built and tested in a locked-down container, and gates that keep main working.
- Memoized CISteps whose inputs didn't change are skipped with their earlier results, so pipelines take seconds.
- Evals for any projectBenchmarks, bundle sizes, coverage, fps or model scores tracked per commit; a pull request that makes them worse is stopped.
A registry for npm, PyPI, Cargo, Zig and containers, and mirrors of the public ones.
- Packagesnpm, PyPI, Cargo, Zig and container images in one registry, next to the code that builds them.
- Mirrors that work anywhereFast mirrors of pypi.org, npm, crates.io, Rust and Zig with their compilers, for networks where the originals are slow or blocked.
Share files by link, prove they are intact, keep private work encrypted.
- Verified storageFiles and repositories you can prove are intact, with links that keep working.
- Encrypted repositoriesPrivate code encrypted with keys only your devices hold.
A WireGuard mesh for your machines, and Zaryn on a filtered internet.
- Private networksA WireGuard mesh for laptops, servers and CI, through any NAT, encrypted end to end.
For Network engineers
Routers and switches as a site: backups, drift, paths, a digital twin and safe rollouts.
- Network sitesRouters and switches from Cisco, Huawei, MikroTik, FRR and VyOS: configs backed up, drift, a live map and an address plan.
- Path ExplainWhy A can't reach B, hop by hop: the route, the ACL rule that drops it, and the fix in the device's own commands.
- Digital twinSee what a config change would do before it's made: which traffic stops or reroutes, and the single points of failure it creates. Every pull request checked.
- Safe rolloutsConfig changes made on the devices, checked on the live network against the twin, and taken back by themselves when it doesn't hold. Approval, canaries, every command kept.
- Device accessA terminal on any router for a limited time, without sharing its password: approved, revocable, recorded keystroke by keystroke.
The network’s source of truth as text, checked against reality and protected by intents.
Network design repositories docs →For Infrastructure and virtualization
Every VM on seven platforms, joined to the switches it runs through.
Virtualization docs →For Companies and security teams
What is free, Premium, paying, and the terms you agree to.
Plans, billing and legal docs →