HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
sozu-proxy
sozu
Rust2017–2026
sozu-proxy / sozu

sozu

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

Web DevelopmentSecurity & PrivacyLanguages & CompilersLearning & ReferenceNetworking
Explore on GitHubRead Hacker News discussions
9Distinct people
10Mentions
0Explicit recommenders
3.8KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

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

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 1:49:46 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year10 dated mentions

Observed mentions: 2017-05-18 19:10:44 UTC to 2026-05-19 21:23:37 UTC.

012342017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments20172018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments20212022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 4 mentions; 2 submissions, 2 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC110
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC101
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC000
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC000
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC000
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC000
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC303
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC000
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC422
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC101

What Hacker News says

10 sources
Shine-neko·May 19, 2026
Hi HN, Sōzune is a reverse proxy I've been building on top of Sōzu (https://github.com/sozu-proxy/sozu), the Rust proxy from Clever Cloud. Sōzu is fast and reload-without-downtime, but it's a low-level building block — you talk to it over a socket and feed it config. Sōzune wraps it with the part most people actually want from a proxy in 2026: it discovers your services automatically (Docker/Podman labels, Swarm, Kubernetes Ingress + Gateway API, Nomad, an HTTP endpoint, or a plain YAML file), provisions and renews Let's Encrypt certs, and applies every change live with no restart. The mental model is Traefik, but the data plane is Sōzu instead of a Go proxy. That's the bet I'd most like feedback on. Try it: # compose.yaml services: sozune: image: kemeter/sozune:latest ports: ["80:80", "443:443"]
Read the rest
volumes: - /var/run/docker.sock:/var/run/docker.sock whoami: image: traefik/whoami labels: - "sozune.enable=true" - "sozune.http.whoami.host=whoami.localhost" docker compose up -d curl -H "Host: whoami.localhost" http://localhost What works today: HTTP/HTTPS/WebSocket/raw TCP, HTTP/2 over ALPN, wildcard + regex hostnames, header rewriting, method-based routing, forwardAuth (Authelia/Authentik), Docker HEALTHCHECK-gated readiness, and a dashboard for diagnostics. What's deliberately not there yet: DNS-01 / wildcard certs, IPAllowList, per-router TLS options, GRPCRoute/TCPRoute on the Gateway API. The roadmap is public and honest about the gaps. Questions I'd genuinely like answered: - Is "Traefik UX on a Sōzu data plane" a reason to switch, or a curiosity? What would make it a reason? - For people running Traefik/Caddy/nginx in prod: what's the one feature whose absence is a hard no? - Anyone running Sōzu directly — does a higher-level layer on top help or get in your way? Repo: https://github.com/kemeter/sozune — Site & docs: https://sozune.kemeter.io — MIT licensed. I'll be around all day to answer.
In Sōzune – a reverse proxy built on Sōzu, with Traefik-style autodiscovery
qweqwe14·Mar 2, 2025
Have you heard of axum[1] or actix-web[2]? What does this do that existing Rust web servers don't? I think the "web server" ecosystem in Rust is pretty mature by now, so you should probably state in what way your project is novel on the website. Edit: OK, I realized that this is supposed to be an nginx/caddy replacement, so a complete, configurable web server/proxy. Maybe check out https://github.com/memorysafety/river or https://github.com/sozu-proxy/sozu [1] https://docs.rs/axum [2] https://docs.rs/actix-web
In Show HN: I built a memory-safe web server in Rust
samsquire·Apr 20, 2023
This is interesting, thank you. I really should learn from BEAM and the OTP and learn Erlang. I get the feeling it's super robust and reliable and low maintenance. I wrote a userspace multithreaded scheduler which distributes N lightweight threads to M kernel threads. https://github.com/samsquire/preemptible-thread I recently wrote a JIT compiler and got lazy compilation of machine code working and I'm nowhere near beginning optimisation https://github.com/samsquire/compiler How do you write robust software, that doesn't crash when something unexpected goes on? I looked at sozo https://github.com/sozu-proxy/sozu and I'm thinking how to create something that just stays up and running regardless.
In More optimizations in the compiler and JIT

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.