• Docs
  • Talk to an expert
Blog
Blog
BlogProductCase studiesNewsInsights
Blog

Run FrankenPHP on Upsun, without managing the runtime

FrankenPHPPHPBlackfireperformanceautoscaling
18 November 2026
Share
This post is also available in German and in French.

TL;DR

  • FrankenPHP is now a managed runtime on Upsun for PHP 8.2 to 8.5.
  • Set type: frankenphp:1.8.5 and deploy. The runtime is managed and optimized for you by Upsun.
  • Classic mode is the default and behaves like PHP-FPM (FastCGI Process Manager). Worker mode is supported for applications built for it.
  • Available on Flex and Fixed projects at no extra cost.

FrankenPHP offers a different way to run PHP. In worker mode, your application boots once and stays in memory, handling request after request without starting each time again. For applications built for it, that can mean lower response times and less compute for the same traffic.

Getting there has meant becoming your own runtime team: assembling FrankenPHP yourself, sizing workers and threads by hand, wiring up profiling, and keeping it allall of it patched. FrankenPHP is now a managed runtime on Upsun, so that work is no longer yours.

From a hand-built setup to a runtime type

Until now, running FrankenPHP on Upsun meant the composable image: add FrankenPHP as a package, then write and maintain your own start command. The FrankenPHP-specific parts of that setup looked like this (abridged):

applications:
  app:
    type: "composable:<version>"
    stack:
      packages:
        - "frankenphp"
    web:
      commands:
        start: frankenphp php-server --worker $PLATFORM_DOCUMENT_ROOT/index.php --listen=localhost:$PORT --root=$PLATFORM_DOCUMENT_ROOT

Now you set the runtime type, and Upsun builds, patches, and optimizes FrankenPHP for your container:

applications:
  app:
    type: frankenphp:1.8.5

Versions 1.8.2 to 1.8.5 give you PHP 8.2 to 8.5 respectively, and follow PHP's own end-of-life policy. The image has been running in production on Upsun since August 2026, and Blackfire's own documentation site runs on it with PHP 8.5.

What Upsun takes off your hands

  • No manual worker tuning. Workers and threads are sized automatically to your container's CPU and memory, with tuned defaults that you can extend with your own FrankenPHP and Caddy configuration.
  • Less runtime maintenance. Security updates and runtime fixes are delivered in the managed image, so your team does not have to track FrankenPHP releases or maintain its own build.
  • Profiling without setup. Blackfire credentials and the profiling probe are delivered automatically, including in worker mode, so you can measure the effect of any change. Continuous Profiling is supported when enabled on the project.
  • Autoscaling in both modes. Upsun autoscaling works in classic and worker mode.

Classic mode or worker mode?

FrankenPHP does not automatically make every application faster. Classic mode performs like PHP-FPM. The major performance opportunity comes from worker mode, where applications built for it stay in memory between requests.

Classic mode is the default. It handles each request the way PHP-FPM does, so your application runs unchanged. It gives you a supported, current FrankenPHP runtime today, with no code changes, and lets you decide about worker mode on your own schedule.

Worker mode is where the gains can be significant. The PHP Foundation, citing an analysis by Sylius, the e-commerce platform, reports response times around 80% lower and more than six times fewer machines in worker mode. Those are their numbers, measured under their conditions. Upsun has not yet published its own benchmark, and results depend on your application and container size.

What worker mode asks of your application

Because the application stays in memory, so does its state. Static variables, class static properties, global variables, and in-memory caches persist between requests. Symfony, Laravel and Yii integrate FrankenPHP; other applications may need cleanup logic. FrankenPHP's worker mode documentation explains what to reset between requests, and Igor, a third-party static analysis tool built for FrankenPHP's worker mode, can help you audit a Symfony application before you switch.

Container size matters too. A worker configuration tuned for several cores has little room to show its value on a small instance with a fraction of a CPU.

A sensible path is to start in classic mode, profile with Blackfire, and move to worker mode when the numbers tell you to.

Availability and pricing

The managed FrankenPHP runtime is available on Flex and Fixed projects at no extra cost. As with every runtime on Upsun, you pay for the resources your container uses.

Two things to know before you start. New Relic is not supported because its PHP extension has no thread-safe build and cannot load in FrankenPHP; Blackfire is the supported profiler. If you already run FrankenPHP on the composable image, your application keeps running as is, and you can move to the managed runtime when you choose. There is no migration guide yet.

Get started

Set the type in your application configuration and deploy. Read the FrankenPHP documentation for configuration options, including worker mode.

Stay updated

Subscribe to our monthly newsletter for the latest updates and news.

Deploy possibility.
Try Upsun for free.

Build with DispatchDeploy on Cloud