// the take
gobetween is a standalone L4 load balancer/reverse proxy written in Go, handling TCP, TLS termination, and UDP traffic with pluggable backend discovery (Consul, Docker, DNS SRV, LXD, exec scripts, etc.). It's aimed at ops teams who want a single static binary instead of wiring up HAProxy or nginx stream modules for simple TCP/TLS routing.
The discovery backend list is unusually broad for a project this size — Consul, Docker/Swarm, LXD, DNS SRV, and even arbitrary exec scripts or regex-parsed plaintext HTTP responses, so it slots into odd infra setups without a sidecar. SNI-based routing plus TLS passthrough and termination in the same binary covers a common multi-tenant TCP case that plain nginx stream config handles awkwardly. iphash1 (sticky hashing that tolerates backend removal without reshuffling other clients) is a detail most lightweight LBs skip. Single static Go binary with a REST API for live config/stats is genuinely low-ops.
The README states it's in maintenance mode, accepting PRs only — the last push was over a year ago, so don't expect new features or fast CVE turnaround, and you're on your own for anything beyond what's already there. It's strictly L4: no HTTP path/header routing, no L7 observability, so it doesn't replace Traefik/Envoy/nginx for anything app-aware. There's no built-in HA or clustering story — it's a single process, so you need your own failover (keepalived, DNS, or an external LB in front) for production redundancy. The project's community and ecosystem (docs on a wiki, no Helm chart or k8s-native integration mentioned) are thin compared to HAProxy or Envoy, so debugging obscure issues means reading the Go source yourself.
We read the README, the directory tree and a key source file in October 2026. Nobody pays to be listed. How we judge →