Adobe Commerce development
Storefront design
Performance & SEO
AI & agentic commerce
Release tracker
Good Magento hosting in 2026 is hosting that runs the exact software stack your Magento version requires, has the memory and CPU headroom for indexing and traffic peaks, and comes with the operational basics: backups, monitoring, security patching and someone who answers when checkout breaks. For Adobe Commerce and Magento Open Source 2.4.9, that stack is PHP 8.5, MySQL 8.4 or MariaDB 12.3, OpenSearch 3, Valkey 9, RabbitMQ 4.3, Varnish 8 and nginx 1.30. Start there, then judge hosts on the checklist below rather than on marketing claims.
What Magento 2.4.9 needs from a host
Adobe publishes system requirements for each release. These are the on-premises requirements for 2.4.9, which became generally available on May 12, 2026:
| Component | 2.4.9 requirement | Why it matters |
|---|---|---|
| PHP | 8.5 | Older PHP versions are not supported by 2.4.9 |
| Database | MySQL 8.4 or MariaDB 12.3 (AWS Aurora MySQL also listed) | MySQL 8.0 reached end of support on April 30, 2026 |
| Search | OpenSearch 3 | Required for catalog search and layered navigation |
| Cache and sessions | Valkey 9 | Adobe's tooling uses Valkey in place of Redis from 2.4.9 |
| Message queue | RabbitMQ 4.3 or ActiveMQ Artemis 2 | Async operations, bulk actions and some integrations |
| Page cache | Varnish 8 | Full page caching in front of PHP |
| Web server | nginx 1.30 | Serves PHP-FPM and static files |
| Composer | 2.10 | Installs and upgrades code |
| Operating system | Linux x86-64 (for example RHEL, Ubuntu, Debian) | Windows and macOS are not supported |
| TLS | Valid certificate; TLS 1.2 or later for repo.magento.com and PayPal | Self-signed certificates are not supported |
Adobe also notes that upgrading applications and extensions can need up to 2 GB of RAM for the process, that OPcache is recommended, and that the PHP pcntl extension is needed to run indexers in parallel. Track how these requirements change from release to release in our Magento release tracker, and see what's new in Magento 2.4.9 for the upgrade context.
The main hosting options compared
Shared hosting is rarely suitable: you usually cannot run OpenSearch, Valkey, RabbitMQ and Varnish, or control PHP settings. The realistic choices fall into five categories. The table below names examples in each and records only what each provider states on its own site or documentation as of November 2026. It is not a ranking, and "not stated" means we could not find it published, not that the host cannot do it. Ask, using the checklist further down.
| Option and example | Who manages what | 2.4.9 stack (as published, Nov 2026) | Scaling | Typical fit |
|---|---|---|---|---|
| Adobe Commerce as a Cloud Service (Adobe SaaS) | Adobe runs the multi-tenant infrastructure and upgrades the application automatically (versionless) | Not a hosting choice; Adobe manages the stack, with a managed edge CDN or your own CDN | Full auto-scaling across the stack, per Adobe | Licensed Adobe Commerce merchants who want no infrastructure or upgrade work |
| Adobe Commerce on cloud infrastructure (Adobe PaaS) | Adobe provides single-tenant infrastructure with Fastly included; you handle upgrades and patching | Adobe's 2.4.9 cloud table: PHP 8.5, OpenSearch 3, Valkey 9, RabbitMQ 4.3, MariaDB 12.3, nginx 1.30; full page caching through Fastly | Horizontal auto-scaling for scaled architecture | Licensed Adobe Commerce merchants who need code-level customization |
| Magento-specialist managed host: Hypernode | Host runs and patches the platform, with monitoring and support | Docs list PHP up to 8.5, OpenSearch up to 3.3, MySQL up to 8.4, a Valkey option and Varnish up to 7.x | Plan up- and downgrades, cluster hosting and an autoscaling add-on | Magento stores that want a tuned platform without running servers |
| Magento-specialist managed host: MGT Commerce | Fully managed on AWS; you keep ownership of the AWS account and data | Site lists PHP 8.1 to 8.4, Valkey or Redis and Varnish; OpenSearch 3 and PHP 8.5 not stated | Auto Scaling plan with 1 to 50 web servers | Stores that want managed AWS with traffic peaks |
| Magento-specialist managed host: JetRails | Fully managed, in JetRails data centers or the customer's AWS account | Site lists Varnish and Redis; its December 2025 changelog moved to OpenSearch 3.2 and Varnish 7.7; PHP 8.5 and Valkey not stated | Vertical scaling, and auto-scaling for AutoPilot clusters | Stores that want managed hosting with AWS as an option |
| Cloud VPS with a management layer: Cloudways | Cloudways handles server setup, monitoring, server-level updates and backups; you own Magento updates, extensions and admin access | Page states support for Magento 2.4.8 (PHP 8.3 and 8.4, OpenSearch 2.19 by default, Redis, Varnish); 2.4.9 not stated | Scale RAM, CPU and storage on DigitalOcean, Vultr, Linode, AWS or Google Cloud | Smaller stores on 2.4.8 that want simple server management |
| Self-managed cloud: AWS or Google Cloud | Your team or agency manages everything from OS to application | You choose every version; Adobe's requirements page also lists supported AWS services | Whatever you build: auto-scaling groups, managed databases, larger instances | Teams with real DevOps capacity |
| Self-managed VPS with CloudPanel: for example Hetzner or Contabo servers | You manage OS, security, backups and the application; CloudPanel provides the control panel | CloudPanel docs list PHP up to 8.5, MySQL 8.4 or MariaDB 12.3 on newer OS releases, Varnish up to 7.7 and Redis; OpenSearch 3 is installed separately; Valkey not listed | Resize the server or add servers yourself | Small stores with in-house or agency sysadmin skills |
Two patterns stand out. First, few hosts publish a complete 2.4.9 stack: Varnish 8 in particular appeared on none of the provider pages we checked, so ask how full page caching will work on 2.4.9. Second, "managed" means different things. Cloudways, for example, states plainly that Magento application updates and extensions remain your job, while Adobe's SaaS edition removes upgrades entirely.
Host evaluation checklist
Send these questions to every host you shortlist and compare the answers in writing. Each maps to a requirement or a common failure point.
1. Software stack (maps to 2.4.9 requirements)
- Can you run PHP 8.5 today, and how quickly do you offer new PHP versions after Adobe adds them?
- Do you offer MySQL 8.4 or MariaDB 12.3? How do you handle major database upgrades?
- Is OpenSearch 3 available, on the same server or as a managed service? How much memory is allocated to it?
- Is Valkey 9 available for cache and sessions, with separate databases or instances?
- Is RabbitMQ 4.3 available, and who keeps queue consumers running?
- Is Varnish 8 included, and can we deploy Magento's generated VCL? Or do you provide a CDN-based full page cache instead?
- Which web server do you run, and at what version?
- Do you support the PHP extensions Adobe lists (including
bcmath,intl,pdo_mysql,sodium,zip) andpcntl?
2. Capacity and scaling
- What CPU and memory are dedicated, not shared, to our store?
- How do you handle traffic peaks such as sales events: scheduled scale-up, auto-scaling, or nothing?
- Can we run cron and indexers without starving the storefront?
- Is storage local SSD or network storage, and what are the I/O limits?
3. Performance features
- Is a CDN included or supported for static and media files?
- Are HTTP/2 or HTTP/3 and Brotli or gzip compression enabled?
- Is OPcache configured with enough memory for Magento?
- What APM or profiling tools can we use on production?
4. Security and compliance
- Who patches the operating system and services, and how fast after a critical advisory?
- Is there a web application firewall and malware scanning?
- How is SSH and admin access controlled (keys, IP allow lists, two-factor)?
- What is your PCI DSS position, and what remains our responsibility?
- Where is data stored (region), relevant for GDPR and data-residency needs?
5. Operations
- How often are backups taken, where are they stored, and how long does a restore take? Can we test one?
- Do you provide staging environments that match production?
- Do you support zero-downtime or low-downtime deployment?
- What monitoring and alerting do you run, and do we get access?
6. Support and contract
- Is support available around the clock, and does it include Magento knowledge or only server knowledge?
- What uptime commitment is in the contract, and what happens when it is missed?
- Can we export everything and leave without lock-in?
Red flags
- The host cannot name the versions it runs, or only supports an older Magento line.
- "Unlimited" resources on a shared plan.
- No staging environment, or staging on a different stack from production.
- Backups you cannot restore yourself, or that have never been tested.
- Full page cache "handled by a plugin" instead of Varnish or a CDN-based equivalent.
How caching changes the hosting picture
A store with a high full page cache hit rate needs far less PHP capacity than one generating every page. Before buying a bigger server, check whether Varnish, Valkey and the CDN are doing their jobs. Our guide to Magento caching with Varnish and Valkey shows how to check each layer.
Frequently asked questions
How much memory does Magento hosting need?
It depends on catalog size, traffic and services on the same server. Adobe notes that upgrades can need up to 2 GB of RAM for the process alone; OpenSearch, the database and Valkey each need their own memory on top of PHP.
Can I still use Redis or Elasticsearch?
Not with 2.4.9's documented requirements, which list Valkey and OpenSearch. Plan the switch as part of your upgrade.
Is Apache still supported?
Adobe's 2.4.9 requirements list nginx 1.30 as the web server for both on-premises and cloud infrastructure, and Apache is not listed (checked November 2026). Plan on nginx for 2.4.9.
Next step
If your store is slow on a host that looks fine on paper, Mistri's Magento performance optimization review covers server configuration, caching and capacity together, so you can tell whether to tune or move.
Sources
Adobe Experience League: Adobe Commerce system requirements; Adobe Experience League: Feature comparison, Cloud Service vs PaaS; Adobe Experience League: Configure Commerce to use Varnish; Hypernode Docs: hypernode-systemctl settings; MGT Commerce: Magento hosting; JetRails: Magento hosting; JetRails: December 2025 AutoPilot changelog; Cloudways: Magento hosting; CloudPanel Docs: Technology stack; CloudPanel Docs: Magento. Checked November 2026.
