How FrankenPHP Is Transforming PHP with Real‑Time, Multi‑Language and Cloud‑Native Power

Overview

FrankenPHP is a high‑performance application server built on top of the Caddy web server. It has been added to the official PHP organization on GitHub, providing a cloud‑native runtime for PHP applications.

Native Real‑Time Support

FrankenPHP embeds the Mercure protocol, which implements Server‑Sent Events (SSE) and WebSub. By exposing a //.well-known/mercure endpoint, PHP code can publish topics directly, and browsers or other clients receive push updates without any external WebSocket or message‑broker component.

In a benchmark performed by an e‑commerce platform, order‑status notifications that previously required a separate Node.js WebSocket service (average latency ≈ 1.2 s) were reduced to under 0.3 s after migrating to FrankenPHP with Mercure.

Multi‑Language Integration via FFI

FrankenPHP enables PHP scripts to call compiled Go, C, or C++ libraries through PHP’s Foreign Function Interface (FFI) . The typical workflow is:

Compile the performance‑critical code as a shared library (e.g., libcompute.so for Linux or compute.dll for Windows).

Expose the required symbols with a C header.

Load the library in PHP using FFI::cdef().

Example:

$ffi = FFI::cdef(
    "int add(int a, int b);",
    "libadd.so"
);
$result = $ffi->add(2, 3); // $result == 5

This approach lets developers implement CPU‑intensive tasks—such as image manipulation, cryptographic primitives, or data compression—in a language that offers native speed, while keeping the surrounding application logic in PHP.

Cloud‑Native Deployment

Because FrankenPHP runs as a Caddy module, it inherits Caddy’s built‑in features:

Automatic HTTPS : TLS certificates are obtained and renewed via Let’s Encrypt without manual configuration.

Dynamic certificate management : Supports wildcard and multi‑domain certificates for SaaS platforms.

Service discovery : Caddy can resolve upstream services via DNS, Kubernetes Service names, or Docker network aliases.

FrankenPHP can be containerised with a minimal Docker image. A typical Dockerfile looks like:

FROM php:8.2-cli-alpine AS builder
RUN apk add --no-cache git
# Install FrankenPHP binary from GitHub releases
RUN curl -L https://github.com/dunglas/frankenphp/releases/download/v1.0.0/frankenphp-linux-amd64 -o /usr/local/bin/frankenphp \
    && chmod +x /usr/local/bin/frankenphp

FROM caddy:2-alpine
COPY --from=builder /usr/local/bin/frankenphp /usr/bin/frankenphp
COPY ./src /srv
WORKDIR /srv
EXPOSE 80 443
CMD ["caddy", "run", "--config", "/etc/caddy/Caddyfile"]

When deployed to Kubernetes, the Caddy configuration can reference the frankenphp binary as the upstream handler, allowing seamless scaling, rolling updates, and health‑checking via native Kubernetes probes.

Performance Impact

Early adopters report measurable gains:

Deployment time reduced by ~50 % compared with traditional LAMP stacks, because Caddy handles TLS and routing automatically.

Resource utilization (CPU & memory) increased up to three‑fold, as the single‑process model eliminates the overhead of separate PHP‑FPM and web‑server processes.