FrankenPHP vs PHP-FPM: A Practical Comparison for Modern PHP Hosting

FrankenPHP and PHP-FPM both execute PHP, but they follow very different architectures and operational models that directly affect performance, deployment simplicity, and how you design your applications. Understanding these differences helps you choose the right runtime for classic, shared-nothing PHP apps or for modern, long-running, high-performance workloads.

Core Architectural Differences

PHP-FPM follows the classic multi-process model: a web server such as Nginx or Apache receives the HTTP request and forwards it to a separate PHP-FPM process pool over FastCGI, where each request is handled in an isolated process. FrankenPHP embeds the PHP runtime directly inside the Caddy web server (written in Go), running as a single integrated application server instead of two separate components.

In PHP-FPM, every request starts from a clean slate: the framework is bootstrapped, configuration is loaded, services are wired, and then torn down again at the end of the request, which is the traditional shared-nothing PHP lifecycle. FrankenPHP offers two modes: in classic mode it behaves similarly to FPM, while in worker mode it keeps the application loaded in memory and reuses it across many requests, allowing state and connections to persist.

Performance and Resource Usage

Because PHP-FPM uses a separate web server and communicates over FastCGI, there is inherent overhead from inter-process communication and repeated application bootstrapping on every request, even though the model is very well-tuned and stable. Benchmarks show that in classic mode, FrankenPHP and an Nginx+PHP-FPM stack deliver almost identical throughput and latency, with differences small enough to be irrelevant for most real-world workloads.

The real performance leap appears when FrankenPHP runs in worker mode: the PHP engine, autoloader, framework bootstrap, and even database connections can be initialized once and reused, significantly reducing response times and increasing requests per second for cleanly developed apps. In some high-throughput tests, FrankenPHP can serve several times more requests per second than traditional PHP-FPM because it avoids per-request initialization and process spawning overhead.

Configuration and Operational Simplicity

PHP-FPM usually means maintaining two layers of configuration: the web server’s virtual hosts, TLS, HTTP/2 or HTTP/3 settings, plus the separate PHP-FPM pool configuration, process limits, and FastCGI tuning, which can be powerful but also complex. FrankenPHP simplifies this by bundling the application server and web server into one modern binary, leveraging Caddy’s automatic HTTPS, HTTP/3 support, and straightforward configuration files for a single-stack deployment.

This integrated approach fits particularly well with containerized environments, because one FrankenPHP image can provide both the web server and PHP runtime instead of orchestrating separate Nginx/Apache and PHP-FPM containers. For teams that prefer declarative, minimal configuration and quick dev-to-prod parity, FrankenPHP’s all-in-one nature often leads to simpler CI/CD pipelines and fewer moving parts to debug.

Developer Responsibilities and Application Design

One of the biggest advantages of PHP-FPM’s shared-nothing model is safety: memory leaks, stale globals, or unexpected side effects are naturally contained because each request runs in a fresh process that exits afterwards. This makes it easier to run legacy or complex applications without refactoring for long-lived workers, and it reduces the risk of subtle state-related bugs under load.

With FrankenPHP in worker mode, developers gain speed at the cost of responsibility: global state, static variables, caches, and persistent connections live across requests, so they must be carefully managed to avoid leaks or data contamination between users. Modern, framework-driven code that already plays well with Octane-style or Swoole-style long-running processes is usually a good fit, while older apps may require adjustments to become worker-safe.

Docker Image Usage

FrankenPHP images (e.g., from dunglas/frankenphp) simplify deployment as a standalone app server ideal for Laravel or Symfony, with built-in static file serving. PHP-FPM images (e.g., php:8.3-fpm) pair with official Nginx/Apache images for customizable, production-proven setups.​

Conclusion: Not Just a “Drop-In” Decision

In classic mode, FrankenPHP behaves much like a drop-in replacement for PHP-FPM, with performance so close that the difference is usually negligible in real applications. The more important factors become operational simplicity, built-in modern features, and whether you plan to evolve towards worker-mode, stateful, high-performance PHP services.

If you prioritize compatibility, isolation, and a proven deployment pattern, PHP-FPM remains a robust and familiar choice. If you are aiming for a modern, integrated, performance-oriented stack with real-time features and Go-powered extensions, FrankenPHP is an exciting alternative that pushes PHP closer to contemporary application server designs.