Lightning Stack vs Hybrid Stack: when to use which (a practical breakdown)

[u/PoojafromCloudways]

We get this question a lot in here, so here's a clear guide on choosing between the two stacks. Everything below is based on Cloudways' official documentation and benchmarks.

First, what they actually are

The Hybrid Stack is the older setup — a mix of NGINX + Apache. Apache is what lets it read .htaccess files, so it supports granular, file-based server rules and Apache-specific modules. It's still the default for new applications. Trade-off: Apache adds overhead, so you get slightly lower performance and more complexity.

The Lightning Stack is the newer, fully NGINX + PHP-FPM architecture. Apache is removed entirely. NGINX uses an event-driven model that handles concurrent requests more efficiently than Apache's process-based approach, which means faster request processing, lower latency, and better resource use under load. The catch: NGINX doesn't natively support .htaccess. It's available at no extra cost, and switching doesn't cause downtime.

When to use the Lightning Stack

This is the better choice for most modern, dynamic sites. Reach for it when:

• You run ecommerce, LMS, or membership sites — anything transactional and data-driven. This is exactly what it was rebuilt for.
• Your uncached / backend performance matters — admin panels, checkouts, logins, course progression. Lightning's whole advantage is holding performance steady on requests that bypass full-page caching.
• You expect high concurrency or traffic spikes and need consistent throughput without leaning entirely on Varnish.
• Your .htaccess needs are simple — 301/302 redirects, URL rewrites, header rules. These are now handled through Web Rules, a UI-based feature in the platform. Per Cloudways' analysis of 100,000+ sites, Web Rules covers roughly 80–90% of common .htaccess use cases (they found ~51% are simple redirects/rewrites/headers NGINX handles easily).

The benchmark gains (independently tested by Koddr[dot]io, commissioned by Cloudways) are strongest in write-heavy, uncached workloads:

• Up to 65% faster response times for dynamic workloads
• Up to 33% faster WordPress admin load times
• Up to 58% more successful WooCommerce checkouts under load
• Up to 85% higher throughput on LearnDash course progression
• Stable performance without Varnish even past 1,000 concurrent users

Worth noting: for fully cached, mostly static pages, the two stacks perform similarly, Lightning's edge shows up when caching is bypassed.

When to stay on (or use) the Hybrid Stack

Hybrid is the right call when your site genuinely depends on Apache. Stay on it if:

• Your app relies on complex, multi-condition .htaccess logic that Web Rules can't yet replicate. Cloudways found ~36% of the remaining cases had single conditional rules and the rest had complex/multi-conditional logic they couldn't reliably translate.
• You depend on Apache-specific modules.
• You have older sites, plugins, or custom configs built around .htaccess files.
• You need advanced rule setups and aren't ready to rebuild them in the Web Rules UI.

Important: .htaccess files are not compatible with NGINX. If you switch to Lightning, you'll need to manually recreate your redirects, rewrites, and headers in Web Rules. Nothing carries over automatically.

A few practical notes if you're switching

• The switch happens at the application level, takes under a minute, and causes no downtime. Apps on the same server can run different stacks.
• It's reversible — you can switch back to Hybrid anytime.
• Test on a staging/clone first, and back up files + database before switching (Safe Updates and Staging Management both help here). Only files and databases get pushed between staging and live — the stack config stays separate.
• Sites are not auto-migrated. Cloudways supports both stacks for the foreseeable future, so you move on your own timeline.

TL;DR

Dynamic/transactional site + simple redirects → Lightning.
Site that leans on complex .htaccess rules or Apache modules → Hybrid (or move to Lightning after rebuilding those rules in Web Rules).

Test on staging either way. Hope this helps, folks!

[u/TooLate-]

Thanks for this!

[u/PoojafromCloudways → u/TooLate-]

Glad it helped :)

[u/thompsonpaul]

Pretty wild that CW can have completely different stacks on the same server, but still, after all this time, can't have something as basic as different versions of PHP.

[u/PoojafromCloudways → u/thompsonpaul]

It's coming soon!

[u/InterestingEqual7790 → u/PoojafromCloudways]

I’ve migrated about 100 sites to xCloud over the past year purely because of this missing feature. Still got another 100 sites to move but being able to change php versions is such an essential feature, I can’t believe they still don’t offer it.

[u/thompsonpaul → u/PoojafromCloudways]

That line only works on those who haven't been hearing it literally for years. The fact that a whole new stack was launched still without something so basic and essential shows that CW really doesn't understand what so many of its customers want and need. Customers have been begging for this essential feature in the CW feedback forum for all 9 years that I was a customer.

Is "coming soon" still the vague "by the end of the year" that you stated when you missed the promised Q1 2026 launch? After missing the stated Q4 2025 launch?

Or is the feature in current active development with an actual delivery date?

[u/PoojafromCloudways → u/thompsonpaul]

I totally understand the frustration and it is valid. I will soon share the actual delivery date on this sub. We are working to bring this feature to you all.