Executables for the open-core Ziti release.


Last 30 days:

Open issues
PRs opened

Project type


Project tech


Currently seeking

  • Developers
  • Technical Writers
  • Testers

Contribution overview

Most contributors are in America

Mentorship & pairing available

Features code maps



Ziti represents the next generation of secure, open-source networking for your applications. Ziti has several components.

Quick Reference

What is Ziti?

  • The Ziti fabric provides a scalable, plugable, networking mesh with built in smart routing
  • The Ziti edge components provide a secure, Zero Trust entry point into your network
  • The Ziti SDKs allow you to integrate Ziti directly into your applications
  • The Ziti tunnelers and proxies allow existing applications and networks to take advantage of a Ziti deployment

Security Features

  • Zero Trust and Application Segmentation
  • Dark Services and Routers
  • End to end encryption

Performance and Reliability

  • A scalable mesh fabric with smart routing
  • Support for load balancing services for both horizontal scale and failover setups

Developer Focus

Easy Management

Let's break some of these buzzwords down.

Zero Trust/Application Segmentation

Many networking security solutions act like a wall around an internal network. Once you are through the wall, you have access to everything inside. Zero trust solutions enforce not just access to a network, but access to individual applications within that network.

Every client in a Ziti system must have an identity with provisioned certificates. The certificates are used to establish secure communications channels as well as for authentication and authorization of the associated identity. Whenever the client attempts to access a network application, Ziti will first ensure that the identity has access to the application. If access is revoked, open network connections will be closed.

This model enables Ziti systems to provide access to multiple applications while ensuring that clients only get access to those applications to which they have been granted access.

In addition to requiring cert based authentication for clients, Ziti uses certificates to authorize communication between Ziti components.

Dark Services and Routers

There are various levels of accessibility a network application/service can have.

  1. Many network services are available to the world. The service then relies on authentication and authorization policies to prevent unwanted access.
  2. Firewalls can be used to limit access to specific IP or ranges. This increases security at the cost of flexibility. Adding users can be complicated and users may not be able to easily switch devices or access the service remotely.
  3. Services can be put behind a VPN or made only accessible to an internal network, but there are some downsides to this approach.
    1. If you can access the VPN or internal network for any reason, all services in that VPN become more vulnerable to you.
    2. VPNs are not usually appropriate for external customers or users.
    3. For end users, VPNs add an extra step that needs to be done each time they want to access the service.
  4. Services can be made dark, meaning they do not have any ports open for anyone to even try and connect to.

Making something dark can be done in a few ways, but the way it's generally handled in Ziti is that services reach out and establish one or more connections to the Ziti network fabric. Clients coming into the fabric can then reach the service through these connections after being authenticated and authorized.

Ziti routers, which make up the fabric, can also be dark. Routers locoated in private networks will usually be made dark. These routers will reach out of the private network to talk to the controller and to make connections to join the network fabric mesh. This allows the services and routers in your private networks to make only outbound connections, so no holes have to opened for inbound traffic.

Services can be completely dark if they are implemented with a Ziti SDK. If this is not possible a Ziti tunneler or proxy can be colocated with the service. The service then only needs to allow connections from the local machine or network, depending on how close you colocate the proxy to the service.

End to End Encryption

If you take advantage of Ziti's developer SDKs and embed Ziti in your client and server applications, your traffic can be configured to be seamlessly encrypted from the client application to server application. If you prefer to use tunnelers or proxy applications, the traffic can be ecnrypted for you from machine to machine or private network to private network. Various combinations of the above are also supported.

End-to-end encryption means that even if systems between the client and server are compromised, your traffic cannot be decrypted or tampered with.

Getting started with Ziti

If you are looking to jump right in feet first you can follow along with one of our up-and-running quickstart
. The quickstart will leverage Amazon Web Services (AWS) and will have you
launch an AMI which will get you up and running in no time.

This environment is perfect for evaluators to get to know Ziti and the capabilities it offers. The environement was not
designed for large scale deployment or for long-term usage. If you are looking for a managed service to help you run a
truly global, scalable network browse over to our website at http://netfoundry.io to learn more.

The CodeSee Map below is a good way to get familiar with the Ziti codebase:

CodeSee map of this codebase
Get a quick visual overview of the major areas of our repo!


The Ziti project welcomes contributions including, but not limited to, code, documentation and bug reports.

Ziti was developed and open sourced by NetFoundry, Inc. NetFoundry continues to fund and contribute to Ziti.

Build status



Resources to learn more about our technology and community.

Project listed on October 10, 2021