# Install zoro with Homebrew Expose local server to external network. Version 20240828 via Homebrew; verified 2026-07-25. ## Install ```sh sudo av install brew:zoro ``` Additional install commands: ### macOS - Homebrew (100%): ```sh brew install zoro ``` Evidence: local Homebrew formula metadata ## Package facts - **Package key:** brew:zoro - **Package manager:** Homebrew - **Version:** 20240828 - **Source summary:** Expose local server to external network - **Homepage:** - **Repository:** - **Last updated:** 2026-07-25T21:50:59+02:00 - **Generated:** 2026-08-03T19:37:03+00:00 ## Executables - zoro (alias) ## Install behavior - Bottle: not available ## Freshness - Page generated: 2026-08-03 - Package-manager version: 20240828 ## Project history and usage zoro is a small Go tunneling tool, formerly known as mr2, for exposing local TCP, UDP, HTTP, and HTTPS services through a remote server. Its history is thinly documented, but the project fits the practical local-tunnel niche occupied by tools such as ngrok, frp, and Cloudflare Tunnel. ### Project history The upstream README identifies the project as "zoro (mr2)" and describes a server/client model for exposing local services to an external network. Older public discussion and GitHub issues still use the mr2 name, showing the continuity between the earlier mr2 identity and the current zoro package. ### Adoption history Public adoption evidence is modest but real: the repository has long-running user issues about Docker, multiple local ports, UDP exposure, Windows behavior, and HTTPS-only servers, and a 2019 Hacker News thread immediately compared mr2/zoro with ngrok, serveo, Argo Tunnel, and frp. ### How it is used A typical setup runs zoro server on a reachable machine and zoro client beside the private service. The examples cover exposing local HTTP, SSH, DNS, directories over HTTP, and arbitrary TCP/UDP services; the HTTPS mode maps a local HTTP service to a remote subdomain-style endpoint. The README notes that UDP can fail in some multi-layer NAT cases, which is a useful operational clue: zoro is best understood as a simple tunneling utility, not a universal NAT traversal guarantee. ### Why package nerds care For package nerds, zoro is interesting as a minimal tunnel package with both TCP and UDP claims, a rename from mr2, and a self-hosted server/client shape rather than a hosted SaaS-only workflow. It is the sort of tool people discover when comparing small networking CLIs by protocol support and operational friction. ### Timeline - 2019: Public mr2 discussion frames the tool as a way to expose local services through a remote server. - 2019-2021: GitHub issues show users asking about Docker, multiple ports, UDP, Windows, and HTTPS deployment cases. - 2020s: The project is presented as zoro (mr2), keeping the local-tunnel use case while adopting the zoro package name. ### Related projects - ngrok: the best-known hosted local-tunnel comparison point. - frp: a self-hostable reverse proxy/tunnel tool often mentioned beside mr2/zoro. - Cloudflare Tunnel: a managed tunnel approach for exposing local or private services. - serveo and localtunnel: simpler public tunneling services in the same developer workflow space. ### Sources - - - ## Security Notes broad file, network, media, or database tool signal. - **Geiger risk:** blue / medium - broad file, network, media, or database tool signal ## Combined YAML source View the package source record on GitHub. [combined/zoro.yml](https://github.com/mxcl/pkgdb/blob/main/combined/zoro.yml) ## Sources - pkg.so package database - Geiger risk classifier - curated package history - pkgdb category and tag curation - cross-ecosystem install command graph