Merlot Digital









Legendary uptime. Linux-fuelled speed.

To deliver powerhouse speeds to your end clients, your Managed Servers are equipped with weapons-grade web-serving systems, including NGINX, Apache, PHP, LSAPI and beyond. These alongside a raft of PHP modules, a threaded Apache MPM, and in-RAM cache indexing, and your client sites will fly like you want them to. We have a set of 3 different Web Server stacks, depending on your needs, loading, and other factors – to make your sites cruise.

PHP v8.2 and v8.3: Defaults

With v8.1 and v7.4 typically available to suit client needs, we regularly push through with update waves in communication with clients, to resolve problems with legacy websites where major change is needed (ie. EOL PHP5, now PHP7). This ensures that end clients websites remain secure, and in turn our clients’ servers do as well.

LSAPI Handler: Power of LiteSpeed

Allowing your end clients to benefit from lightning-fast load times, we employ LSAPI (LiteSpeed API) PHP Handler on CloudLinux – which doesn’t have the same RAM consumption demands as PHP-FPM, yet delivers consistently good performance. This is further helped by on-site tuning like smushing, as well as multi-level caching.

NGINX w/ Cache: Apache as fallback

Our default Web Stack used is NGINX as a Reverse Caching Proxy, in front of the Apache (httpd) Web Server. This is being furthered by our beta contributions to Apache2NGINX (by CloudLinux), which seeks to remove the need to “proxy pass” difficult requests back to Apache at all. Bliss! This also gives lightning-fast caching.

CloudLinux LVE: Emails if any problem

Whereas some providers make it a nightmare to know if your server is even online, we work the other way around – and configure CloudLinux so it lets you know if any sites are hitting resource caps. This means you’re ahead of your clients in the event of spurious issues, like eComm/WP-Cron demands, or whatever is going on.

MariaDB v10.6: High-performance SQL

MySQL was great, though we’ve been all for MariaDB since it became easier to shift over earlier in v10’s history. We currently run all servers on MariaDB v10.6 with all common storage engines, and do not allow clients to continue with EOL software (ie. MySQL earlier versions). Our SQL configs are performant and incredibly stable.