korridor fits if…
- You publish web applications and want to keep the traffic on your premises.
- You currently maintain several tools for proxying, WAF and authentication.
- You want a readable, versioned configuration.
korridor use case
Publishing applications with a self-hosted reverse proxy
A reverse proxy, a web application firewall, an authentication proxy and an ACME client: four tools to configure, update and monitor separately.
The short answer
korridor combines reverse proxy, TLS certificates, web application firewall and per-user access control in a single piece of software installed on your Linux machines. Its configuration is a versioned, signed file, verified before every change is applied.
Publishing without assembling a stack
Applications are served over TLS, with certificates issued and renewed automatically, without opening port 80.
- HTTP/1.1, HTTP/2 and HTTP/3 reverse proxy
- Load balancing across several servers, with circuit breaking
- WebSocket and streaming without per-route configuration
- Static site hosting with caching and compression
Filtering before the application
Requests are filtered and access is checked before they reach your servers.
- Coraza WAF and OWASP rules, enabled route by route
- Rate limiting, country filtering and reputation lists
- Access policy re-evaluated on every request
- Portal compatible with your identity provider (OIDC)
Is it the right tool for you?
Limits to know
- korridor installs on a Linux machine or VM (amd64 or arm64).
- High availability requires two machines.
- Pricing is still being defined.