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

hintjen/selfhosted-gateway resource

Self-hosted Docker native tunneling to localhost. Expose local docker containers to the public Internet via a simple docker compose interface. observed · 2026-08-28

github.com/hintjen/selfhosted-gateway · homepage · Shell · AGPL-3.0 (copyleft) observed · 2026-08-28

Health v2 · maintenance only

38/100

  • Activity 13
  • Release rhythm 35
  • Longevity 100

Flags: no_releases

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: n/a
  • age_days: 1452
  • days_rel: n/a
  • days_push: 523
  • n_releases_24m: 0

Full methodology

Adoption not part of the score

1734 stars · 87 forks observed · 2026-08-28

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

A self-hosted, Docker-native tunneling solution that exposes local Docker Compose services to the public Internet via WireGuard tunnels with NGINX (gateway) and Caddy (client). It is a FOSS alternative to Cloudflare Tunnels, Tailscale Funnel, and ngrok, built entirely from existing open-source components with automatic HTTPS certificate provisioning.

Use cases

  • expose local docker containers to the public internet
  • self-host behind CGNAT or double-NAT like Starlink
  • replace ngrok or Cloudflare Tunnel with a self-hosted alternative
  • access home lab services without port forwarding or a static IP
  • hide my home IP address while self-hosting apps
  • automatically provision HTTPS certificates for self-hosted services
  • proxy TCP and UDP traffic to localhost through a VPS

When to choose

  • you self-host services behind CGNAT, double-NAT, or a dynamic IP
  • you want a fully self-hosted, code-free alternative to Cloudflare Tunnels or ngrok
  • your services are already defined in docker-compose and you want Docker-native integration
  • you want automatic Let's Encrypt/ZeroSSL HTTPS without extra tooling

When to avoid

  • you don't have (or want to run) a publicly addressable VPS as a gateway
  • you need a managed service with zero infrastructure to maintain
  • your services are not containerized or not managed via Docker Compose
  • you need features like access control policies or application-level analytics offered by commercial tunnels

Facets

infra-config · maturity active

networking proxy security self-hosted deployment networking self-hosted privacy self-hosted cli wireguard tunneling reverse-proxy caddy nginx docker-compose cgnat vps-gateway https sni devops containers linux docker

3 sources

Member repositories

RepositoryRoleHealth v2
hintjen/selfhosted-gatewaymain38

For agents

markdown · JSON · MCP: product_card(name="hintjen/selfhosted-gateway")

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