Skip to the content
Documentation
Help Start
Reading in:
  • German: 9,059 of 9,059 pages
About the help in other languages
All help pages

Web servers and engines in the ecosystem

The ways an Exponential site is served - Velocity with its Qbix, FrankenPHP and PHP built-in engines, and the traditional servers Apache, Nginx, LiteSpeed, Caddy, IIS, lighttpd, H2O and Traefik - with what each is for.

Download as PDF

Address: https://doc.exponential.earth/exphelp/viewer/help/ecosystem/php-stack/web-servers-and-engines.md

On this page

Web servers and engines in the ecosystem

"Exponential runs behind any web server that can rewrite a URL" and "does not require any particular one" (README.md, "How Exponential is served").

Warning

.htaccess slows down every request. When .htaccess files are enabled (AllowOverride anything but None), let alone used, Apache looks for them and reads and evaluates them on every request, in every directory of the path, and page loading times go up drastically (measured). The only real fix is to switch the feature off for the virtual host: AllowOverride None in the HTTPS virtual host, and the rules in the virtual host's own configuration as mod_rewrite rules. That is far faster in production speed tests and well worth the time it takes to optimize a production configuration. Switch over right away: copy the rules of the example HTTPS virtual host into your virtual host (with the static cache, also staticcache_offload.conf), set AllowOverride None, run apachectl configtest, reload Apache and test the site. The same rules for other servers: nginx, LiteSpeed, Caddy, IIS, Velocity (built in); where virtual host rules go in a control panel: Plesk, cPanel, DirectAdmin, ISPConfig. On LiteSpeed or OpenLiteSpeed, the server's own page cache can also answer anonymous visitors and crawlers without PHP: Page caching with LiteSpeed and OpenLiteSpeed.

Contents

  1. Velocity and its engines
  2. Traditional servers
  3. Choosing

Velocity and its engines

EngineRole
QbixVelocity's own server; "The recommended engine for every stage, from development to production, and the fastest"
FrankenPHP"The production-ready alternative"
PHP's built-in serverFor development; "the shipped default because it always works"

More: Exponential Velocity, Velocity engines.

Traditional servers

ServerHow it rewritesNotes from the README
Apache HTTP Servermod_rewrite, .htaccess"The most widely used; .htaccess ships with Exponential"
Nginxtry_files / rewriteRules in the server block
LiteSpeed, OpenLiteSpeed.htaccess-compatibleReads Apache rules in most cases
Caddyrewrite / handle / try_filesAutomatic HTTPS
Microsoft IISURL Rewrite Module (web.config)Windows hosting
lighttpdmod_rewriteSmall footprint
H2Oredirect / file.custom-handlerHTTP/2 focused
TraefikReplacePathRegexUsually in front of another server

PHP's built-in server with php -S is "Development only [...] Never expose it to the internet" (README.md).

Choosing

SituationChoice
Your own server or VMVelocity with the Qbix engine
You prefer a Caddy-based single binaryVelocity with FrankenPHP
Shared hosting without long-lived processesApache or LiteSpeed with .htaccess
Several customers needing operating-system isolationOne Velocity instance per site, or per-site PHP-FPM pools
A tuned Nginx or Apache already in frontKeep it; Velocity can run behind it

Source: README.md, "When a traditional server is still the right answer". Hosting models: Hosting companies: start here.

Become an Exponential Partner

Partners share their information, provide funding, contribute back and develop the products with us, and that is how Exponential grows. A partner website and dashboard are planned for mid-2027: please become a partner today to speed up our growth rate and land new features faster.

Something wrong on this page? Report an error

Documentation license

This documentation is free documentation, licensed under the GNU Free Documentation License 1.3 or later.

Exponential Copyright © 1998-2026 Exponential Foundation and 7x