Notice: Ferron 2.0.0 is currently in beta.
Ferron is a fast web server with automatic TLS certificate management, easy configuration, and rock-solid security — so you can go live in minutes.
Command unavailable
Designed with modern web hosting needs in mind, Ferron combines speed, security, and ease of use in one powerful package.
Thoroughly optimized for speed with support for high concurrency.
Built with memory safety as a priority, eliminating common security vulnerabilities.
Seamless SSL/TLS certificate acquisition and renewal with Let's Encrypt integration.
Simple, intuitive configuration with sensible, secure defaults and comprehensive documentation.
Advanced reverse proxy capabilities with support for load balancing and health checks.
Built-in support for modern API patterns including WebSockets.
Ferron can outperform other popular web servers in performance benchmark tests across different workloads.
Higher is better | Benchmarks run on AMD Ryzen 5 8600G, 32GB RAM, with the ferrbench -c 1000 -d 60s -t 12 -h https://localhost --http2
command
Higher is better | Benchmarks run on AMD Ryzen 5 8600G, 32GB RAM, with the ferrbench -c 1000 -d 60s -t 12 -h https://localhost --http2
command
Lower is better | Benchmarks run on AMD Ryzen 5 8600G, 32GB RAM, with the ferrbench -c $CONCURRENCY -d 60s -t 12 -h https://localhost --http2
command
Higher is better | Benchmarks run on AMD Ryzen 5 8600G, 32GB RAM, with the ferrbench -c 100 -d 60s -t 12 -h https://localhost --http2
command
Get started with Ferron in minutes. Choose your preferred platform and installation method.
Command unavailable
Ferron has simple, intuitive configuration, compared to more complex configurations of some popular web servers.
server {
listen 80;
listen 443 ssl http2;
server_name example.com;
server_tokens off;
# Assuming you use Certbot for automatic certificate management
ssl_certificate /etc/letsencrypt/live/example.com/fullchain.pem;
ssl_certificate_key /etc/letsencrypt/live/example.com/privkey.pem;
root /var/www/html;
gzip on;
location / {
try_files $uri $uri/ =404;
}
}
// TLS certificate is obtained automatically by Ferron
example.com {
root "/var/www/html"
}
upstream backend {
server localhost:3000;
keepalive 32;
}
server {
listen 80;
listen 443 ssl http2;
server_name example.com;
server_tokens off;
# Assuming you use Certbot for automatic certificate management
ssl_certificate /etc/letsencrypt/live/example.com/fullchain.pem;
ssl_certificate_key /etc/letsencrypt/live/example.com/privkey.pem;
location / {
proxy_pass http://backend/;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection 'upgrade';
proxy_set_header Host $host;
proxy_cache_bypass $http_upgrade;
}
}
// TLS certificate is obtained automatically by Ferron
example.com {
proxy "http://localhost:3000"
}
server {
listen 80;
listen 443 ssl http2;
server_name example.com;
server_tokens off;
# Assuming you use Certbot for automatic certificate management
ssl_certificate /etc/letsencrypt/live/example.com/fullchain.pem;
ssl_certificate_key /etc/letsencrypt/live/example.com/privkey.pem;
root /var/www/html;
index index.php index.html index.htm;
location / {
gzip on;
try_files $uri $uri/ =404;
}
location ~ \.php$ {
fastcgi_split_path_info ^(.+\.php)(/.+)$;
fastcgi_pass unix:/var/run/php/php-fpm.sock;
set $path_info $fastcgi_path_info;
fastcgi_param PATH_INFO $path_info;
fastcgi_index index.php;
# The "fastcgi.conf" is located in the NGINX configuration directory (at least on Debian-based systems)
include fastcgi.conf;
}
}
// TLS certificate is obtained automatically by Ferron
example.com {
root "/var/www/html"
// Check if the PHP-FPM socket file is accessible by the web server user, often "ferron"
fcgi_php "unix:///var/run/php/php-fpm.sock"
}
Ferron can automatically obtain TLS certificates for your website, making it easy to secure your site with HTTPS.
Don't take our word for it — hear from the system administrators and developers who use Ferron every day.
I suspect that people don't like changing web servers, and perhaps that's why it took the industry so long to move away from Apache. Ferron actually looks great — great performance, automatic TLS, easy reverse proxy configuration and more. Congrats on shipping this!
Join many administrators and developers using Ferron to deliver content faster, more securely, and with less overhead.