Stock WordPress leaves the hardening to you, and doing it well is demanding work. wp³ ships the hardened baseline instead: a small attack surface, every plugin inspected and contained, and reserved memory with a fair share of CPU. Your team keeps full control, and the platform carries the routine security work.
The platform is built so the constructs plugin attacks rely on are not there to break: no core to exploit, no process spawning, no writable code paths, least privilege throughout. There is less to attack, and what remains is fenced in.
wp³ analyses each plugin before it runs and again at runtime, learning the functions, hooks and outbound hosts it uses, then holds it to that behaviour. Something a plugin was never seen doing is refused, not assumed safe.
A plugin cannot drop code it wants the server to run, cannot reach servers you did not approve, and cannot quietly create an administrator. When a plugin turns out to be vulnerable, the damage it can do is small and it disappears with the request.
Each site gets its own reserved memory that no other site can use, and a fair share of CPU and disk. Memory is never oversubscribed, so a busy neighbour cannot take yours; CPU and disk are shared fairly, so one site cannot starve another.
The real alternative is rarely a named host. It is the habit of running standard WordPress, adding a security plugin, and hoping the next plugin disclosure is patched in time. Kinsta, WP Engine, Hostinger and the rest run standard WordPress with good operations and backups, but they run the same plugin surface and the same race.
Sign in, add your site and move it across from the control panel. Bring your theme and plugins with it.
The 14 day trial runs your actual site, so you see how your plugins behave in place rather than in theory.
If a plugin does not work as required, contact us and we look at it. Everything else is self-service.
wp³ is not a drop-in replacement for every WordPress site. This comparison is deliberately candid about where standard hosting is the better choice.
A plugin that turns out to be vulnerable cannot leave a back door behind, because plugins cannot write runnable files, reach unapproved addresses, or create an administrator. We state this plainly as limits, not as a perfect guarantee.
Every plugin is studied before it is trusted: the platform learns what it calls and where it connects, then holds it to that behaviour. New behaviour is refused, not assumed safe.
For the plugins we support, pages render the same as on standard WordPress. We verify this against a real WordPress install rather than assuming it.
A plain-language security brief for business and technology leaders explains the model, its limits, and the questions to ask any host.
One flat price per site, with reserved memory and a fair share of CPU. A 14 day trial to prove it on your real site, then hosting you can predict. Founding prices are locked for life for early customers. On-premises and enterprise deployments are on request.
Run your real site and plugins before you pay.
Founding price, list 299 EUR. One site on the wp³ platform.
Founding price, list 749 EUR. For sites that need enforced outbound limits and anomaly detection.
Yes. Move the site yourself from the control panel and bring your theme and plugins with it. If a plugin does not work as required, contact us and we will look at it.
No. wp³ is an independent hosting platform. Your themes and plugins run and render the same way, but wp³ is not affiliated with WordPress.org or Automattic, and it does not include their code.
Block themes and full-site editing, the block editor (Gutenberg), multisite, automatic updates and XML-RPC are out of scope. We say so plainly rather than pretending they are on the way.
Plugins run under limits we enforce: they cannot write runnable files, reach servers you did not approve, or create an administrator. That removes the usual ending of a plugin attack, where an attacker leaves a small file for the server to run later.
No host can promise that, and we will not. What we can say is that a vulnerable plugin has far less it can do here, so the blast radius is much smaller than on a standard WordPress site.
Migration is self-service: add your site and move it from the control panel. There is a 14 day trial so you can test the real site before paying, and if a plugin does not work as required, contact us.