FrankenPHP review
A focused open-source server for modern PHP applications, containers, and real-time updates.
Reviewed by iTechGuides Editors · Editorial team · Updated Oct 2026
FrankenPHP is an open-source PHP application server built on Caddy. It is aimed at teams running modern PHP applications, including Laravel, Symfony, API Platform, and WordPress, as well as containerized deployments using Docker or Kubernetes. Classic PHP server mode supports conventional applications, while worker mode targets long-running PHP applications. FrankenPHP runs on Linux, macOS, and Windows, with self-hosted deployment options for teams that want control over the serving environment.
Its strongest appeal is the combination of application serving and platform features in one product. FrankenPHP provides automatic HTTPS certificate generation and renewal, native HTTP/2 and HTTP/3 support, structured logging, compression, Prometheus metrics, tracing, hot reloading, and graceful reloads. Standalone self-executable application binaries support portable deployments, while Docker images are available in Debian and Alpine variants. The built-in Mercure hub adds real-time updates, and integrations with Caddy, Laravel, Symfony, API Platform, WordPress, Docker, Kubernetes, and Mercure give it a clear fit within PHP-focused ecosystems.
The main trade-off is its narrow focus. Teams serving PHP applications can benefit from the worker model, framework integrations, and deployment choices, but organizations supporting primarily non-PHP stacks should look for a server designed around broader language coverage. FrankenPHP also places deployment, updates, and operational ownership with the self-hosting team. For real-time features, its documented path is Mercure rather than native WebSocket support, so projects built around WebSocket-specific requirements should evaluate another option. Choose FrankenPHP for PHP applications that need modern protocol support, container workflows, and flexible execution modes; choose an alternative when non-PHP breadth or native WebSockets is central.
FrankenPHP pros and cons
- Where it wins
- Supports classic and worker-mode PHP execution
- Includes HTTP/2, HTTP/3, automatic HTTPS, metrics, and tracing
- Runs through standalone binaries, Docker images, and Kubernetes
- Where it doesn't
- PHP-centered scope limits its fit for non-PHP application stacks
- Self-hosted deployment requires team-managed operations
- Real-time delivery centers on Mercure rather than native WebSockets
FrankenPHP fact sheet, pricing and score →
Advertiser disclosure: iTechGuides is reader-supported. Vendors can pay for top positions in our rankings and for a place on other products' pages, and we may earn a commission when you click some links. Bought places stand at the number bought; this page and our disclosure say so. Paying vendors may get a fuller, more detailed review from our editors, and that review can change their score. How we rank.
Last updated · How we research and update