We are not a host and we do not sell hosting. BookPress is software you run on your own infrastructure: a native implementation of WordPress core that serves the sites already on your platform, from the same database, the same themes, and the same URLs they use today.
The PHP stack stops being in the request path. A page that took 45.2 ms to render takes 0.36 ms, and a site that needed 410 MB of resident memory needs 11.4 MB — both measured on one machine, against the standard WordPress stack, on pages a cache cannot serve. The full method and every figure are published, and the numbers below link to the run that produced them.
The consequence for a fleet is density. A box that holds tens of PHP-FPM workers holds thousands of BookPress sites, because an idle site is a few hundred kilobytes rather than a pool of processes waiting for a request that may not come. At 512 MB of RAM, the naive WordPress stack in our own capacity run could not answer a visitor at all within ten seconds; BookPress served every request in the same budget.
Their themes, their admin, their URLs, their database. A migrated site is
the same site: the same wp_posts rows, the same permalinks, the
same /wp-admin. Nothing about the move is visible to the person
who owns the site, which is the only version of this that a support desk can
survive.
This is the part most vendors leave out, so here it is first. BookPress covers a measured share of WordPress and the rest is honestly marked: there is no Customizer and no Site Editor, no plugin or theme installer, no multisite, and plugin support is real but partial — plugins run as PHP on our own engine, and each one is certified, limited or refused before it can be activated.
That last point is worth more than it sounds. Every plugin on a site is checked before it runs, and a plugin that would fail is named with the file and the line that would fail. WordPress installs anything and the site finds out at request time, on a white screen. You will know which of a customer's plugins work before you move them.
A site arrives as a standard MySQL dump — the format your backup tooling already produces — and is replayed into BookPress inside a single transaction that rolls back completely if anything in it is wrong. There is no partially migrated state to clean up.
Leaving works the same way in reverse: BookPress writes a MySQL-dialect dump
that MySQL and WordPress load directly, and exports WXR from the same
/wp-admin/export.php WordPress uses. A site can go back to a PHP
stack whenever you want it to, using the tools you already have. We would
rather you could leave easily than have you decline to start.
Running WordPress at scale and want to try this on a real fleet?