OpenZiti Tunnel

OpenZiti Tunnel is an open-source zero-trust tunneler that provides encrypted, identity-based access to services without exposing IP addresses.

  • Network Services
  • Tools & Utilities
OpenZiti Tunnel is an open-source zero-trust tunneler that provides encrypted, identity-based access to services without exposing IP addresses. It works with existing applications without code changes, so self-hosters can securely reach their homelab from anywhere without opening firewall ports or managing NAT.

Platform availability

Available on 2 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

75/100 Good

Maintained
100last commit 4 days ago
Popular
734,492 GitHub stars
Easy to install
352 install platforms, install notes
Light to run
No data
Security check
70no serious findings, 4 minor, CI, tests, OpenSSF Scorecard 6/10

Based on 4 of 5 factors.

Availability: platform listings confirmed today

GitHub stars
4,492
Open issues
401
Last commit
2026-11-17
Latest release
v2.0.8
License
Apache-2.0
Activity
declining

Checked 4 days ago - source: GitHub (openziti/ziti)

Resources & Compatibility

Requirements not published yet.

First-install notes

  • Install the Linux agent first Run the one-line installer with sudo so the zrok agent is added to your Linux system; without it, the app has no background program to create tunnels. source
  • Copy the .env.example before Docker If you use Docker (a packaged way to run the app), copy .env.example to .env and edit that file before starting anything; skipping it can leave the app without the settings it needs. source
  • Make it start automatically on Windows On Windows, use nssm (a small tool for turning programs into services) to install the agent as a service if you want it to start after reboots and keep running quietly; otherwise it stops when you close the terminal. source

Fetched 53 days ago - each note links to its source

Alternatives (2)

Checked 40 days ago - source: AlternativeTo

Common questions

Do OpenZiti services need open public ports?

No. The source describes dark APIs and services using zero listening ports, so authorized clients connect through OpenZiti while everyone else sees nothing.

Can a homelab deployment work behind CGNAT?

A forum source walks through remote homelab access and Jellyfin using a controller, public edge, and Proxmox behind CGNAT.

What common mistakes make OpenZiti appear broken after setup?

Misconfigurations with extra spaces or spelling errors, blocked firewall ports, offline routers, and bad policies are common. They can cause log errors or services not appearing.

What file must be prepared before starting a Docker deployment?

Copy .env.example to .env and edit it before starting anything. Skipping it can leave the app without the settings it needs.

How can the tunnel agent keep running on Windows after a restart?

Use nssm to install the agent as a Windows service. Otherwise it stops when the terminal is closed.

Answers sourced from github.com, github.com, github.com, openziti.discourse.group, openziti.discourse.group

Community

Collected 48 days ago - public community threads