Ross ROSS = Recommend OSS · open-source software intelligence for agents

ChrispyBacon-dev/DockFlare

DockFlare: Automate Cloudflare Tunnels with Docker Labels observed · 2026-08-28

github.com/ChrispyBacon-dev/DockFlare · homepage · Python · NOASSERTION (other) observed · 2026-08-28

Health v2 · maintenance only

85/100

  • Activity 99
  • Release rhythm 96
  • Longevity 36

Flags: no_license no_readme

How is this computed?

round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-02. Adoption (stars, forks) is never an input.

  • gap_med: 5
  • age_days: 508
  • days_rel: 28
  • days_push: 9
  • n_releases_24m: 38

Full methodology

Adoption not part of the score

2407 stars · 107 forks observed · 2026-08-28

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

DockFlare is a self-hosted Python/Flask application that watches Docker container events and automatically manages Cloudflare Tunnel ingress rules, DNS records, and Zero Trust access policies from Docker labels. It includes a web UI, multi-server agent architecture, OAuth/OIDC identity provider management, and automatic cleanup when containers stop.

Use cases

  • automatically expose docker containers via cloudflare tunnel
  • manage cloudflare tunnel ingress rules from docker labels
  • auto-create and delete cloudflare dns records for containers
  • apply cloudflare zero trust access policies per container
  • manage tunnels across multiple docker hosts
  • replace manual cloudflare dashboard configuration for self-hosted services
  • secure homelab services with oauth or oidc authentication

When to choose

  • you self-host many docker services behind Cloudflare and want label-driven automation
  • you want tunnel routing, DNS, and Zero Trust policies managed in one tool
  • you run containers across multiple hosts and need a central tunnel control plane
  • you want automatic cleanup of DNS and access rules when containers stop

When to avoid

  • you don't use Cloudflare for DNS or tunnels
  • you need a general-purpose ingress controller or reverse proxy independent of Cloudflare
  • you prefer fully declarative infrastructure-as-code over a label-driven daemon
  • your environment has no access to the Docker socket or Cloudflare API

Facets

application · maturity active

networking security configuration-management deployment workflow-automation networking self-hosted security self-hosted python cloudflare-tunnel cloudflare-zero-trust docker-labels reverse-proxy ingress-controller dns-automation homelab flask web-ui devops containers docker linux

9 sources

Member repositories

RepositoryRoleHealth v2
ChrispyBacon-dev/DockFlaremain85

For agents

markdown · JSON · MCP: product_card(name="ChrispyBacon-dev/DockFlare")

Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem