Containerized Stack

Dual‑Mode PHP Runtime for Magento

Run Magento on PHP-FPM or Caddy-embedded FrankenPHP, with OPcache sized for Magento, workers sized to your server, and isolated containers.

Two Runtimes, One Image

Every Magento environment includes a PHP container that supports two runtime modes. PHP-FPM is the default: battle-tested, widely documented, and compatible with every Magento extension. FrankenPHP embeds PHP in the Caddy web server and, when the store includes a worker-mode module, keeps Magento loaded in memory between requests. The platform detects that module and configures the workers for you.

You choose the runtime per environment. Both modes ship with OPcache sized for Magento out of the box: a large shared memory pool, room for every class file a big Magento codebase has, and an enlarged interned-strings buffer.

Workers Sized to Your Server

The PHP-FPM worker pool is calculated from the server's RAM and vCPU count at provision time, based on the measured memory a Magento request needs, so PHP gets the most concurrency the server can safely give it without starving the database. Workers are recycled regularly so memory leaks in third-party modules cannot accumulate.

Configurable PHP Versions

Each environment pins its own PHP version, from 8.1 up to 8.5, selected at creation time. Version upgrades happen per-environment, so you can test a new PHP version on staging while production stays where it is. No shared runtime means no version conflicts between environments.

Container Isolation

The PHP container drops every Linux capability it does not need and runs with a read-only root filesystem. Temporary files write to in-memory tmpfs mounts, and sessions live in Redis, so the container can be replaced at any time without losing state. It connects only to its own environment's private Docker network and cannot reach other environments' services. Read the FrankenPHP / PHP-FPM docs for runtime mode and OPcache configuration details.