Magento logo
CMS & Commerce

Magento Hosting on Your Own VPS

Magento 2 on a server actually sized for it, with the search and cache services it requires.

Size a server for Magento

Every stop is a real configuration you can deploy. Priced per month and billed monthly, exclusive of 18% GST.

4 vCPU
2 vCPU $3.93 a month 64 vCPU
16 GB
4 GB $7.86 a month 128 GB
160 GB
40 GB $6.05 a month 2000 GB

What Magento is

Magento 2 is the heaviest application on this page, and it is worth saying plainly: it does not run acceptably on shared hosting, and it barely runs on a small VPS. It is a large PHP application with a demanding dependency list — Elasticsearch or OpenSearch for catalogue search, Redis for cache and sessions, MySQL, a message queue, and ideally Varnish in front.

Those are requirements, not optimisations. Magento 2.4 refuses to install without a supported search engine. Indexers rebuild in the background and consume real CPU. Static content deployment during a deploy is memory-hungry enough to fail on a 2 GB machine. Anyone quoting you Magento on a small plan has not run it.

What you get for that weight is a genuinely capable commerce platform: multi-store, multi-currency, complex pricing rules, and B2B features that would be plugin sprawl elsewhere. It suits catalogues and business rules that have outgrown simpler platforms.

“Magento Open Source software delivers basic eCommerce capabilities to build a unique online store from the ground up.”

— Magento Open Source, on GitHub

Why run Magento on a VPS

Enough memory to install and reindex, which is where undersized servers fail first.

Elasticsearch, Redis and Varnish on the same machine, all under your control.

Root access for PHP memory limits and cron, both of which Magento needs raised.

Resize as the catalogue grows, rather than migrating.

Magento features

Multi-store and multi-currency from one installation

Catalogue search via Elasticsearch or OpenSearch

Redis for cache and session storage

Varnish full-page caching

Complex catalogue and cart price rules

B2B features including company accounts and quotes

CLI tooling for deploys, indexers and cache management

Magento hosting requirements

The recommended starting point for Magento, not a hard floor — size it on the sliders.

Memory16 GB. Not a suggestion — Elasticsearch alone wants several, before PHP and MySQL
CPU4 vCPU minimum; indexers and static deployment are CPU-heavy
Storage160 GB; media, indexes and generated static content all accumulate
Operating systemUbuntu 24.04 LTS or Debian 13
Installs onUbuntu 24.04 LTS, Debian 13 (Trixie)
Ready inAbout 25 minutes
Smallest server2 vCPU · 4 GB memory · 40 GB disk

How deployment works

Magento Open Source 2 is installed with PHP-FPM at a raised memory limit, MariaDB and OpenSearch, and the store and its admin are ready when it finishes; Redis and Varnish can be added in front of it. Cron must be running for indexers, and static content deployment during a deploy needs headroom — this is the step that fails on undersized servers. Composer authentication keys from your Adobe account are needed to install extensions and upgrades through Composer.

It is your server. Magento is installed directly on your VPS or VDS, not inside a container we manage. You get root over SSH, you can install anything alongside it, change its configuration, or remove it entirely. We do not hold a key to it.

What people run it for

Large catalogues

Tens of thousands of SKUs with attributes and layered navigation.

Multi-store operations

Several storefronts, currencies and tax rules from one backend.

B2B commerce

Company accounts, negotiated pricing and quote workflows.

Migrating off Magento 1

A supported platform on infrastructure sized for the real thing.

Magento hosting questions

No, not acceptably. It requires Elasticsearch, Redis and raised PHP memory limits, and needs background cron for indexers. A VPS is the realistic minimum.

Deploy Magento on your own server

Root access, your choice of size, and no container between you and the application.