# loxilb-io/loxilb

eBPF based cloud-native load-balancer for Kubernetes|Edge|Telco|IoT|XaaS.

Repository: https://github.com/loxilb-io/loxilb
Canonical: https://ross.abutalabs.com/products/loxilb
Homepage: https://www.loxilb.io
Language: Go
License: Apache-2.0
License Family: permissive
Topics: cloud-native, ebpf, edge, golang, k8s, networking, hybrid-cloud, kubernetes, public-cloud, nat, nat64, service-loadbalancer, network-security, sctp, kubernetes-networking, loadbalancing, ingress, network-proxy, 5g, 6g
Last push: 2026-08-26T00:29:17+00:00

## Health v2 (maintenance only)
Score: 94/100 (v2, computed 2026-09-03T02:20:16.233290+00:00)
- activity 99, release rhythm 84, longevity 100
- inputs: {"age_days": 1528, "days_push": 8, "days_rel": 26, "gap_med": 31.5, "n_releases_24m": 11}
- flags: none
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 1871, forks 147 (observed 2026-08-28T04:05:46.923014+00:00)

## What it is
loxilb is an open-source, eBPF-based cloud-native load-balancer written in Go, designed to work across on-prem, public-cloud, and hybrid Kubernetes environments. It provides service type load-balancing (L4 by default, with L7 support) and handles telco/edge protocols like GTP, SCTP, and SRv6.

## Use cases
- provide service type loadbalancer for on-prem kubernetes clusters
- replace kube-proxy with an eBPF-based alternative
- load balance SCTP and GTP traffic for 5G telco workloads
- run a self-managed load balancer instead of cloud provider LB
- deploy load balancing at the edge for IoT and mobility
- bring your own load balancer to EKS or other managed k8s
- do NAT64 and NAT translation with eBPF

## When to choose
- you run self-managed or on-prem Kubernetes and need a service type loadbalancer
- you need high-performance L4 load balancing with eBPF
- your telco/5G workloads involve SCTP, GTP, or other exotic protocols
- you want a single LB solution across on-prem, public cloud, and hybrid environments

## When to avoid
- you only need a simple L7 reverse proxy and are happy with nginx or envoy
- you need a fully managed cloud-provider load balancer
- your environment does not support eBPF (older kernels, non-Linux platforms)

## Facets
- artifact type: service
- maturity: active
- function: networking, proxy, api-gateway
- domain: networking, cloud-computing
- platform: self-hosted, go
- tags: ebpf, l4-load-balancer, l7-load-balancer, service-type-loadbalancer, nat64, sctp, gtp, edge-computing, telco, 5g, hybrid-cloud, ingress, kube-proxy-alternative, load-balancing, containers, kubernetes, devops, telecommunications, linux, docker

## Member repositories
- loxilb-io/loxilb (main) score 94

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:05:46.923014+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-30T03:15:01.901988+00:00, confidence not recorded.
  - readme: https://github.com/loxilb-io/loxilb (fetched 2026-08-28T04:05:46.923014+00:00, sha 6a2581cffca6)
  - homepage: https://www.loxilb.io (fetched 2026-08-29T10:53:59.528689+00:00, sha 9111e5537b1e)
- Data as of 2026-08-30T08:39:29.467469+00:00.