Overview
zrok is an open-source sharing and tunneling platform from NetFoundry, built on the OpenZiti zero-trust networking project. It connects a local service or resource to other people or to the public internet without requiring inbound firewall ports or traditional port forwarding. The official site describes zrok as both a SaaS product and a self-hosted service instance, while the current documentation identifies version 2.0 as current. In practical terms, zrok can put a development web server behind a public HTTPS URL, let another zrok user access a private resource as though it were local, or expose files and directories through supported sharing modes.
The distinction between public and private sharing matters. Public shares are intended for HTTP and HTTPS resources that must be reachable by someone who is not running zrok. Private shares require the accessing person to have an account on the same zrok service instance and the share token; they can also carry TCP and UDP traffic. This makes zrok more than an HTTP reverse proxy: its documented private modes include raw network tunnels and SOCKS5 access, while its public modes include proxying, serving a directory, WebDAV drive sharing, and a Caddy-based server.
Key Features
zrok supports public and private resource sharing, identity-based access through the OpenZiti overlay, and operation through firewalls and NAT without opening inbound ports, as described in the official product overview. Public sharing supports HTTP/HTTPS backend modes including proxy, web, drive, and caddy; the backend-mode documentation explains what each mode does. Private sharing supports all backend modes plus tcpTunnel, udpTunnel, and socks, according to the private-sharing guide.
The hosted product also documents automatic TLS for public shares, optional Google or GitHub OAuth authentication, an anti-phishing interstitial for a public share created by an unverified free account, and defenses against maliciously large uploads and SQL-injection requests on shared web applications on the official pricing and product page. The repository documents cross-platform support for Windows, macOS, Linux, and Raspberry Pi, plus a Go SDK for embedding sharing into applications in the official GitHub README.
Use Cases
For developers, zrok can publish a local web application for a remote review, demo, integration test, or webhook callback without changing router configuration. The public-share documentation specifically identifies development web servers, webhooks, and other HTTP/HTTPS resources as common uses. For teams, private shares can connect a service, development environment, or low-level TCP/UDP endpoint to another authorized zrok user while keeping it off the public internet.
For file and content distribution, the web backend serves a local directory as a browsable file index or static site, and the drive backend exposes a local directory over WebDAV for mounting as a network drive. A self-hosted operator can run an internal sharing service for an organization, configure its own OAuth and user-management policies, and apply resource-count or bandwidth limits through the documented limits agent. The self-hosting documentation covers Linux, Docker, and Kubernetes deployments.
Best for
zrok is best for engineers who need short-lived or persistent ingress to local HTTP services, controlled peer-to-peer sharing, private TCP/UDP connectivity, file and drive sharing, or a zero-trust alternative to exposing ports. It is particularly suitable when the operator values an open-source implementation, wants the option to run the control plane on its own infrastructure, or needs public and private sharing in one tool. It is less appropriate to describe zrok as a general-purpose CDN, a hosted application platform, or a complete observability suite: those functions are not what the reviewed official sources document.
Alternatives
ngrok is the closer comparison when the primary need is a managed developer tunnel and public endpoint for local HTTP services. zrok differs by emphasizing open-source operation, OpenZiti-based private peer-to-peer sharing, additional private TCP/UDP/SOCKS modes, and self-hosting. Tailscale is primarily a mesh VPN and device-to-device networking product; it is a better conceptual fit for persistent private network access between managed devices, whereas zrok focuses on shareable resources and public or private ingress. Hookdeck is oriented toward receiving, inspecting, replaying, and routing webhooks; zrok can expose a local webhook endpoint, but it is not documented by the reviewed sources as a webhook observability and workflow product.
Pricing
The hosted zrok free plan is listed at $0 per month with no credit card required. The official pricing page states limits of 5 daily GB, 25 environments, 50 share backends (ephemeral or reserved), and 50 private access frontends, plus community support. It also says a credit card can be added to remove interstitial pages. For production workloads, SLAs, dedicated infrastructure, and custom limits, NetFoundry directs users to contact it about commercial options; the page does not publish an exact commercial price. Self-hosting is presented as an open-source Apache 2.0 option with “no limits” in the hosted pricing comparison, but the operator can configure limits for its own instance.
Frequently Asked Questions
Does zrok require opening a firewall port?
No inbound port opening is required for the documented sharing workflows. The official overview says zrok works through firewalls and provides secure tunneling using the OpenZiti overlay.
What can a public zrok share expose?
Public shares support HTTP and HTTPS resources. Documented public backend modes are proxy, web, drive, and caddy; raw TCP and UDP modes are private-share capabilities rather than public-share modes.
How does private sharing control access?
A private share is identified by a share token, and the accessing user must have an account on the same service instance and an enabled environment. The resource is accessed locally through the zrok2 access command.
Can I run zrok myself?
Yes. Official documentation provides self-hosting paths for Linux, Docker, and Kubernetes. The repository and pricing page identify the project as Apache 2.0 open source, and the self-hosting guides cover configuration, OAuth, metrics, limits, organizations, and user management.
What are the hosted free-plan limits?
The official hosted free plan costs $0 per month and includes 5 daily GB, 25 environments, 50 share backends, and 50 private access frontends. It also includes community support and does not require a credit card to start.

