Magento Support and Maintenance, Included with Your Hosting
Magento support and maintenance is included with every EveryHost hosting plan. Our UK engineers patch and look after the server and the stack under your store, apply Magento security patches in staging first, watch the server around the clock and restore backups when you need them, with 24/7 UK support by ticket. We only support stores we host: there are no standalone support plans or retainers, and support comes with your hosting. See plans and prices for what each plan includes.
What Magento support and maintenance covers
Many providers use "support" and "maintenance" to mean the same thing. In practice, maintenance is the planned work that keeps a store patched and stable, and support is the help you get when something goes wrong. For a Magento store, the work usually splits like this:
| Work | What it means |
|---|---|
| Server and stack maintenance | Operating system, PHP and service updates, and security hardening |
| Security patching | Applying Adobe's security releases and emergency hotfixes, tested on staging first |
| Monitoring | Uptime, server health and security monitoring, with alerts |
| Backups and restores | Regular backups, and help restoring them |
| Extension and theme updates | Updating third-party code and testing it on staging |
| Bug fixes and custom code | Developer time to fix faults and make changes to the store |
| Version upgrades | Moving to a newer 2.4.x release |
The first four sit with the host. The last three depend on your extensions and custom code, so they sit with whoever looks after your code.
Magento support and maintenance included with EveryHost hosting
Every EveryHost hosting plan includes the maintenance work on the server and the stack underneath your store:
- server-level patching, PHP updates and security hardening;
- nginx, Varnish, Redis or Valkey, OpenSearch and PHP-FPM, configured for your store, with the stack matched to your Magento version;
- Magento security patches, applied in staging first, then coordinated to production with you;
- monitoring, with a 99.5% uptime SLA on every plan;
- Sentinel, our Magento-tuned security monitoring, at no extra cost;
- backups held on your server, with restores handled by our engineers, and Bastion, our encrypted off-site backup, as an optional add-on;
- a staging environment;
- 24/7 UK support by ticket.
Sentinel on every plan
Sentinel reads your server's logs, blocks abusive sources at the server firewall, and our engineers review what it finds. Managed VPS plans include Sentinel Plus: bot protection, file integrity monitoring and stricter blocking rules at the server firewall. Dedicated and high availability plans include Sentinel Pro, which adds active tuning during an attack and priority response from our engineers. Sentinel is not a web application firewall, a CDN or a proxy, and it does not sit in front of your store. If you want an edge WAF or CDN as well, we recommend putting Cloudflare in front of your store, alongside Sentinel. See how Sentinel protects Magento stores.
Who does what: EveryHost, your developer and you
Clear boundaries prevent the worst support problem: everyone assuming someone else is handling it. Even Adobe's own cloud leaves merchants "responsible for the compliance of their custom code, system and network processes, and organization" (Adobe shared responsibility). On a hosted Magento Open Source store, the server is ours and the code is yours or your developer's.
| Task | EveryHost | Your developer or agency | You |
|---|---|---|---|
| Server, operating system and PHP patches | Included | ||
| nginx, Varnish, Redis or Valkey, OpenSearch configuration | Included | ||
| Magento security patches | Applied in staging first, then coordinated to production | Tests custom code against the patch | Agrees the release window |
| Version upgrades | Prepares the stack and staging | Upgrades and tests the code | Signs off the release |
| Extensions, theme and custom code | Quoted separately if you want our help | Usually | |
| Content, products and orders | Yes |
Upgrades between Magento versions are a project rather than routine maintenance: we prepare the stack and staging and work alongside your developer or agency. See Magento upgrades and security patching. We work with agencies as well as directly with merchants. If you are an agency, see Magento hosting for agencies.
Magento support packages: support comes with your hosting plan
Elsewhere, Magento support packages are usually sold separately from hosting: an hourly rate, a fixed monthly fee, or tiers of included hours. The published entry prices for standalone monthly Magento support from UK providers we found on 10 October 2026 ranged from about £200 to £750 a month, and published developer rates from £95 to £100 an hour, all ex VAT where stated. That is a sample of five providers that publish prices, not a market survey.
We do it differently. Our Magento support package is your hosting plan: support and maintenance of the server and stack are included in the monthly price, with no separate support contract. Every plan includes priority UK support. Dedicated plans add account management, and high availability plans add architecture support. Plans start from £119 a month + VAT for a Managed VPS, £249 for a dedicated server and £799 for high availability. See plans and prices, our managed Magento VPS and our dedicated Magento servers.
How to get Magento support
Raise a support ticket at any time, day or night: our UK engineers work on tickets 24/7. You can raise and follow tickets in the client area, where you also manage billing and see your services. For sales and general enquiries, call 0333 577 6191 or contact us.
If your store is hosted elsewhere, we cannot support it there. We can move it to us: a move from another host to EveryHost is free, with minimum downtime, and most stores are live within 24 to 48 hours. See free Magento migration.
How we handle Magento security patching
Adobe published six Adobe Commerce security bulletins in 2025, and six so far in 2026 including one out-of-band emergency fix (7 September), checked on 11 October 2026. Most fall on the second Tuesday of a month (Adobe security bulletins). Our approach is staging-first: patches are applied in staging first, then coordinated to production with you.
For what the -pN version numbers mean, see Magento security patches explained, and for planning review windows around Adobe's releases, see our Adobe Commerce patch cadence guide.
What happens if a Magento store falls behind
Falling behind is not just a missed feature release. It changes what fixes you can get:
- Patches stop. "Open Source merchants can only download patches for version 2.4.7 or later" (Adobe KB, APSB26-138). See Magento end of life dates.
- The stack goes out of support. PHP 8.1 reached end of life on 31 December 2025 (php.net end of life), and PHP 8.2 security support ends on 31 December 2026 (php.net supported versions). MySQL 8.0 reached end of support on 30 April 2026 (Adobe system requirements).
- Unpatched stores get attacked. A week after Adobe fixed the CosmicSting flaw in June 2024, security firm Sansec measured only a quarter of Magento stores as patched. By October 2024 it counted 4,275 stores hacked through the flaw, about 5% of all Magento stores (Sansec). Those figures are Sansec's own telemetry.
- Patching late does not undo a break-in. After CosmicSting, "existing secret keys were not invalidated automatically", so a patched store could still be exposed until its keys were rotated (Sansec).
Common Magento problems and where they sit
These are common, documented Magento failures, listed by the symptom a customer usually notices first. Server-side causes such as cron and caching sit with us; code, extension and configuration causes sit with your developer or agency.
| Symptom | Usual cause | Source |
|---|---|---|
| Emails, sitemaps, price rules or currency rates stop updating | Cron is not running. Magento needs cron for "price rules, newsletters, sitemap generation, currency rate updates, and indexing". | Adobe cron guide |
| "Reindex Required" in the admin | "the indexers cannot be updated automatically", usually because cron is not configured | Adobe index management |
| Slow site, heavy database load, stuck cron jobs | "Flat tables and indexers remain enabled" | Adobe knowledge base |
| Checkout broken after upgrading to 2.4.7 or later | Content Security Policy runs in restrict mode on payment pages from 2.4.7, so unlisted inline scripts are blocked | Adobe knowledge base |
| Features stop working after installing an extension | "conflicting modules that cannot both be enabled at the same time" | Adobe module guide |
| Old content or broken pages after a change | Stale caches, generated code or static files | Adobe debugging guide |
Related reading
For the hosting side, see Magento hosting, our guide to what a store needs from a server, and our Magento hosting UK plans. Still on Magento 1? See Magento 2 migration. If you are weighing up running Magento yourself on AWS, see Magento hosting on AWS vs managed UK hosting.
Frequently asked questions
Magento support that comes with your hosting
Tell us about your store and we will recommend the right plan, with support and maintenance included.