Pintle
Route local development domains through one HTTPS reverse proxy
A Go reverse proxy for local development with Docker and file routes, TLS termination, SNI passthrough and an embedded dashboard. Its optional static-only mode serves loopback routes without Docker discovery.
Visit Pintle → View the changelog →Getting started
Read Pintle quick-start →Requirements
- Local TLS certificates from mkcert and route configuration
- Linux x64 for the public binary, or Docker/source build for another supported setup
Things to know
- Host-native port redirection requires administrator privileges
- Static-only mode serves loopback HTTP routes without Docker discovery or TCP routing
- The routes file check validates destination syntax only, not upstream reachability or certificates
A local proxy that reads existing labels
Pintle routes local HTTPS domains to development services. Its source accepts Pintle, Traefik and Caddy label formats, reads static route files, and can pass an SNI domain through to another proxy. The embedded dashboard and GET /api/self describe the running local configuration.
The public homepage and Linux download provide the binary, checksum and full setup guide. Extracting the archive starts no service and does not install a certificate authority. The source setup guide also covers other-platform builds and Docker use. The optional static-only mode serves loopback HTTP routes and omits Docker discovery, TCP listeners and SNI passthrough.