Hosting for Magento, PrestaShop and OpenCart: The Heavier Carts

Not every self-hosted store runs WooCommerce, and the other carts change the hosting math. Magento (Adobe Commerce Open Source) is heavy — it needs a minimum of 4 GB of RAM plus a full supporting stack, so it belongs on a VPS, managed cloud or dedicated server, never shared hosting. PrestaShop and OpenCart are lighter than Magento but heavier than a basic WordPress site, sitting comfortably on a good VPS or mid-tier managed plan. Here's what each demands.

Magento / Adobe Commerce: a serious server, not a shared plan

Magento 2.4.8 (read September 2026) expects a production stack most shared hosts can't provide: PHP 8.3 or 8.4, MySQL 8.4 or MariaDB 11.4, a minimum of 4 GB RAM on SSD, Composer 2.9+, and supporting services including OpenSearch for catalogue search, Redis or Valkey for caching and sessions, and Varnish for full-page caching, typically behind Nginx. That's why Magento is a VPS, managed-cloud or dedicated-server platform by nature. If someone offers you Magento on a $5 shared plan, walk away — it will be slow or unstable under any real load.

Where to host Magento

For most Magento shops, the realistic options are a managed cloud host like Cloudways (which can run the required stack on a sized cloud server) or a managed store host like Liquid Web that offers Magento-capable plans, and for larger merchants a tuned VPS or dedicated server. Technical teams comfortable running the OpenSearch/Redis/Varnish stack themselves often self-manage a VPS for the best value — a Hetzner cloud instance is the strongest raw-value option there, and it pays us nothing, so we mention it purely because it's genuinely the right answer for that use case. Our best ecommerce hosting ranking covers the managed options in depth.

PrestaShop: mid-weight, VPS-friendly

PrestaShop is lighter than Magento but still benefits from more than a bottom-tier shared plan. It wants a current PHP version, a MySQL or MariaDB database, and enough memory and CPU to handle its module-heavy back office. A good VPS or a mid-tier managed plan runs it comfortably, and adding object caching helps a busy PrestaShop store the same way it helps WooCommerce. As with any self-hosted cart, the uncacheable checkout is the capacity constraint, so size the plan around concurrent buyers rather than catalogue size.

OpenCart: the lightest of the three

OpenCart is the most modest of these carts and runs on relatively humble hardware — a decent shared plan can host a small OpenCart store, and a VPS handles a larger one easily. It still needs a current PHP version, a MySQL/MariaDB database and HTTPS, and it still can't cache checkout. OpenCart suits owners who want a straightforward, lightweight self-hosted store without Magento's overhead. As traffic grows, the same rule applies: watch concurrent-checkout capacity and move to a VPS or managed plan before a busy season.

Choosing a host for a non-WooCommerce cart

Match the host to the cart's weight: Magento needs a VPS, managed cloud or dedicated server with 4 GB+ RAM and the full search/cache stack; PrestaShop wants a solid VPS or mid-tier managed plan; OpenCart is happy on a good shared plan to start. Across all of them, confirm current PHP, a real database on SSD/NVMe, HTTPS, backups and enough capacity for concurrent checkouts. If you're weighing WooCommerce instead — the lightest and most popular option — start with its hosting requirements and compare from there.

Why Magento's stack changes the hosting math

Magento's hardware demands come from its architecture, not from bloat. It leans on several supporting services that each want their own memory and CPU: OpenSearch (or Elasticsearch, now deprecated) powers catalogue search and can't be skipped on a real store; Redis or Valkey holds sessions and cache so the database isn't hammered; and Varnish provides full-page caching in front of the application. Layer those on top of PHP-FPM and MySQL and you understand why 4 GB of RAM is a floor rather than a target — a busy Magento store with a large catalogue and many store views is comfortable with 8 GB or more. This is also why Magento performance tuning is a specialist skill: the indexers, cache warming and cron jobs all need to be configured correctly, and a misconfigured cache can make even a powerful server feel slow. If you've only ever run WooCommerce, budget for both more hardware and more setup time when you move to Magento.

Managed Magento versus self-managing a server

The honest split is about skills and time. If you have a developer or agency comfortable with Linux, the OpenSearch/Redis/Varnish stack and Magento's deployment model, self-managing a VPS or dedicated server gives you the best value and full control — you provision the box, install the stack, and own updates, security and the PCI configuration. If you don't have that expertise in-house, pay a managed Magento-capable host to run the stack, apply patches and keep it fast, and treat the higher price as buying back your team's time and reducing risk on a platform where a broken deploy can take checkout down. PrestaShop and OpenCart forgive more, but the same logic applies at a smaller scale: match the amount of server management you take on to the skills you actually have, and don't run a store you can't confidently keep patched. A store that handles payments is the wrong place to learn sysadmin on the job.

In short, let the cart set the floor. Magento's stack makes it a VPS-or-above platform where 4 GB of RAM is the starting line and real expertise is assumed; PrestaShop is comfortable on a solid VPS or mid-tier managed plan; and OpenCart is light enough to start on good shared hosting. Whichever you run, the constant is the uncacheable checkout, so size for concurrent buyers, keep the software patched, and match the amount of server management you take on to the skills you genuinely have rather than the ones you hope to acquire under fire.