The WordPress Stack

LAMP with blistering performance, high security, automated developer tools and flexible locations.

L is for Linux

And we use Debian Linux, our preferred distro. We like it because it’s a tight community and it’s very security conscious, like us.

A is for Apache

Except we don’t usually use Apache. We use Nginx, a high-performance web server to replace Apache (though Apache is available, if that’s your poison and you’d rather not change). Nginx is significantly faster than most other web servers for a number of reasons, and is also very flexible, capable of acting as a reverse proxy server as well.

M is for MySQL

Or in our case, Percona Server. Percona provide a performance-enhanced version of MySQL. It is a completely drop-in replacement, safe to use with any LAMP application.

P is for PHP

PHP-FPM to be precise. This is a PHP-specific flavour of the popular FastCGI software, allowing better performance and scalability. (As with Nginx, mod_php for Apache is also available, if you prefer. We can do a standard LAMP stack as easily as we do our Nginx-based LAMP replacement stack. It just won’t be quite as performant).

And the rest…

We also include as standard a few other tools, namely WP-CLI is available as standard on our WordPress servers, so you can script your own devops if you like or manage your WordPress site from the command line. Varnish, the reverse-proxy server, is available as standard, for very high performance when serving pages to anonymous traffic. Memcached is also part of our standard stack, providing a distributable caching layer for the object cache that plugins like WP-FFPC can readily use.

We also provide Jenkins CI-backed automated deployment tools for WordPress developers, to speed up the process of deploying change and remove human error as a factor in your deployments to live systems.