Start from your situation, see what Ferron looks like there, then explore what matches.
Best for: homelab, personal services, small-team apps
A single binary for proxying, TLS, and observability: readable configuration with predictable behavior, and debugging with a single grep.
Ferron configuration:
# TLS certificate is obtained automatically by Ferron
example.com {
proxy http://localhost:3000
}Covered: ntfy and Jellyfin examples, automatic TLS, and observability.
Best for: WordPress, hosting panels, PHP-FPM fleets
Deploy Ferron as an LSCache-compatible accelerator in front of Apache, PHP, or WordPress. Edge caching and declarative config with request visibility via trace IDs and built-in metrics.
Ferron configuration:
example.com {
root /var/www/html
fcgi_php "unix:///var/run/php/php-fpm.sock"
}Covered: caching proxy versus direct PHP-FPM, control panels, and performance.
For most general use cases
Debug production issues with correlated trace IDs, built-in observability, and configuration diagnostics. Built for operators replacing Apache, NGINX or Caddy.
Planned Ingress alternative
Route traffic to Kubernetes with built-in observability and automatic TLS.
Compare configuration patterns in the docs, then try Ferron on your machine.