In short
Magento hosting decides how fast your store loads, how well it survives a sales day and how quickly it recovers when something breaks. Magento 2.4.9 needs a specific stack: PHP 8.5, MySQL 8.4 or MariaDB 12.3, OpenSearch 3, Valkey 9, Varnish 8 and RabbitMQ 4.3. Shared hosting cannot run that properly. For most stores the real choice is between a VPS you manage yourself, managed Magento hosting and a cloud setup on AWS, Google Cloud or Adobe Commerce Cloud.
What Magento 2 hosting needs to run in 2026
Adobe publishes the tested software versions for every Magento release in its system requirements. For Magento Open Source and Adobe Commerce 2.4.9 on your own servers, the list is:
- PHP 8.5
- Composer 2.10
- MySQL 8.4 or MariaDB 12.3 as the database
- OpenSearch 3 for catalog search
- Valkey 9 for cache and sessions
- Varnish 8 for full-page cache
- RabbitMQ 4.3 or ActiveMQ Artemis 2 for message queues
- nginx 1.30 as the web server
Two changes catch many stores out. Redis and Elasticsearch are no longer in the 2.4.9 list: the cache line names Valkey, and search runs on OpenSearch only. Adobe also states that it supports only the listed combinations, with an example: upgrade to MariaDB 12.3 before you upgrade to 2.4.9. A good host therefore keeps up with Magento releases, not only with PHP releases.
Older releases need older versions. A store on 2.4.8 runs PHP 8.3 or 8.4, for example, so the server stack has to be planned together with your next upgrade.
Shared, VPS, managed or cloud: types of Magento hosting
Most offers fall into four groups. What matters most is who installs, tunes, patches and watches the server.
| Shared hosting | VPS or dedicated server | Managed Magento hosting | Cloud (AWS, Google Cloud, Adobe Commerce Cloud) | |
|---|---|---|---|---|
| Magento stack | Usually no OpenSearch, Varnish or Valkey, limited PHP settings | Whatever you install yourself | Installed and tuned for Magento by the host | Built from managed cloud services, by you or a partner |
| Who runs the server | The host, for many sites at once | You or your developer | The host or agency, with Magento know-how | You, a partner, or Adobe for Adobe Commerce Cloud |
| Performance | Shared with other sites, hard to predict | Good if configured well | Good and predictable | Scales out for peaks |
| Work for your team | Low, but you hit limits fast | High: updates, security and backups are yours | Low: patches, backups and monitoring included | Medium to high, depending on who runs it |
| Best for | Not recommended for a live Magento 2 store | Teams with their own server administrator | Most small and mid-size stores | High traffic, scaling and enterprise needs |
Adobe Commerce on cloud infrastructure is a special case. It is Adobe’s own platform for Adobe Commerce licences, runs on AWS or Azure, and includes Fastly CDN and a staging environment. It is not an option for Magento Open Source stores.
Some hosts specialise in Magento, others offer it as one product among many. There is no single best Magento hosting for every store: compare any provider on the points below, not on the name.
How to size a Magento hosting server
There is no fixed formula. These factors decide how much CPU, memory and storage your store needs.
- Catalog size: the number of products, attributes and configurable variants affects indexing time, the search index and database load.
- Traffic and peaks: average visits matter less than the busiest hour, such as a campaign, a newsletter or Black Friday.
- Store views and languages: every website, store view and currency multiplies indexes and cache entries.
- Cron, indexers and queues: imports, price rules, stock updates and emails run in the background and compete with visitors for the same CPU.
- Extensions and integrations: ERP, PIM, marketplace and feed connections add API calls and background jobs.
- Uncached pages: cart, checkout, customer account and search are not served from Varnish and need real PHP and database power.
The safest way to size a server is to measure: check your current server load, then run a load test on staging before a move or a big campaign.
What managed Magento hosting should include
“Managed” means different things at different hosts. For a Magento store, ask for these points in writing.
- Magento security patches and server updates, applied on a schedule and tested first
- Daily off-site backups of files and database, with restore tests
- 24/7 monitoring of uptime, disk space, cron and error logs, with someone who reacts
- A staging environment that matches production
- CDN and a web application firewall (WAF) in front of the store
- SSL certificates installed and renewed automatically
- OpenSearch, Varnish, Valkey and the database tuned for Magento, not left on default settings
- SSH or SFTP access, and an account and data that stay in your name
Magento hosting for EU stores: data location and GDPR
If you sell to customers in the EU or the UK, your store processes personal data: names, addresses, orders and account details. Your host usually processes that data on your behalf, so you need a data processing agreement with it.
- Ask in which country the servers and the backups are located.
- Check whether data leaves the EU, for example through support teams, monitoring tools or backups, and which safeguards apply.
- Make sure the agreement also covers the host’s subcontractors.
- Many EU stores choose data centres in Germany or elsewhere in the EU to keep this simple.
Questions to ask a Magento hosting provider
- Which Magento versions do you support, and which PHP, database, OpenSearch and Valkey versions will my store run?
- Who applies Magento security patches and server updates, and how are they tested?
- How often do you back up, where are the backups stored, and when did you last test a restore?
- Is a staging environment included, and how do changes go live?
- What do you monitor, and how fast do you respond to an outage at night or at the weekend?
- How do you handle traffic peaks, and can we move to a larger setup without rebuilding the store?
- In which country are the servers and backups, and do you sign a data processing agreement?
- Who owns the server account, and how do we leave if we need to?
Common Magento hosting mistakes
- Running a live Magento 2 store on shared hosting, without OpenSearch, Varnish or enough memory
- No staging, so patches and extension updates go straight to the live store
- OpenSearch left on default settings, so search and category pages are slow or indexing fails
- Cron not running or not monitored, so indexes, emails and sitemaps quietly stop
- Backups that exist but have never been restored
- Upgrading Magento without checking that the server stack supports the new release
- Choosing the cheapest offer and paying later with downtime and lost orders
Managed Magento hosting at MageBooster
MageBooster offers managed Magento hosting packages on Amazon AWS, Google Cloud or Contabo, with Contabo servers in Germany and the EU. Our engineers install and tune each server for your catalog, traffic and Magento version, from 2.4.6 to 2.4.9. Every package includes 24/7 support, setup and migration, daily off-site backups kept for 30 days with tested restores, firewall and WAF, 24/7 monitoring, monthly security patches and SSL. Staging is included from the Business package up, and the account and your data stay in your name.
Not sure what your store needs? Send us your store link. In a free analysis we review your current server, speed and security and recommend the right setup.
See our managed Magento hosting packages →
Read about Magento speed optimization →
Let us get in touch with you
Leave your details and your store address. We look at your store first and contact you within one business day, by phone, WhatsApp or email, whichever you prefer.
English
German
Dutch
Turkish