OpenZiti Controller

OpenZiti Controller is the management server for OpenZiti's open-source zero-trust network platform, used by self-hosters and teams to authenticate…

  • Network Services
  • Tools & Utilities
OpenZiti Controller is the management server for OpenZiti's open-source zero-trust network platform, used by self-hosters and teams to authenticate identities, enforce access policy, and coordinate encrypted service traffic.

Platform availability

Available on 1 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 (not listed)

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.

71/100 Good

Maintained
100last commit 16 days ago
Popular
734,475 GitHub stars
Easy to install
251 install platform, install notes
Light to run
502 GB minimum RAM

Availability: platform listings confirmed today

GitHub stars
4,475
Open issues
419
Last commit
2026-11-05
Latest release
v2.0.8
License
Apache-2.0
Activity
declining

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

Resources & Compatibility

Minimum requirements: 2 GB RAM, 1 CPU core(s).

Checked 40 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Start with quickstart for a basic network Run ziti edge quickstart to start a local controller (the main management server), router (the part that passes traffic), and default admin identity (a login account for the network). This gives you a working local network and a first admin account to use, so you are not left with no basic network or identity. source
  • Use the Docker quickstart container If you are using Docker Compose (a tool that starts app containers from a file), run docker compose up quickstart-check to start the all-in-one quickstart container in the background. This brings up the controller service without manually configuring separate pieces, which avoids missing-service errors. source
  • Use different ports for each cluster member When starting a controller cluster (multiple controller copies working together), give each member a unique instance ID (the name for this controller copy) and ports; the first quickstart member uses control port 1281 for controller commands and router port 3021 for routing traffic. If you reuse the same ports or IDs, the extra member can't join and the cluster may fail. source

Fetched 40 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Should I expose the OpenZiti controller management API to a reverse proxy or public network?

No, you should not expose the controller's management API and only expose the edge client API. The management API can make changes to the network and should be separated for full-time use.

Can a self-hosted OpenZiti controller and edge router be used with Nextcloud on another host or network?

A community example covers a basic self-hosted Ziti controller and edge router setup with Nextcloud on a separate host and network. It asks for advice on the configuration.

Answers sourced from openziti.discourse.group, www.reddit.com

Community

Collected 48 days ago - public community threads