FrankenPHP integrates PHP into a server based on Caddy. It can serve traditional PHP requests and offers worker mode, which boots application code once and handles multiple requests with persistent process state. That can reduce startup overhead but changes assumptions made by code written for short-lived requests.
Deployments may use Docker images, package-managed builds or standalone executables. Static or mostly static builds can bundle the PHP interpreter and extensions, so a host-level PHP package update may not change the code that FrankenPHP is executing.
In worker mode, state outside the request handler can persist across requests. Framework integrations and application code must reset request-specific data carefully to prevent unintended data sharing or stale state.
Track the FrankenPHP build and embedded PHP version together, rebuild or replace affected images or executables after a security release, and verify the actual server process.