Gufo Tower
A native management and deployment tool for NOC.
Documentation: https://docs.gufolabs.com/gufo_tower/
Source Code: https://github.com/gufolabs/gufo_tower/
Gufo Tower is a native management and deployment tool for NOC.
Tower is designed for system administrators who manage NOC infrastructure. A NOC node can be a physical server or a virtual machine, and Tower provides a simple way to deploy, configure, upgrade, and manage NOC installations ranging from a single node to clusters of hundreds of nodes.
Tower provides centralized management of NOC nodes, making it easy to maintain consistent configurations and operate NOC infrastructure at any scale.
Installation
To install Tower, run the installation script:
curl https://sh.gufolabs.com/tower | sh -s -- venv
The script creates a Python virtual environment and installs Tower into it. See the Installation Guide for other installation methods and detailed instructions.
Usage
After installation, open the Tower web interface at:
http://<IP>:8888/
where <IP> is the IP address of the host running Tower.
Follow the instructions in the web interface to deploy and manage NOC nodes.
On Gufo Stack
Gufo Tower is a part of the Gufo Stack.
Gufo Stack is a collaborative effort led by Gufo Labs. Its goal is to create a robust and flexible set of tools for building network management software and automating routine administration tasks.
The stack extracts key technologies proven in NOC and develops them as independent packages. These components provide reusable functionality for networking, asynchronous I/O, error handling, storage, monitoring, and other common tasks.
NOC uses the resulting components as external dependencies, while other network management products can benefit from them as well.
Gufo Tower complements this ecosystem by providing a simple and reliable way to deploy and manage NOC as a native application.
Metadata
Release files for gufo-tower 2.0.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| gufo_tower-2.0.0.tar.gz | 2.7 MB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| gufo_tower-2.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 7.4 MB
Release files / gufo_tower-2.0.0.tar.gz
| Download URL | gufo_tower-2.0.0.tar.gz |
|---|---|
| Size | 2.7 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5891837f4921be5cc2a05a900feedba6ee64c907fb258856e0188c5c676aeb78
|
|
BLAKE2b-256 checksum How to use checksums |
42711543cabeefb6ca66c660e06181f5fd04b15a99d12988fe99807304d767ed
|
| 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 Sep 23, 2026.
Transparency logRelease files / gufo_tower-2.0.0-py3-none-any.whl
| Download URL | gufo_tower-2.0.0-py3-none-any.whl |
|---|---|
| Size | 4.7 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4d28ad059a5f03b97cc9eaae4c0688b51f94933413bcd4cfa9bc3c48a629c334
|
|
BLAKE2b-256 checksum How to use checksums |
44646c11a7a7f6bbbfd34decc6733f3b6aa269241a5d7e71e25ab9a120178147
|
| 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 Sep 23, 2026.
Transparency log