Every Magento server needs the same weekly work: patches, indexers, cron, search, cache, backups and someone to answer when checkout breaks. The real question is who does it. This guide compares running the server yourself with having a host run it, so you can decide. If nobody on your team owns servers, managed Magento hosting is usually the safer default.
What a Magento server needs every week
Magento is not a site you install once. Its stack has several moving parts, and each one fails in its own way.
- Security patches. Adobe releases security patches several times a year, and Magento stores are a common target. A patch that waits a month is a month of exposure.
- Indexers and cron. Prices, stock and search results update through scheduled jobs. When one gets stuck, the storefront shows old data and nobody gets an error.
- Search. Magento 2.4 needs OpenSearch or Elasticsearch. It has to be sized, secured and kept running.
- Cache and sessions. Varnish serves cached pages and Redis keeps sessions and the backend cache in memory. Both need tuning for your catalogue.
- PHP-FPM and MySQL. Checkout cannot be cached, so it depends on these two being sized and tuned for your orders.
- Backups. Daily, stored off the server, and tested by restoring them.
- Monitoring. Something has to notice a stuck indexer, a full disk or a failing payment webhook before a customer does.
Who does what
| Job | Self-managed | Managed |
|---|---|---|
| Server hardware and network | Host | Host |
| OS and stack updates | You | Host |
| Magento security patches | You | Host with your developer |
| Indexer, cron and search monitoring | You | Host |
| 24/7 response when the store is down | You | Host |
| Backups and restore tests | You | Host |
| Your theme, extensions and code | You | You |
The last row does not change. A managed host runs the server, not your code. Slow extensions are fixed together with your developer or agency.
When running it yourself makes sense
- You have a sysadmin or DevOps engineer who already runs production Magento.
- Your store can tolerate being down overnight or on a weekend.
- You enjoy tuning, and the time spent on it costs less than a managed fee.
When managed hosting pays for itself
- No one owns the server. The developer who built the store is not an ops engineer, and should not be woken at 2 a.m.
- Sale days decide your month. Outages and slow checkouts cost the most when traffic peaks.
- You run client stores. Patching and monitoring many stores is easier when one team does it for all of them.
- You are still on Magento 1. Adobe stopped patching it in June 2020. A managed host can keep it hardened while you plan the move to Magento 2.
To compare, count the hours a month your team spends on the jobs in the table, price them at what those hours really cost, and set that against the managed fee. The Magento hosting page lists the plans and what each one includes.
How to choose a host
Whichever route you take, ask any host four questions:
- Is the stack built for Magento, or generic PHP hosting?
- Who notices a stuck indexer or cron job?
- Who applies security patches, and when?
- Who answers at 2 a.m., and how fast?
Our guide to choosing Magento hosting by store size goes deeper on each hosting category.
Frequently Asked Questions
What does managed Magento hosting include?
A server built for Magento, with patching, 24/7 monitoring, daily backups with restore tests and incident response. Your developer or agency still owns the code, theme and extensions.
Is managed hosting worth it for a small Magento store?
If nobody on your team can run production servers, yes. A small store can lose a day of sales to a stuck indexer or a failed patch. If you have an engineer who already runs Magento, self-managed can be enough.
Does managed hosting fix slow extensions?
No. A managed host shows which extension or query is slow and works with your developer on the fix. Fixing or rewriting extension code is development work, not hosting.