Zipwebport -

Ready to try ZipWebPort? Here is a basic implementation using the open-source reference library (fictional example, but illustrative).

Prerequisites: Docker, a web app running on port 3000.

Step 1: Install the ZipWebPort CLI

curl -sSL https://get.zipwebport.io/install.sh | sh

Step 2: Create a Configuration File (zwp-config.yaml)

listen: ":443"  # Secure port
upstream: "http://localhost:3000" # Your app
compression:
  algorithm: "zstd"
  level: 3  # Speed vs. ratio
  dictionary: "/var/lib/zwp/dicts/web_common.bin"
security:
  tls_cert: "/etc/ssl/zwp/cert.pem"
  tls_key: "/etc/ssl/zwp/key.pem"
  enforce_mtls: false
tunneling:
  max_packet_size: 4096
  keepalive: 30s

Step 3: Launch the ZipWebPort Daemon

sudo zipwebport start --config zwp-config.yaml

Step 4: Test the Tunnel Use curl with the special --zipwebport flag (or a compatible client library):

curl --zipwebport https://localhost:443/api/data

You will notice the Content-Encoding: zwp header in the response, confirming the compression tunnel is active. zipwebport

ZipWebPort is available in three editions:

System administrators can script ZipWebPort to perform nightly database dumps. Instead of saving the dump locally (consuming storage), ZipWebPort pipes the compressed output directly to an S3-compatible object store. This reduces the backup server’s disk footprint by nearly 50%. Ready to try ZipWebPort