Velocity packages, Docker images and binaries
This page is for administrators who install Velocity outside an Exponential installation: as a system service, a container or a single binary. An Exponential installation already has the engine through Composer and needs none of this (see From Exponential). Applies to Exponential Velocity 0.0.4.28 and later.
Pick a form
Every Velocity release is published in the forms people actually install:
| Form | For |
|---|---|
Composer package se7enxweb/exponential-velocity | Exponential installations (the usual way; Exponential's exp:velocity finds the engine in vendor/) |
| deb and rpm packages | A system service on Debian 12 and 13, Ubuntu 22.04 and 24.04, Enterprise Linux 9 and 10, using the distribution's own PHP |
Docker images on ghcr.io/se7enxweb/exponential-velocity | Containers, amd64 and arm64, one image per PHP version and variant |
| Static binaries | One file with PHP built in: Linux x86-64 and aarch64, macOS arm64, Windows x64 |
The phar sbin/qbixserver.phar | The server as one PHP archive, run by any PHP 8.0+ (8.1+ before release 0.0.4.54) |
| A source kit | A build kit for a platform, architecture or PHP version no release covers |
All files of a release carry checksums in SHA256SUMS.
Why use it
You choose the form that fits the machine instead of building anything: apt or dnf for a server, Docker for a platform, a single file for a laptop or an appliance. The extension set is defined once (the extension baseline), so every form is checked against the same list, and qbixctl ext:check tells you what a given PHP lacks and the exact command that installs it.
Operating-system packages
curl -LO https://github.com/se7enxweb/exponential-velocity/releases/download/v<release>/exponential-velocity_<release>-1+deb12_all.deb
sudo apt install ./exponential-velocity_<release>-1+deb12_all.deb # Debian, Ubuntu
sudo dnf install ./exponential-velocity-<release>-1.el9.noarch.rpm # EL 9, on the stock PHP 8.0
sudo dnf install ./exponential-velocity-<release>-1.el10.noarch.rpm # EL 10| Distribution | Package | PHP |
|---|---|---|
| Debian 12 | exponential-velocity_<release>-1+deb12_all.deb | 8.2 |
| Debian 13 | ...+deb13_all.deb | 8.4 |
| Ubuntu 22.04 | ...+ubuntu22.04_all.deb | 8.1 |
| Ubuntu 24.04 | ...+ubuntu24.04_all.deb | 8.3 |
| EL 9 | exponential-velocity-<release>-1.el9.noarch.rpm | 8.0, the default AppStream PHP (the package depends on php-cli >= 8.0; no module stream needed, a newer one still works) |
| EL 10 | ...el10.noarch.rpm | 8.4 |
The packages are architecture-independent (the server is PHP). Nothing starts on install. Start the service when the configuration is ready:
sudo systemctl enable --now exponential-velocity
systemctl status exponential-velocity
sudo systemctl reload exponential-velocity # graceful: finishes requests in flight
qbixctl ext:check # what this PHP has and lacksThe service runs as the qbix system user with /var/lib/exponential-velocity as its state directory, and can bind ports below 1024. Its settings are in /etc/default/exponential-velocity:
| Setting | Default | Meaning |
|---|---|---|
QBIX_ROOT | /usr/share/exponential-velocity/web | Document root (a welcome page until you point it at your application) |
QBIX_SITE | /etc/qbix/sites-enabled/default.conf | The site file |
QBIX_OPTS | empty | Any other qbixserver options, for example --workers=16 --https-port=8443 |
The server listens on 8080 until /etc/qbix/ports.conf says otherwise.
PHP 8.0 and Red Hat Enterprise Linux
From release 0.0.4.54 (20 October 2026) the engine runs on PHP 8.0 to 8.5 ("php": ">=8.0", it was >=8.1), with
nothing extra on 8.0: no polyfill package, no extension.
- RHEL 9 and its rebuilds: the el9 rpm depends on
php-cli >= 8.0and installs on the default AppStream PHP 8.0 without enabling a module stream; a newer stream still works. Composer works on 8.0 too. - RHEL 8: the default PHP is 7.2. Enable the 8.0 stream (
sudo dnf module enable php:8.0) and use the phar or Composer; there is no el8 rpm. - What differs on 8.0: AVIF image output needs PHP 8.1 (negotiation stops at WebP); the dashboard's per-request
memory peak needs PHP 8.2 (the column is empty);
$_FILEShas nofull_path, as in PHP 8.0 itself; a class declared witheval()that has static properties makes its worker get replaced after that request (correct, it costs a fork). The zygote runs on 8.0.
Extensions, the systemd unit, SELinux and how to verify the installation are in the engine's PHP 8.0 and Red Hat Enterprise Linux page.
What goes where
/usr/share/exponential-velocity/ the server: phar, console tools, baseline, designs, docs
/usr/sbin/qbixserver, qbixctl, qbixconsole the programs (0.0.4.41 and later)
/usr/bin/qbixserver, qbixctl, qbixconsole links to the three above (their former paths)
/usr/bin/vc-qshell the shell (0.0.4.42 and later)
/etc/qbix/ the configuration tree: qbix.conf, ports.conf, envvars, *-available, *-enabled
/etc/default/exponential-velocity the service's settings
/var/lib/exponential-velocity/ state, owned by qbixEverything under /etc is configuration: an upgrade never overwrites a file you changed. Enable and disable sites, snippets and modules with qbixctl ensite, dissite, enconf, disconf, enmod, dismod (layout).
Moving from the qbix-webserver package
Install exponential-velocity over it. The old package is removed (the new one replaces and provides it) and, once: /etc/default/qbix-webserver becomes /etc/default/exponential-velocity with paths rewritten; the state in /var/lib/qbix-webserver is copied; an enabled or running old service is stopped and the new one enabled or started in its place; /usr/share/qbix-webserver becomes a link. Where apt removed the old service before the new package was unpacked, run sudo systemctl enable --now exponential-velocity. The service user stays qbix and /etc/qbix is unchanged.
Docker
ghcr.io/se7enxweb/exponential-velocity:<release>-php<version>-<variant> fixed
ghcr.io/se7enxweb/exponential-velocity:php<version>-<variant> moves with each release
ghcr.io/se7enxweb/exponential-velocity:latest newest PHP, standard variant<version> is 8.2, 8.3, 8.4 or 8.5; <variant> is mini, lite, standard or full. Every tag is multi-architecture. Pin a fixed tag in production.
docker run -d --name web -p 8080:8080 \
-v "$PWD/public:/app" \
ghcr.io/se7enxweb/exponential-velocity:php8.3-standardThe document root is /app; any server option can be passed by replacing the command (qbixserver --root=/srv/site/public --port=8080 --workers=16). The standard and full variants also build with Oracle, Firebird and ODBC drivers. The old image ghcr.io/se7enxweb/qbix-webserver is deprecated: it keeps its tags but gets no new ones; change the name and keep the tag.
Variants
| Variant | Carries | Size (Linux x86-64, PHP 8.3) | For |
|---|---|---|---|
mini | Only what the server needs: process isolation, sockets, TLS, sessions, its own metrics store | 16 MB | Static sites, small scripts |
lite | mini plus what a typical application platform requires: XML, images (gd), MySQL/MariaDB, SQLite, cURL, intl, zip, opcache | 68 MB | Most applications |
standard | lite plus the recommended tier: PostgreSQL, MongoDB, caches (apcu, redis, memcached, igbinary), LDAP, SOAP, bcmath and more | 73 MB | The default; what the documentation assumes |
full | Everything static-php-cli can build on that platform, best effort | about 90 to 120 MB | An extension outside standard |
source | A build kit: the phar, the baseline, the console tool and a recipe for every platform, PHP version and variant | n/a | A platform no release covers |
A full build leaves some extensions out where they cannot be built (for example rar and gmssl everywhere); php sbin/qbixctl.php ext:plan --variant=full --platform=windows-x64 lists what and why.
Binary file names
qbixserver-<platform>-php<version>-<variant>[.exe] the server, one file
php-<platform>-php<version>-<variant>[.exe] the same PHP as a plain interpreter
qbixserver-windows-x64-php<version>-<variant>-gui.exe Windows, no console window
qbixserver-source-kit-<release>.tar.gz the source kitPlatforms: linux-x86_64, linux-aarch64, macos-arm64, windows-x64.
curl -LO https://github.com/se7enxweb/exponential-velocity/releases/latest/download/qbixserver-linux-x86_64-php8.3-standard
curl -LO https://github.com/se7enxweb/exponential-velocity/releases/latest/download/SHA256SUMS
sha256sum --ignore-missing -c SHA256SUMS
chmod +x qbixserver-linux-x86_64-php8.3-standard && ./qbixserver-linux-x86_64-php8.3-standard --versionCheck what any binary's PHP carries: QBIX_STATIC_BUILD=1 ./php-linux-x86_64-php8.3-standard sbin/qbixctl.php ext:check --variant=standard.
Custom binaries and signing
--pack=DIR --output=FILE bundles an application into a binary (add --gui on Windows). A binary can be signed by several people and verified against a threshold: --sign-binary --key=alice.pem --signer=Alice, then --verify-binary --m=2; signatures can be published to Sigstore Rekor. --verify-binary says so (instead of printing PHP warnings) for an unsigned file, and --sign-binary exits non-zero when it cannot sign (fixed in 0.0.4.27).
Platforms we watch but do not ship
A platform matrix runs the phar on systems no binary exists for: musl, DragonFly, FreeBSD, NetBSD, OpenBSD, illumos (on demand), RISC-V and ARMv5. The platform documentation lists three honest tiers (proven, expected, not today). Windows binaries have no pcntl/posix and no intl.
From Exponential
Exponential's exp:velocity uses the Composer copy of the engine; the package is installed with the rest of the installation; see Velocity engines for choosing and running it. The engine archive and Exponential's own archive are different things: see phar.
Limits
- The packages need PHP 8.0 or later (8.1 before release 0.0.4.54); EL 9 installs on its stock PHP 8.0, EL 8 has no package (use the phar or Composer after
dnf module enable php:8.0). - Some recommended extensions (
mongodb,redis,memcached) come from EPEL or Remi on EL;qbixctl ext:checknames them. - Release assets exist only for tags that have a section in the engine's changelog; three early tags (
v0.0.4.21,v0.0.4.22,v0.0.4.26) have no release.
Related pages
- uwebserver, HTTPS and certificates, Q shell (
vc-qshell), Velocity web server - Specification: engine settings (programs and the
sbin/andbin/layout) - Upgrade: Velocity engine upgrade notes (package and path renames), Velocity on-disk layout, Velocity engines
- Changelog: Exponential Velocity engine
- History: August 2026 (first binaries), 23 September (platform matrix), 24 September (packages), 25 to 30 September (rename,
sbin/)
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.