sozu-proxy/sozu

Sōzu HTTP reverse proxy, configurable at runtime, fast and safe, built in Rust. It is awesome!

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 36 minutes ago
Added to GitGenius on September 18th, 2026
Created on January 18th, 2017
Open Issues & Pull Requests: 72 (-4)
GitHub issues: Enabled
Number of forks: 215
Total Stargazers: 3,730 (+0)
Total Subscribers: 39 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 17.0 hours
Mean response time: 218.7 days
90th percentile: 799.3 days
Tracked items: 140

Most active contributors

Sign in to see contributor activity.

How this project is maintained

Roughly one issue in five opened in the past year never receives a reply. 39% of open issues come from outside the core team, a mix of external reports and the maintainers' own roadmap. Work labelled "integration" is answered fastest, typically in about 24 hours, while "h2" waits about 8 days. Only 59% of issues opened in the past year have been closed. Three people close 93% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 41
New in 7 days: 16
Closed in 7 days: 3
Avg open age: 1,189 days
Stale 30+ days: 26
Stale 90+ days: 21

Recent activity

Opened in 7 days: 16
Closed in 7 days: 3
Comments in 7 days: 6
Events in 7 days: 8

Top labels

  • enhancement (63)
  • integration (15)
  • h2 (14)
  • router (10)
  • bug (9)
  • tls (9)
  • documentation (8)
  • metrics (8)

Detailed Description

Sōzu is a lightweight HTTP reverse proxy server built in Rust that can be reconfigured at runtime without restarting.

The tool addresses the operational burden of traditional reverse proxies that require restarts for configuration changes or upgrades. Sōzu solves this through hot configuration: it accepts configuration updates via secure Unix sockets while continuing to process requests. The proxy can upgrade itself in place without dropping connections, remaining always-up during the entire process. It handles TLS termination for backend servers, supporting multiple cryptographic backends at compile time including ring, AWS-LC with post-quantum and FIPS 140-3 options, and OpenSSL. Performance is optimized through Rust's memory safety guarantees and zero-copy HTTP parsing via the Kawa library, which translates HTTP messages without unnecessary data duplication.

Sōzu suits teams running services that cannot tolerate downtime during proxy updates or configuration changes, particularly those managing infrastructure where frequent redeployment is costly. It works well for deployments requiring TLS termination at the edge while keeping backend servers focused on application logic. The tool's sandboxed worker processes provide defense-in-depth even if a worker is compromised. Organizations needing post-quantum cryptography or FIPS compliance can select the appropriate compile-time feature. The project includes sozu top, a live terminal dashboard for monitoring cluster status, backend health, and HTTP/2 flood-mitigation metrics in real time.

The project maintains a steady release cadence with pre-built binaries for multiple Linux targets and architectures, Docker images published to Docker Hub, and cryptographic signatures via sigstore keyless signing and SLSA build provenance. Development activity shows consistent attention to security practices and cross-platform support, with explicit handling of edge cases like musl libc compilation on ARM64. The maintainers actively document deployment scenarios and provide comprehensive command-line tooling alongside the core proxy functionality.