Python SDK for OpenZiti
Getting Started • Examples • Support • Contributing • License
The Python SDK for OpenZiti is a library that enables you to integrate zero trust network connectivity into your Python applications, and establish secure connections with remote network resources over an OpenZiti network. The SDK also simplifies the process of adding secure, zero-trust network connectivity built into your Python application. It's so simple that it can be done in just two lines of code!
OpenZiti is an open-source project that provides secure, zero-trust networking for applications running on any platform.
More specifically, the SDK allows you to integrate zero trust at the application level. This means your data is never exposed outside the application environment providing you with end-to-end encryption for ultimate security. See other zero trust models here.
Getting Started
See the get started guide to learn how to deploy your own overlay.
Or, you can try CloudZiti for free, check out more here.
Installing the SDK
The Python SDK for OpenZiti is distributed via the Python Package Index (PyPI) and can be installed using
pip package manager.
pip install openziti
Using Ziti Python SDK
With just two lines of code, you can turn your plain old web server into a secure, zero-trust embedded application. Below is an example of just how simple it is to get started.
Provide a hostname, and port for your application, a simple monkey patch, and you're ready to go. You don't even need to know what a monkey patch is! However, if you're interested in what a monkey patch is, expand the block below.
What is Monkey Patching?
Monkey patching allows developers to modify functionality for code even when they may not have access to the original source code. Because Python has a dynamic object model allowing developers to modify objects at runtime. Monkey patching allows developers to point a function call to any function they want. We can even implement our own function that doesn't exist in the source code.
The way this Python SDK uses monkey patching is to override existing functionality in socket handling by the socket module.
Taking a look at the code below, the key lines are the last two. You can see how, for each monkey patched function, we're telling that function call on the
sockobject to be directed to the function held in_patch_methods. Therefore, this SDK can be used on any application that doesn't manage its own sockets.def __init__(self, **kwargs): self.orig_socket = sock.socket sock.socket = _patchedSocket(kwargs) self.orig_methods = {m: sock.__dict__[m] for m, _ in _patch_methods.items()} for m_name, _ in _patch_methods.items(): sock.__dict__[m_name] = _patch_methods[m_name]
cfg = dict(ztx=openziti.load('/path/to/identity.json'), service="name-of-ziti-service")
openziti.monkeypatch(bindings={('127.0.0.1', 8000): cfg})
Or try our decorator pattern with a function annotation
@openziti.zitify(bindings={('127.0.0.1', 18080): {'ztx': '/path/to/identity.json', 'service': 'name-of-ziti-service'}})
def yourFunction():
The binding dictionary configures what happens when the code tries to open a server socket. Standard network addresses
are mapped to ziti service configurations. For example, with his configuration
bindings = {
('0.0.0.0', 8080): { 'ztx': 'my-identity.json', 'service':'my-service' }
}
when application opens a server socket and binds to address 0.0.0.0:8080 it will actually bind to the ziti service named my-service.
Binding addresses can be specified with tuples, strings, or ints(ports). ('0.0.0.0', 8080), '0.0.0.0:8080', ':8080', 8080
are all considered and treated the same.
Examples
Try it out yourself with one of our examples
Support
Looking for Help?
Please use these community resources for getting help. We use GitHub issues for tracking bugs and feature requests and have limited bandwidth to address them.
- Read the offical docs
- Join our Developer Community
- Participate in discussion on Discourse
Contributing
Do you want to get your hands dirty and help make OpenZiti better? Contribute to the OpenZiti open-source project through bug reports, bug fixes, documentation, etc. Check out our guide on contributing to our projects here.
License
2 maintainers
Metadata
2 maintainers
Release files for openziti 1.7.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| openziti-1.7.1.tar.gz | 39.1 kB | With provenance | Details |
Release files / openziti-1.7.1.tar.gz
| Download URL | openziti-1.7.1.tar.gz |
|---|---|
| Size | 39.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1c403a4391f41d91a84d5c7ae6d415d0c3403d0c18636d46786ce2fc910fd96f
|
|
BLAKE2b-256 checksum How to use checksums |
bf466f1c133453270e46db20966b501b83f8c5c5706aabce8500d5b0693d21c9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 30, 2026.
Transparency logSecurity for openziti 1.7.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 1 file in this release has been uploaded with provenance metadata.
Attestation for openziti-1.7.1.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 30, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
