Documentation

Pertisk Proxy Docs

Run the Pingora + HTTP/3 reverse proxy or Kubernetes Ingress controller.

Overview

Pertisk Proxy is a shared data plane built on Cloudflare Pingora (HTTP/1.1 + HTTP/2) and Quiche (HTTP/3). Run it as a file-driven reverse proxy or as a Kubernetes Ingress controller that watches Ingress resources.

Modes

Standalone reverse proxy

Configure sites and upstreams from files, then expose an admin plane for HTTPS sites and edge rules.

Kubernetes Ingress controller

Deploy with Helm. The controller watches Ingress objects and programs the same Pingora + HTTP/3 data plane used in standalone mode.

Edge chain

Requests can pass through:

  1. GeoIP — location-aware routing or blocking
  2. WAF — request filtering
  3. Bot score — automated traffic signals
  4. Captcha — challenge when scores require it

Deploy

Use the Helm chart for multi-arch cluster installs. For standalone, start from the example config in the repository and point DNS at the proxy listeners.

helm install pertisk-proxy ./charts/pertisk-proxy