Magento hosting in India: requirements, what drives the cost, and the right setup
TL;DR: Magento is a heavy application that needs a full stack of services, not just PHP and a database: a search engine, a cache, ideally a full-page cache, and a web server tuned for it. That rules out shared hosting. A small store can run on a well-specced VPS with about 4 to 8 GB of RAM, larger catalogues and busy stores need dedicated or multi-server setups, and the version you pick decides which PHP and database your host must support. The cost is driven by server size, managed support, search and caching services, and your Magento licence if you choose Adobe Commerce rather than the free Open Source edition.
Why Magento hosting is different
A WooCommerce store is WordPress plus a plugin. Magento is a separate, much larger application framework. It builds pages from layers of configuration, relies on a search engine to power category and search pages, and uses caching heavily to stay fast. Without that caching it can feel slow even on a strong server.
That means hosting a Magento store is closer to running a small platform than hosting a website. The server needs the right services installed and tuned, and someone needs to keep them patched.
If you are weighing it against a lighter option, the sizing difference is clear in how much RAM a WordPress and WooCommerce site needs on a VPS. Magento needs more.
The software stack by version
Requirements change with each Magento release, and your host must support the version you run. Figures below come from third-party version trackers and hosting vendors. Always confirm against Adobe's official system requirements before you commit.
| Component | 2.4.8 | 2.4.9 |
|---|---|---|
| PHP | 8.3 or 8.4 | 8.5 |
| Database | MySQL 8.4 or MariaDB 11.4 | MySQL 8.4 or MariaDB 11.8 / 12.3 |
| Search | OpenSearch (2.x to 3) | OpenSearch 3 |
| Cache and sessions | Valkey or Redis | Valkey 9 |
| Full-page cache | Varnish | Varnish 8 |
| Web server | nginx recommended | nginx 1.30 |
| Composer | 2.x | 2.10 |
Three things stand out.
PHP 8.5 for 2.4.9. Many hosts have not rolled out the newest PHP. If your host cannot offer the PHP version a release requires, you cannot run that release. Ask before you sign up.
Search is mandatory. Magento needs OpenSearch. Elasticsearch has been dropped for 2.4.9, so a host that only offers Elasticsearch will not do.
Support windows. One tracker lists 2.4.8 as supported until May 2028 and 2.4.9 until May 2029. Running an out-of-support version means no security patches, which is not an option for a store that takes payments.
Web server support is reported inconsistently across sources. nginx is the safe choice. Check Adobe's documentation if you want Apache.
How much server you need
Hosting vendors' published guidance clusters around these figures. Treat them as starting points, then test with your own catalogue.
| Store size | CPU | RAM | Storage |
|---|---|---|---|
| Development or very small catalogue | 2 cores | 4 GB | 120 GB SSD |
| Production, moderate traffic | 4 cores | 8 GB | 240 GB NVMe |
| Large catalogue or heavy traffic | 8+ cores | 32 GB or more | 500 GB+ NVMe |
Commonly recommended PHP settings include a memory limit of around 2 GB, a long maximum execution time for admin and indexing tasks, and a large OPcache. A web server and database on the same machine is acceptable for a small store. In production, separating them is the usual next step as traffic grows.
Catalogue size matters as much as traffic. Thousands of products with many attributes make indexing and search heavier, and checkout is expensive on any store.
Why shared hosting does not work
Shared hosting fails Magento for practical reasons, not just performance.
- No control over services. You cannot install OpenSearch, Valkey or Varnish.
- Resource limits. Shared plans cap memory, CPU and processes well below what Magento needs for indexing and cron jobs.
- Long-running tasks. Reindexing and import jobs get killed by shared-hosting limits.
- No shell access, in many cases, which makes Composer-based installs and updates impractical.
If you are tempted by a cheap plan, read when to move from shared hosting to a VPS. For Magento you are already past that threshold on day one.
VPS, cloud, dedicated or managed
| Option | Fits | Trade-off |
|---|---|---|
| Unmanaged VPS | A technical team comfortable running Linux services | You install, tune and patch everything |
| Managed VPS | A small store without in-house server skills | Higher price, support included |
| Cloud (scalable) | Traffic spikes, flash sales | More moving parts and bills that vary |
| Dedicated server | Large catalogues, steady heavy traffic | Highest fixed cost, needs capacity planning |
| Magento-specialist managed hosting | Stores that want the stack pre-tuned | Costly, but fewer operational surprises |
For a first Magento store, a managed VPS with the stack pre-installed is the most forgiving route. The decision between VPS and dedicated is covered in VPS vs dedicated server for a small business, and the difference between cloud and VPS in cloud hosting vs VPS hosting.
What drives the cost
Published price lists vary widely, so rather than quote numbers that go stale, here is what actually moves the bill.
- Server size. Cores, RAM and NVMe storage are the largest line item.
- Managed support. Having someone else patch, monitor and tune adds to the monthly cost but removes risk.
- Search and cache services. Hosted search or a separate cache node adds cost if you do not run them on the main server.
- Licence. Magento Open Source is free. Adobe Commerce is licensed and priced through quotes, which is a different order of cost entirely.
- Extensions and themes. Many useful features come from paid third-party extensions.
- Development time. Customisation, upgrades and security patching take developer hours, often the biggest cost over a year.
- CDN and backups. A CDN and off-server backups are inexpensive insurance.
Ask any host for a written quote that states the exact specs, which Magento versions and PHP version are supported, and what is included in management.
Indian store specifics
- Hosting location. Servers in India reduce latency for Indian shoppers and can simplify data-location questions. See how to speed up WordPress for Indian visitors for the principles, which apply here too.
- Payments and GST. Indian gateways and GST-compliant invoicing usually come from third-party extensions. Confirm they support your exact Magento version before you commit.
- Sale traffic. Festival peaks can multiply load. Plan capacity ahead and rehearse with load testing before a sale.
- Security patching. Magento publishes security patches that must be applied in order. PHP-level flaws such as PHP2Shell also affect your store, so choose a host that patches the runtime promptly.
A checklist before you choose a host
- Which Magento versions do you support, and do you offer PHP 8.5?
- Is OpenSearch available, and is it included or extra?
- Do you provide Valkey or Redis and Varnish?
- How much RAM and CPU are included, and can I scale without migrating?
- Is the server in India, and what is the network quality?
- Who applies security patches and OS updates?
- How are backups taken and where are they stored?
- Can you handle a Magento upgrade or point me to someone who can?
- What is the response time for support during a sale?
- What happens to my data and contract if I leave?
FAQs
Can I host Magento on shared hosting?
No in practice. Shared plans do not let you install the required search engine and cache services, and they impose resource limits that break indexing and cron jobs.
What is the minimum server for Magento?
Hosting vendors commonly give 2 CPU cores and 4 GB of RAM as a minimum for a small store, with 8 GB and 4 cores recommended for production. Larger stores need much more.
Which PHP version does Magento need?
It depends on the release. Version 2.4.8 supports PHP 8.3 and 8.4. Version 2.4.9 requires PHP 8.5. Check the official requirements for the exact release you plan to install.
Is Magento Open Source really free?
The software licence is free. You still pay for hosting, developers, extensions, themes and support. Adobe Commerce, the paid edition, has an additional licence cost.
Do I need a separate server for the database?
Not for a small store. As traffic and catalogue size grow, separating the web server and database is a common step, and large stores often add dedicated nodes for search and cache.
Is Magento better than WooCommerce?
Magento suits large catalogues and complex requirements, with a much higher hosting and development cost. WooCommerce is simpler and cheaper to run for most small and mid-sized stores. The right choice depends on your catalogue and budget.
Do I need Varnish?
It is the standard full-page cache for Magento and makes a large difference to speed under load. Some managed hosts provide an equivalent built-in cache, so ask what is included.
How do I know if my Magento version is still supported?
Check Adobe's lifecycle policy or a version tracker. Out-of-support versions do not get security patches, which is a risk for any store that handles payments.
Conclusion
Magento rewards a proper hosting setup and punishes a cheap one. Match the server to the version you run, insist on the right PHP, search and cache services, and decide early whether you will manage the stack yourself or pay for management. For most new stores, a managed VPS with Indian data-centre latency is the sensible starting point.
HostCloud can help you size a server for your catalogue. See our plans at https://hostcloud.in.
Sources: