bfenetworks/bfe

Health v2 · maintenance only

Adoption not part of the score

6261 stars · 947 forks observed · 2026-08-28

What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-29, confidence not recorded

BFE (Beyond Front End) is a modern layer 7 load balancer and reverse proxy written in Go, originally developed at Baidu and now a CNCF sandbox project. It provides content-based routing, load balancing, and traffic management, with a control plane (API server, config agent, dashboard) and a Kubernetes Ingress controller.

Use cases

• layer 7 load balancing for http services
• content-based routing of traffic to backend servers
• reverse proxy for microservices
• kubernetes ingress controller
• traffic management and config-driven forwarding rules
• self-hosted alternative to cloud load balancers

When to choose

• you need a programmable layer 7 load balancer with content-based routing
• you want a kubernetes ingress controller backed by a mature proxy engine
• you need config-driven traffic management with a control plane and dashboard
• you prefer a go-based, CNCF-hosted proxy for large-scale traffic forwarding

When to avoid

• you only need simple TCP/UDP layer 4 load balancing
• you want a minimal single-binary proxy without a separate control plane
• your team is already invested in nginx, envoy, or haproxy ecosystems
• you need a lightweight edge proxy for very small deployments

Facets

service · maturity active

load-testing proxy api-gateway http-server routing middleware networking infrastructure-as-code cloud-computing microservices go self-hosted cloud layer7-load-balancer reverse-proxy content-based-routing traffic-management cncf ingress-controller devops linux docker kubernetes

Member repositories

For agents

markdown · JSON · MCP: product_card(name="bfenetworks/bfe")