Inside the router

One process, from incoming connection to container backend.

Follow the request path

HTTP and HTTPS listeners feed the middleware chain, which handles routing policy and forwards requests to the selected backend pool. Docker discovery updates route state alongside this request path.

Internet :80 / :443
        │
        ▼
  TLS + middleware
        │
        ▼
  Host / path router ◀── Docker discovery
        │                 │
        ▼                 ▼
    Backend pool      Docker socket
        │
        ▼
    Your containers

A standard-library runtime

DockRouter is implemented in Go using the standard library. The runtime does not need a separate configuration service or a hosted control plane. The marketing website is a separate Next.js application.

Leave connections open when they need to be

The proxy supports WebSocket upgrades and streaming HTTP responses, including server-sent events. Responses are streamed rather than accumulated as complete bodies before forwarding.

Know the deployment boundaries

DockRouter is a Docker ingress router, not a container orchestrator. Your deployment still owns networking, DNS, storage, application authorization, backups and host security. Automatic discovery needs access to the Docker daemon.