Reproxy

Free plan APILinuxMacSelf-hostedWindows

What Reproxy is

Reproxy is a self-hosted HTTP(S) edge server and reverse proxy that routes requests to destination servers. Routing rules can come from static files, file providers, Docker, or Consul Catalog. Its Docker provider discovers running containers and configures them as destinations. Reproxy supports automatic Let’s Encrypt certificates, user-provided certificates, and TLS termination. Health checks, failover, load balancing, response caching, and rate limiting provide traffic controls. Per-route basic authentication and IP-based access control restrict routes. An optional management server exposes route information and Prometheus metrics, while a static assets server includes an optional SPA mode. External plugins run as separate processes or containers through RPC. DNS-01 challenges support Cloudflare and AWS Route53. Distribution includes a self-contained binary, Docker image, and Debian or RPM packages for Linux, macOS, and Windows on listed x86_64 and ARM architectures.

Who it suits

It suits teams deploying a self-hosted proxy for containerized or traditional services. It is relevant when routing, TLS, health checks, and metrics are managed directly.

What it does well

Supports Docker and Consul routing providers
Automatic and user-provided TLS certificates
Includes health checks and load balancing
Offers route-level access controls
Provides Prometheus metrics

What to know first

Container runs as root by default
Forwarded IP headers can be spoofed
Project may introduce breaking changes before version 1
Self-hosted deployment requires administration

Limits

Reproxy is under active development and may have breaking changes before version 1. Its container runs as root by default, and forwarded IP headers require control by a trusted proxy to avoid spoofing.

Getting started

Visit the Reproxy website
Choose a self-contained binary, Docker image, Debian package, or RPM package
Deploy it on Linux, macOS, or Windows using a supported architecture
Select static, file, Docker, or Consul Catalog routing
Configure certificates through Let’s Encrypt or provide your own
Add health checks, access controls, caching, or rate limiting as needed

Verdict

Reproxy provides routing, TLS, traffic management, and extensibility in a self-hosted package. Its active development brings current changes, so configuration may need adjustment before version 1.

Questions

Is Reproxy free?

Yes. Reproxy has a free plan.

Where can Reproxy run?

Its binary and image support Linux, macOS, and Windows on listed x86_64 and ARM architectures.

How is Reproxy deployed?

Reproxy is self-hosted and distributed as a binary, Docker image, Debian package, or RPM package.

Can Reproxy discover Docker containers?

Yes. Its Docker provider can automatically find running containers and use them as routing destinations.

Which DNS providers support DNS-01 challenges?

Reproxy lists Cloudflare and AWS Route53 support for DNS-01 certificate challenges.

Facts from Reproxy's own pages

Access controls: It supports IP-based route restrictions and global or per-route basic authentication. · reproxy.io, 5 Oct 2026
Container security: The container runs as root by default, and the documentation recommends using a less-privileged user when Docker discovery is not needed. · reproxy.io, 4 Oct 2026
Distribution: Reproxy is distributed as a self-contained binary and Docker image, with Homebrew installation and Debian and RPM packages also documented. · reproxy.io, 5 Oct 2026
Docker discovery: Its Docker provider can automatically discover running containers and configure them as routing destinations. · reproxy.io, 5 Oct 2026
Extensibility: It supports external plugins implemented as independent processes or containers using RPC. · reproxy.io, 4 Oct 2026
Health and balancing: Reproxy provides live health checks and fail-over/load-balancing for destinations. · reproxy.io, 5 Oct 2026
Integrations: Documented service-discovery integrations include Docker and Consul Catalog; SSL DNS challenge providers include Cloudflare and AWS Route 53. · reproxy.io, 5 Oct 2026
Management: The management server provides route information and Prometheus metrics. · reproxy.io, 5 Oct 2026
Monitoring: Its optional management server exposes route information and Prometheus metrics. · reproxy.io, 4 Oct 2026
Project status: The project says it is under active development and may have breaking changes before version 1; it describes version 0.4.x as suitable for real-life use. · reproxy.io, 5 Oct 2026
Purpose: Reproxy is an HTTP(S) edge server and reverse proxy that routes requests to destination servers using configured providers. · reproxy.io, 5 Oct 2026
Routing providers: The documented providers are static, file, Docker, and Consul Catalog, and multiple providers can be used at once. · reproxy.io, 5 Oct 2026
Security: The documentation recommends running the container as a less-privileged user when Docker discovery is not needed and warns that forwarded IP headers can be spoofed unless controlled by a trusted proxy. · reproxy.io, 5 Oct 2026
Service discovery: Its Docker provider can automatically discover running containers as routing destinations. · reproxy.io, 4 Oct 2026
SSL: It supports automatic Let’s Encrypt certificates and user-provided certificates. · reproxy.io, 4 Oct 2026
Static assets: It includes a static assets server with an optional SPA-friendly mode. · reproxy.io, 5 Oct 2026
Supported systems: The installation documentation lists Linux, macOS, and Windows builds, including x86_64 and ARM variants for some systems. · reproxy.io, 5 Oct 2026
TLS: Reproxy supports automatic SSL certificates through ACME/Let’s Encrypt and user-provided certificates. · reproxy.io, 5 Oct 2026
Traffic management: It supports health checks, failover, and load balancing. · reproxy.io, 4 Oct 2026

Where Reproxy stands on Freedom251

Reverse Proxy Software#21 of 33