Production edge · Live today

The web server that doesn’t wait on Apache.

Velox is a purpose-built edge for PHP and static sites. Direct FastCGI. Explicit routing. Page-cache at the edge. No mod_rewrite tax on every request.

See the numbers How it works
−6% to −15% vs LiteSpeed on PHP paths
4.9ms homepage p50 (BookOrb)
~1ms static assets (edge cache)

The problem

Apache was the middleman you paid for twice.

On a modern edge, every request that still touches Apache pays a proxy hop, .htaccess evaluation, and rewrite churn — even when PHP-FPM is already ready.

Legacy path Slow

Client
↓
Edge
↓
Apache :7081
.htaccess / mod_rewrite
↓
PHP-FPM

Velox Fast

Client
↓
Velox (native)
try_files · page-cache · rules
↓
PHP-FPM

Measured in production

Fair fight: same app, same host, LiteSpeed vs Velox.

BookOrb on www.bookorb.com — Interlink on :8444, LiteSpeed on :443. Same public hostname, real TLS SNI, HTTP/2, identical PHP 8.3 docroot. Single-request p50 over 30–120 samples (27 Jun 2026).

Path Type LiteSpeed p50 Velox p50 Δ
Homepage / PHP 5.20ms 4.91ms −5.6%
/genre/fiction PHP 4.66ms 4.23ms −9%
/books/…harry-potter PHP 5.04ms 4.31ms −15%
/search?q=love PHP 4.60ms 4.06ms −12%
/css/app.css Static 1.25ms 0.96ms −23%
/img/og-default.png Static 1.27ms 1.65ms +30%

Source: /root/velox/velox-bench/reports/interlink-vs-litespeed-bookorb.html. Interlink wins single-request latency on every PHP path. Static is at parity (~1ms). LiteSpeed still leads sustained PHP throughput on loopback with integrated LSPHP workers (~594 vs ~436 rps) — honest caveat, not hidden.

Fleet migration (Apache proxy era)

After LiteSpeed: beating the Apache middleman.

Once the fleet moved LiteSpeed → Apache → Velox, the win is removing the proxy hop. Same FPM pools, both returning HTTP 200 (July 2026).

Path Apache :7081 Velox Gain
/charity/ 91–155ms 17–18ms ~6–8×
/dictionary/woman/ 42–72ms 15–28ms ~2–3×
/upgrade/ (billing) 72–82ms 22–30ms ~3×
CRM login / API health 16–27ms 12–21ms edge tax gone
Fleet log (OK responses) — p50 9ms steady-state

Apache figures are the residual proxy path (veloxd → httpd → FPM), not LiteSpeed. App-level bugs (e.g. a dead glob() on /members/) are excluded — those are optimisations, not edge wins.

Capabilities

Built for real PHP estates.

Front controllers, pretty URLs, Basic Auth, page-cache SEO farms, and payment flows — without pretending every site is a static SPA.

01

Direct FastCGI

Talks to the same PHP-FPM pools Apache used — no reverse-proxy detour, no mod_fcgid tax.

02

Explicit routing

try_files, catch_script, pretty_php, and script_rules replace sprawling .htaccess trees with reviewable config.

03

Edge page-cache

Serve on-disk HTML for SEO long-tails with zero PHP. PropertyPulse-class traffic stays idle on FPM.

04

HTTP Basic Auth

Native htpasswd support for protected tools and guest portals — no Apache AuthType required.

05

Instant rollback

Per-site proxy fallback stays one config line away. Migrate carefully; never paint yourself into a corner.

06

Security at the edge

Deny rules for UA, path prefixes/suffixes, and dotfiles — before a request ever reaches PHP.

Architecture

One process. Public ports. Native apps.

Velox owns :80 and :443. Apache remains only where it must — Roundcube webmail and offline holdouts — not in the hot path for applications.

TLS · HTTP/2 · HTTP/3-ready edge public :443
Velox route · cache · deny · auth
PHP-FPM pools per-site sockets
Static assets & page-cache no PHP
“Measured the fair way — same hostname, real TLS — Interlink wins single-request latency on every BookOrb PHP path against LiteSpeed.”
BookOrb side-by-side · 27 Jun 2026 · velox-bench
31 Native vhosts (PHP + redirects)
10 Remaining Apache proxies (webmail + nexus)
~210 MB Velox RSS vs ~543 MB residual httpd

Next

Ship the edge your apps deserve.

Velox is the production edge behind LinkCentre, CompanyPulse, PropertyPulse, 3Syxty, and the Interlink CRM estate.

Request a briefing Review benchmarks