The right runtime for your PHP application.
FrankenPHP, NGINX, and Apache serve different application requirements. Choose compatibility first, then validate performance with your own workload.
Compatibility without separate control panels
The web engine belongs to the website configuration and release identity. Changing it should produce a new, reviewable release with a rollback path.
FrankenPHP
Start here for a PHP application without an Apache-specific dependency.
Compatibility checks
- Use conventional request execution unless the application explicitly supports worker mode.
- Long-lived workers must reset request, authentication, and application state safely.
- Check PHP extensions and application lifecycle before choosing concurrency settings.
NGINX + PHP-FPM
Choose a FastCGI deployment when your routing and PHP-FPM requirements are already known.
Compatibility checks
- Translate routing requirements into the supported server configuration.
- NGINX does not execute .htaccess directives.
- Validate static files, front-controller fallback, upload limits, and process capacity.
Apache
Evaluate applications that depend on Apache rewrite rules or supported modules.
Compatibility checks
- Review the actual .htaccess rules and module requirements.
- Avoid assuming arbitrary server configuration is available in shared hosting.
- Test plugin behaviour, redirects, file access restrictions, and document root.
| Engine | Application fit | What to verify | Availability |
|---|---|---|---|
| FrankenPHP | PHP applications; worker mode when the application supports it | Validate application lifecycle and long-lived worker behaviour | Planned |
| NGINX + PHP-FPM | FastCGI PHP applications and static sites | Configure document root, routing rules, and PHP-FPM limits | Planned |
| Apache | PHP or static applications with Apache-specific requirements | Validate modules, rewrite rules, and .htaccess behaviour | Planned |
Decide from requirements before benchmarking
Inventory the current application and identify the requirement that would prevent it from running on another engine. A measured performance difference is useful only after functional behaviour, routing, uploads, authentication, and scheduled work have been validated.
Treat an engine change as a release
Changing the web engine changes the runtime assumptions. Build a staging release with the new configuration, verify the same requests and background work, and keep the previous artifact and configuration available. Recheck database compatibility before any rollback.
Bring your PHP application, choose the runtime it needs, and keep releases, domains, and operations together in your Orisite panel.
