What kinds of resources can zrok share beyond HTTP endpoints?

Updated

zrok can share more than HTTP endpoints: it lets users share files and web content directly, and its peer-to-peer framework is designed to extend to other decentralized resource types such as repositories and video. The key condition is that sharing happens through zrok's private, Zero Trust overlay rather than by exposing a public endpoint, so the resource type changes but the security model does not.

Beyond HTTP proxies: what the framework covers

The zrok site describes the product as going "beyond HTTP proxies." Rather than only proxying an HTTP endpoint, zrok lets users "easily and rapidly share files and web content." The same page lists repositories and video as examples of decentralized resources, and states that zrok "is also ready to be extended to support many kinds of decentralized resource sharing."

That means the practical answer has two layers:

  • Available today per the site: files and web content, plus HTTP application tunneling.
  • Designed for extension: repositories, video, and other peer-to-peer resource types through the same framework.

The site frames this as "a framework that makes this kind of peer-to-peer resource sharing simple and secure," so the extensibility is a stated design property, not a promise of a fixed feature list.

How sharing differs from a public tunnel

zrok offers two modes, and the resource type interacts with which one you choose:

Mode What is exposed Best fit
Public sharing A publicly reachable endpoint Web content or apps meant for anyone
Private sharing Nothing public; traffic moves between zrok clients Files, repositories, or internal resources for specific people

In private usage, the site says "your private resources are not exposed to any public endpoints, and all communication is securely and privately transported between zrok clients." For file or repository sharing among a known group, that private path is the relevant one; public sharing suits web content you intend to publish.

The mechanism in one example

Suppose a small team needs to pass a build artifact or a documentation folder to a colleague without standing up a server. With zrok, one side shares the resource through the zrok environment and the other side reaches it as a zrok client; the transfer rides the OpenZiti Zero Trust overlay instead of a public URL. The same pattern applies to a video file or a repository snapshot, which is why the site describes the framework as extensible rather than tied to one resource type.

What to check before relying on it

  • Confirm the specific resource type in the docs. The homepage names files, web content, repositories, and video, but exact commands and supported sharing modes for each are documented separately under docs.
  • Decide public vs. private first. Private sharing keeps resources off public endpoints; public sharing is for content you want reachable.
  • Account setup is a prerequisite. The site's three steps are zrok2 invite (create an account with the service), zrok2 enable (enable your shell environment), and zrok2 share (share resources). The same binary supports self-hosted environments layered on an OpenZiti network, so self-hosting is an option if you do not want the NetFoundry-operated public instance.

If your need is limited to exposing an HTTP app, a standard tunnel is enough. If you need to move files, publish web content, or share repositories and media peer-to-peer without public exposure, zrok's broader sharing framework is the reason to choose it.