Magento hosting requirements (OpenSearch, Redis, Varnish, 4GB+ RAM) rule out shared hosting. Here’s what actually works instead.
Table of Contents
Magento (now officially Adobe Commerce, though “Magento” remains the name most site owners actually search for) has a genuinely heavier hosting footprint than any of the other major ecommerce platforms, and it’s worth being direct about that upfront: shared hosting, the starting point for WooCommerce, PrestaShop, or OpenCart, generally isn’t a realistic option for a real Magento store. Understanding exactly why matters more than a generic “Magento needs more resources” warning, since the specific requirements determine what tier of hosting actually works.
Magento Hosting Requirements: What Magento Actually Requires
Current Magento 2.4.8/2.4.9 requires PHP 8.3 or 8.4 (8.1 and 8.2 are no longer supported), and the database layer has shifted meaningfully: MySQL 8.0 reached end of support on April 30, 2026, and current releases have moved on accordingly, 2.4.8-p5 supports MySQL 8.4 or MariaDB 11.4/11.8, while 2.4.9 supports MySQL 8.4 or MariaDB 11.8/12.3 (12.3 recommended). Older releases still on MySQL 8.0 are explicitly advised by Adobe to migrate to a supported MariaDB version rather than staying put.
Beyond the core PHP and database stack, a production Magento install expects OpenSearch 2.19 for catalog search and indexing, Valkey 8 or Redis 7.2 for caching and session storage, and Varnish 7.6 as a full-page caching layer sitting in front of the application. That’s not an optional performance add-on stack, it’s the environment Magento is actually designed and tested to run in; skipping any of these pieces doesn’t just mean a slower store, it means running the platform outside its own documented, supported configuration.
Why This Rules Out Shared Hosting
OpenSearch, Redis or Valkey, and Varnish are each separate services that need to be installed, configured, and kept running alongside PHP and the database, not something a typical shared hosting control panel provisions or exposes to a customer at all. Adobe’s own minimum hardware guidance for a production store starts at 4GB of RAM, a floor that assumes reasonably modest traffic; a store with a real catalog and real order volume needs meaningfully more. Shared hosting is built around many customers sharing one server’s resources at a much smaller per-account footprint than Magento’s own stack requires just to run correctly, before traffic even enters the picture.
What Actually Works
A Magento store needs either a specialized managed Magento/Adobe Commerce hosting provider (built specifically around this stack, with OpenSearch, Redis, and Varnish pre-configured and maintained) or a dedicated server or high-tier VPS with full root access, where you or a developer install and manage that stack directly. The second path is realistic for a technically capable team; it is not a reasonable starting point for a store owner without server administration experience or a developer who can own that setup.
On a dedicated server with full root access, the resources exist to run Magento’s complete stack correctly, but the OpenSearch, Redis/Valkey, and Varnish configuration itself is on you or whoever manages the server, it does not come pre-installed the way a one-click WordPress or Joomla installer does on shared hosting.
What to Actually Check Before Committing to a Host
- Confirmed PHP 8.3/8.4 support, not just “PHP available,” with the specific version verified.
- Root or admin-level access sufficient to install and configure OpenSearch, Redis/Valkey, and Varnish yourself, or a host offering managed Magento hosting where these come pre-configured.
- Real RAM headroom well above the 4GB floor once your actual catalog size and expected traffic are factored in, not the bare minimum.
- Database version matching current requirements (MySQL 8.4 or MariaDB 11.4), since running against an unsupported database version is a real, documented compatibility risk, not a theoretical one.
- SSH access with Composer support, since Magento’s own deployment and dependency-management tooling assumes command-line access as a baseline, not an optional convenience.
The Honest Bottom Line
If you’re evaluating Magento for a new store and don’t already have a developer or team comfortable managing OpenSearch, Redis, and Varnish directly, that operational requirement is worth weighing as heavily as the platform’s ecommerce features themselves, since the hosting complexity is a real, ongoing commitment, not a one-time setup cost. For a smaller store without that technical capacity, a platform with a lighter hosting footprint, WooCommerce or PrestaShop on a properly-specced VPS, is often the more realistic starting point, with a path to Magento later if the business genuinely grows into needing its specific enterprise-catalog capabilities.
Magento® and Adobe Commerce™ are trademarks of Adobe Inc. and are not affiliated with AllCloudHost.
Key Takeaways on Magento Hosting Requirements
- Magento hosting requirements include search, caching, and plenty of memory, which rules out shared hosting.
- Check each Magento hosting requirements item against a provider’s plan before committing.
Further reading: Adobe Commerce: system requirements.