# Traefik Proxy

The Cloud Native Application Proxy

Repository: https://github.com/traefik/traefik
Canonical: https://ross.abutalabs.com/products/traefik-proxy
Homepage: https://traefik.io
Language: Go
License: MIT
License Family: permissive
Topics: microservice, docker, marathon, mesos, consul, etcd, kubernetes, load-balancer, reverse-proxy, zookeeper, letsencrypt, golang, go, traefik
Last push: 2026-08-26T13:29:23+00:00

## Health v2 (maintenance only)
Score: 95/100 (v2, computed 2026-09-03T02:39:23.370411+00:00)
- activity 99, release rhythm 87, longevity 100
- inputs: {"age_days": 4007, "days_push": 7, "days_rel": 7, "gap_med": 0.0, "n_releases_24m": 113}
- flags: none
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 64607, forks 6160 (observed 2026-08-28T04:12:19.228558+00:00)

## What it is
Traefik is a cloud-native HTTP reverse proxy and load balancer written in Go that automatically discovers services from orchestrators like Kubernetes, Docker, Consul, and Etcd and dynamically generates routes. It includes a web UI, automatic TLS via Let's Encrypt, and middleware support, and ships with an official Helm chart for Kubernetes deployment.

## Use cases
- expose kubernetes microservices with automatic ingress routing
- reverse proxy for docker containers with auto-discovery
- load balancer with automatic letsencrypt certificates
- edge router for microservices that reconfigures itself dynamically
- replace nginx with a proxy that reads service registries like consul or etcd
- deploy an ingress controller on kubernetes via helm
- route http traffic to services that scale up and down many times a day

## When to choose
- you run containers or microservices on an orchestrator and want zero-touch routing
- you need automatic TLS certificate management with Let's Encrypt
- you want a built-in dashboard and dynamic configuration without reloads
- you deploy on Kubernetes and prefer a Helm-installable ingress controller

## When to avoid
- you need a lightweight static reverse proxy with hand-written config files
- you require advanced layer-7 features of a full API gateway like complex quota or billing
- your environment has no dynamic service discovery and changes rarely

## Facets
- artifact type: service
- maturity: stable
- function: proxy, api-gateway, routing, middleware, http-server, service-discovery, configuration-management
- domain: microservices, cloud-computing, networking, self-hosted, infrastructure-as-code
- platform: windows, go, self-hosted, cloud
- tags: reverse-proxy, load-balancer, letsencrypt, edge-router, ingress, helm-chart, service-mesh-adjacent, auto-discovery, load-balancing, devops, containers, docker, kubernetes, linux, macos

## Member repositories
- traefik/traefik (main) score 95
- traefik/traefik-helm-chart (infra) score 95

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:12:19.228558+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-29T16:17:25.323839+00:00, confidence not recorded.
  - readme: https://github.com/traefik/traefik (fetched 2026-08-28T04:12:19.228558+00:00, sha 03697ac6e286)
- Data as of 2026-08-30T08:39:29.467469+00:00.