twill VS RoadRunner

Since you're asking for PHP, it sounds like you want a framework to build your site with, and to manage content. There's Twill based on Laravel, or Ghost and Wordpress if you want tools in that space.

PHP has a lot of top tier CMSes. IMHO bunch of them are even better than Statamic. Craft CMS (https://craftcms.com/) is a lot more mature database based CMS. Kirby (https://getkirby.com/) is better at flat-file and has a lot better admin interface. Twill (https://twillcms.com/) is better integrated in Laravel and is fully open-source. Statamic mostly feels like it's sitting besides Laravel and they call themselves Laravel based for marketing.

I've worked with Twill before, so I decided to use it for my project: an open, free system with rich features and good support. Why not? :-)

Twill is a great one for content focused admins.

PHP Headless Or you go with a Headless PHP CMS. Some options for that are Bolt CMS, Suru, Twill and ExpressionEngine. A Headless CMS doesn't have any frontend. It can provide you with a REST API or you create it in their template engine and integrate your JS stuff there. There are so many, i can't count them all. You can also search for Cockpit and Strapi.

Perhaps Twill comes close. It supports running it as a headless CMS. However, I am not so sure whether RESTful API's are provided out of the box. But it seems like the Twill (PHP) API allows you to relatively easy create the required REST API's.

I'm building something similar. Intranet/wiki site first and then later going to build the marketing site on top of it. Using Twill: https://twill.io/

So currently I set the goal for myself to learn inertia via https://laracasts.com/series/build-modern-laravel-apps-using-inertia-js and also maybe connect it to twill cms.

Twill

FrankenPHP

why link to the old URL when linking to its redirected one is less confusing?

https://github.com/roadrunner-server/roadrunner#readme (MIT)

Don't follow any advice to use Apache as a reverse proxy, or bundle php with a classic web server.

There are real application servers using an event loop by now, most notably Roadrunner (https://roadrunner.dev), FrankenPHP (https://frankenphp.dev), Laravel Octane (https://laravel.com/docs/10.x/octane#introduction), Swoole Bridge for Symfony (https://github.com/insidestyles/swoole-bridge-bundle).

In general, you can do a lot with OpenSwoole or Roadrunner. They are vastly superior (in a container scenario) to any other suggestion in this thread!

https://roadrunner.dev which golang php application server which can replace nginx +php fpm has a module for running golang via php using sockets.

You could also use something like EventMachine (In ruby), Twisted (Python), Node (JS) or ReactPHP (for PHP) that will use the language and turn it into a web application server, and then you'll have only one long running process that handle all your requests with shared memory. You could even use something more fancy like RoadRunner in the case of PHP.

Have you considered optimizing the Laravel app? I love Go, but full rewrite for such low rate sounds overkill. Have you looked at the RoadRunner PHP application sample, for example?

Has state resetter for long-running workers serving multiple requests such as RoadRunner or Swoole.