Side by side
Airlock Microgateway vs BFE Ingress Controller
Both stand on kubernetes ingress controllers. Which one you can start free with, which one lets you read the code, and what each costs once you pay.
Free plan APISelf-hosted
Visit Airlock Microgateway Free plan Open source APILinuxMac+2
Choose BFE if you need a free, self-hosted Layer 7 load balancer with content-based routing and tenant isolation. Its balancing and observability features make it suited to deployments that need those controls. Look elsewhere if you require HTTP/3 support now or a deployment model other than self-hosted.
Visit BFE Ingress ControllerThe facts
| Airlock Microgateway | BFE Ingress Controller | |
|---|---|---|
| Free plan | Yes | Yes |
| Open source | Not published | Yes |
| Runs on | API, Self-hosted | API, Linux, Mac, Self-hosted, Windows |
| Lowest paid plan | Free or on request | Free or on request |
| Plans published | 3 | 1 |
| Maker | Not published | Not published |
| Website | airlock.com | bfe-networks.net |
| On kubernetes ingress controllers | #6 of 28 | #2 of 28 |
Airlock Microgateway: what it does well
BFE Ingress Controller: what it does well
- Open-source under the Apache 2.0 License.
- Supports HTTP, HTTP/2, WebSocket, gRPC, and FastCGI.
- Provides global, distributed, and zone-aware load balancing.
- Tenant configurations are isolated from other tenants.
- Includes metrics, logs, and distributed tracing.
What to know first
- HTTP/3 is planned rather than listed as supported.
- Deployment is self-hosted.
Alternatives to Airlock Microgateway Alternatives to BFE Ingress Controller The whole list

