Absolutely not and no intention to vendor-lock to a heavily commercialized product that works in a narrow segment: WordPress and Joomla. Even then, you’re forcing people to upgrade to its commercial variant, Litespeed Enterprise, to get a usable multi-tenant setup.
I would recommend benchmarking ApisCP independently on your own. There’s a guide to walk you through the benchmark process. If you want Apache to benchmark like NGINX and Litespeed, then it must be configured as such. This includes migrating .htaccess directives to runtime directives as well as trimming the superfluous directives that bloat .htaccess rules. This guide will walk you through those steps.
People overprescribe and under-research quite often, no matter the software. WordPress is especially problematic that so much mysticism surrounds proper configuration. Proper configuration is what separates a well-oiled machine from a nasty CVE. Litespeed is marketed as a silver bullet to WordPress but in fact taking a step back to see why these problems exist is a bit more prudent.
From what customers have independently discovered, ApisCP performs as close or better to LS in fact I’ve even had some converts sell their lifetime Litespeed licenses. Most of this lore comes from comparing with cPanel that still uses Prefork MPM in 2022. There’s no reason to use Prefork past 2010 unless you’re floating $540 million in debt. cPanel’s price hikes seem to corroborate they need all the revenue streams they can get.
Plus, you can do some cool things with Apache including integrated DoS deterrence, malware scrubs, any-version Ruby/Node/Python, and rendering optimization through Pagespeed that Litespeed has dropped support for because it conflicts with their commercial endeavors.
Some folks have tried porting Litespeed but the mod_rewrite implementation isn’t truly drop-in. We synthesize addon and subdomains by leveraging filesystem caches to reduce static memory allocation. It results in a lower footprint than your typical implementation.
Definitely benchmark to get a fair comparison. Any statistic can be massaged to conform to any bias you so desire to market.
It’s a touch bias too to characterize Apache as sluggish without giving its implementation in ApisCP a chance, right? 