BFE Ingress Controller
bfe-networks.net
- Free plan
- Open source
- Windows
- macOS
- Linux
- API
- Self-hosted
What BFE Ingress Controller is
BFE Ingress Controller is a self-hosted, open-source Layer 7 load balancer derived from Baidu’s Baidu Front End. It handles HTTP, HTTPS, SPDY, HTTP/2, WebSocket, TLS, gRPC and FastCGI traffic; HTTP/3 is planned. A domain-specific language lets teams write content-based routing rules, while global and distributed balancing, zone awareness, zone-level failure resilience and overload protection help manage traffic. BFE’s plugin framework can add traffic management, security and observability functions. Tenant configurations are isolated from one another. For operations, BFE provides subsystem metrics, troubleshooting and analysis logs, and distributed tracing. The vendor lists integrations with mainstream Layer 4 load balancers and projects including Kubernetes, Prometheus, Jaeger and Fluentd. Installation paths include source, binaries, Go, Snap and Docker. BFE is available under the Apache 2.0 License and is a CNCF sandbox project. It runs on Linux, macOS and Windows, and is available through an API.
Who it suits
BFE suits teams that need self-hosted Layer 7 traffic routing and load balancing. Its tenant isolation, plugin framework and operational visibility may also fit multi-tenant environments and teams integrating with Kubernetes or observability projects.
Good to know, and what to watch
- Supports HTTP, HTTP/2, gRPC and FastCGI.
- Content-based routing rules use a domain-specific language.
- Zone-aware balancing and overload protection are supported.
- Tenant configurations are isolated.
- Provides metrics, logs and distributed tracing.
- HTTP/3 is planned, not listed as supported.
- No plan limits are stated.
- Security issue reports must be sent privately.
Plans
Every plan and priceOpen source
Free plan
Getting started
- Open the BFE Networks website
- Choose an installation path: source, binary, Go, Snap, or Docker
- Deploy BFE in a self-hosted environment
- Configure content-based routing rules
- Connect listed integrations such as Kubernetes or Prometheus
Limits to check
The Open source plan has no stated plan limits. HTTP/3 support is planned rather than listed as available.
The verdict
BFE combines content-based routing with distributed balancing and operational visibility in a self-hosted package. Teams should account for its listed protocol support and installation paths when evaluating fit.
Questions people ask
How much does BFE Ingress Controller cost?
The Open source plan costs nothing.
Is BFE open source?
Yes. It is available under the Apache 2.0 License and is a CNCF sandbox project.
Where can BFE run?
The listed environments are API, Linux, macOS, Windows, and self-hosted deployments.
Which protocols does it support?
BFE supports HTTP, HTTPS, SPDY, HTTP/2, WebSocket, TLS, gRPC, and FastCGI. HTTP/3 is planned.
What installation methods are available?
Documentation lists source, binary, Go, Snap, and Docker installation paths.
What the maker publishes
- API security warning
- Documentation says the management API should be reachable only from an internal network. source
- CNCF status
- BFE is a CNCF Sandbox project, a category CNCF describes as experimental and not yet widely tested in production. source
- Company founded
- LinkedIn lists Baidu as founded in 2000 and having more than 10,001 employees. source
- Company ownership
- Baidu, Inc. is the company behind BFE; LinkedIn lists it as a public software company headquartered in Beijing. source
- Control plane
- The broader BFE system separates BFE Server from API Server, Conf Agent and Dashboard control-plane components. source
- Cookie routing
- Ingress traffic can be routed using cookie conditions. source
- Documentation scope
- Ingress documentation includes deployment, RBAC, configuration, status, route priority, TLS, load balancing, redirects, rewrites, FAQ and annotations. source
- Extensibility
- BFE offers Go plugin modules and a WebAssembly plugin path through a proxy-Wasm host. source
- Header routing
- Ingress traffic can be routed using HTTP header conditions. source
- Host routing
- Ingress traffic can be routed using Host rules. source
- Hot reload
- Configuration reloads are designed to avoid interrupting existing long-lived connections. source
- Independent listing
- Kubernetes documentation lists BFE Ingress Controller as a third-party BFE-based controller and says Kubernetes does not maintain third-party controllers. source
- Installation
- The documentation describes installing from source and provides binary, Go, Snap, and Docker installation paths. source
- Installation methods
- The project documents source, binary, Go, Snap and Docker installation paths. source
- Integrations
- The vendor lists integration with mainstream Layer 4 load balancers and ecosystem projects including Kubernetes, Prometheus, Jaeger, and Fluentd. source
- Integrations
- Official documentation names Kubernetes, Prometheus, Jaeger, Fluentd and mainstream layer-4 load balancers as integrations. source
- Kubernetes API limit
- Kubernetes says the Ingress API is frozen and recommends Gateway API for new development. source
- Kubernetes deployment
- The ingress controller can be installed with kubectl manifests or a Helm 3 chart. source
- License
- BFE is available under the Apache 2.0 License and is a CNCF sandbox project. source
- License
- BFE and the ingress controller are released under the Apache 2.0 license. source
- Limit: documentation gap
- Independent analysis notes that English control-plane documentation was listed as coming soon and operational guidance was thinner than the codebase. source
- Limit: Kubernetes packaging
- Independent analysis characterizes the Kubernetes setup as a kustomize example rather than a managed operator and notes possible cleanup or finalizer troubleshooting. source
- Limit: operational complexity
- Independent analysis says a fleet with API, UI and configuration management requires four separate deployments because the data plane and control-plane components are split. source
- Limit: plugin maintenance
- Independent analysis says compiled Go plugins require rebuilds and redeployments, while WebAssembly plugins add a runtime compatibility layer. source
Checked against the maker's pages on 15 Oct 2026.