The same WordPress sites.
4.5 to 5+ times the requests per second.
BookPress is software you run on your own infrastructure: a native
implementation of WordPress core that serves the sites already on your
platform. They keep the themes, /wp-admin and URLs they use today. We sell the software, and we leave the hosting to
you.
Look at one before you read any further. The live demo runs
this engine on a Google Cloud e2-micro, two shared vCPU and
969 MB of memory, with the Kadence theme and WooCommerce, Elementor, Yoast SEO, Contact Form 7, Yoast Duplicate Post and Hello Dolly
all active, and no page cache anywhere. You see your own login when you start your sandbox. We delete your sandbox 15 minutes after you start it, so put nothing personal into it.
Changes on your fleet
BookPress takes the PHP stack out of the request path. On the site's WooCommerce and Elementor
pages, BookPress serves about 4.5 times the requests per second of a
tuned WordPress on the Intel server and over 5 times on the ARM server.
A site with no plugins serves about 112.9 times the requests per second
on the Intel server and 125 times on the ARM server. We measured speed
on Google Cloud c2-standard-4 and c4a-standard-4 machines,
uncached, against WordPress running its own PHP with opcode JIT, Redis and MariaDB, on
pages a cache cannot serve.
Under full load on the Intel server, four BookPress workers used about 0.6 GB, against 0.55 GB for a right-sized WordPress and 1.8 GB for a tuned 64-child pool. After 30 seconds idle, BookPress released to about 0.3 GB while the WordPress pools held. We measured memory on BookPress 0.2.57. The speed and density pages have every figure and the method.
BookPress sets its number of workers from the machine's processors and
memory when the service starts. If you set a number in /etc/bookpress/bookpress.conf, BookPress uses it. Every worker shares the engine code and plugin bytecode (about 75 MB). Each worker then adds
about 100 to 180 MB of its own under load and gives most of it back when idle.
It compiles a site's PHP files when it starts and when a file changes, so
the first visitor does not wait for that. A worker that has had no request
for 30 seconds gives memory back to the system. We are measuring how many
sites one machine carries.
Your customers keep their sites
They keep their themes, admin, URLs and content. A migrated site keeps its wp_posts rows, permalinks and /wp-admin. The site owner sees nothing change.
Some parts don't work yet
BookPress doesn't support Multisite. The Customizer and the Site Editor work in part: the Customizer previews by reloading the page, and the Site Editor has no template revisions and no style variations. Both need a WordPress install on disk beside BookPress. You install plugins and themes from wordpress.org in wp-admin. Themes have no update flow yet. Image editing covers crop, rotate by quarter turns, flip and scale, for JPEG and PNG. Plugin support is partial. Plugins run as PHP on our own engine, and we certify, limit or refuse each one before it can activate.
We check each plugin on a site before it runs. If a plugin would fail, we name it, with the file and the line it would fail on. On WordPress you install anything and find out at request time, on a white screen. You'll know which of a customer's plugins work before you move them.
Install it
curl -fsSL https://bookpress.io/install.sh | sudo sh The installer detects apt or dnf, asks for your customer id and access token, installs the signed package and starts the service. The manual steps per distribution are on your account's install page.
The installer asks for the address visitors use. Behind nginx, Caddy or a
load balancer on the same machine, BookPress serves https links with no extra
setting. If HTTPS ends on another machine, name that machine with
--trusted-proxy. BookPress ignores forwarded headers from anywhere else. For scripted installs, --site-url sets the address and
--yes skips the questions.
BookPress updates itself. Releases install unattended by default. A major version waits for your consent. After each update it checks that the
site still answers and goes back to the previous version if not. Tools →
Site Health shows the installed version and the last result.
UPDATER=off in /etc/bookpress/updater.conf switches
the updater off.
Getting sites in, and out
You need one command each way. Our package installs its own wp beside
the server. Each command asks once before it writes anything;
--yes skips the prompt in scripts.
The commands work straight after install, with or without WP-CLI on the host. The program behind them is bookpress-wp, and bookpress-wp import and bookpress-wp export are its short forms.
In
$ wp bookpress import --dir=<wp-root> --path=/var/lib/bookpress
BookPress import from the WordPress at <wp-root>
Import <home-url> (<n> tables, <size> uploads) into BookPress at <bookpress-root>? [Y/n] y
...
Success: Import complete. The source WordPress at <wp-root> and its MySQL database were not modified; `wp bookpress export --dir=<wp-root>` takes the site back. Import runs the site's own WP-CLI for the dump, so BookPress never handles the database password, and it leaves the source WordPress and its MySQL database untouched. It records how to reverse itself: table prefix, table definitions, renamed keys, which tables and options are ours, home and site URL, a file manifest. It ends with a verdict for every plugin, which may say limited or refused.
Out
$ wp bookpress export --dir=<wp-root>
backup: <wp-root>/../bookpress-backups/bookpress-backup-20260927T131258Z.sql (94.1 KB, verified)
Are you sure you want to overwrite the contents of your MySQL database? We stored a backup of it in <wp-root>/../bookpress-backups/bookpress-backup-20260927T131258Z.sql. [y/N] y
...
Success: Export complete. WordPress at <wp-root> now holds the BookPress site. The backup of what was there is <wp-root>/../bookpress-backups/bookpress-backup-20260927T131258Z.sql. Export uses that record. A site that goes in and straight back out is
byte-identical in the database and in wp-content. A test suite checks that against a real WordPress on MariaDB. Export writes the backup
outside the web root. We'd rather you could leave than have you decline to start.
Want us to run your sites for you? We're setting up BookPress Hosting, managed WordPress hosting for people who own sites and don't run servers. Join the list →
If you run WordPress at scale and want to try this on a real fleet, tell us what's on it.