Reproxy
reproxy.io
- Free plan
- Windows
- macOS
- Linux
- API
- Self-hosted
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 configuration, files, Docker, or Consul Catalog, and the Docker provider can discover running containers automatically. It supports automatic Let’s Encrypt certificates, user-provided certificates, and TLS termination. Traffic controls include health checks, failover, load balancing, response caching, and rate limiting. Per-route basic authentication and IP-based access control restrict routes. Reproxy can serve static assets with an optional single-page-application mode. An optional management server exposes route information and Prometheus metrics. External plugins run as separate processes or containers through RPC. DNS-01 certificate challenges support Cloudflare and AWS Route53. Distribution options include a self-contained binary, Docker image, and Debian or RPM packages. Listed x86_64 and ARM builds support Linux, macOS, and Windows. The container runs as root by default, and documentation recommends a less-privileged user when Docker discovery is unnecessary. The project is under active development and may introduce breaking changes before version 1.
Who it suits
Reproxy suits operators deploying a self-hosted reverse proxy with configurable routing, TLS, discovery, and traffic controls. It supports Linux, macOS, and Windows deployments through listed binaries and images.
Good to know, and what to watch
- Supports Docker and Consul routing providers
- Automates Let’s Encrypt certificates
- Includes health checks and load balancing
- Offers route authentication and IP controls
- Provides Prometheus metrics
- Container runs as root by default
- Forwarded IP headers can be spoofed
- Project may have breaking changes before version 1
- Self-hosted deployment is required
The verdict
Reproxy combines reverse-proxy routing, certificate management, discovery, traffic controls, static serving, and extensibility in a self-hosted package. Operators should account for its default container privileges and active pre-1.0 development status.
What the maker publishes
- Access controls
- It supports per-route basic authentication and IP-based access control. source
- Access controls
- It supports IP-based route restrictions and global or per-route basic authentication. source
- Container security
- The container runs as root by default, and the documentation recommends using a less-privileged user when Docker discovery is not needed. source
- Distribution
- It is distributed as a self-contained binary and Docker image, with packages for Debian and RPM systems. source
- Distribution
- Reproxy is distributed as a self-contained binary and Docker image, with Homebrew installation and Debian and RPM packages also documented. source
- Docker discovery
- Its Docker provider can automatically discover running containers and configure them as routing destinations. source
- Extensibility
- It supports external plugins implemented as independent processes or containers using RPC. source
- Health and balancing
- Reproxy provides live health checks and fail-over/load-balancing for destinations. source
- Integrations
- For DNS-01 certificate challenges, it supports Cloudflare and AWS Route53. source
- Integrations
- Documented service-discovery integrations include Docker and Consul Catalog; SSL DNS challenge providers include Cloudflare and AWS Route 53. source
- Management
- The management server provides route information and Prometheus metrics. source
- Monitoring
- Its optional management server exposes route information and Prometheus metrics. source
- 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. source
- Purpose
- Reproxy is an HTTP(S) edge server and reverse proxy that routes requests to destination servers. source
- Purpose
- Reproxy is an HTTP(S) edge server and reverse proxy that routes requests to destination servers using configured providers. source
- Routing providers
- It supports static, file, Docker, and Consul Catalog providers for routing rules. source
- Routing providers
- The documented providers are static, file, Docker, and Consul Catalog, and multiple providers can be used at once. source
- 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. source
- Service discovery
- Its Docker provider can automatically discover running containers as routing destinations. source
- SSL
- It supports automatic Let’s Encrypt certificates and user-provided certificates. source
- Static assets
- It includes a static assets server with an optional SPA-friendly mode. source
- Static assets
- It includes a static assets server with an optional SPA-friendly mode. source
- Supported systems
- The binary and image support Linux, macOS, and Windows on listed x86_64 and ARM architectures. source
- Supported systems
- The installation documentation lists Linux, macOS, and Windows builds, including x86_64 and ARM variants for some systems. source
Checked against the maker's pages on 5 Oct 2026.