High Availability Magento Hosting in London
EveryHost High Availability is managed Magento hosting on multi-node clusters designed for failover, in our London data centre. There are two plans: HA Starter at £799 a month (multi-node web tier with HA database options) and HA Pro at £1,299 a month (multi-node with redundancy across tiers), both ex VAT. Both include Sentinel Pro security, 24/7 monitoring, staging with release process support, on-server backups, 99.5% uptime and managed migration. Each cluster is sized from your store's measured peak load and the exact build is confirmed with you.
High availability Magento plans and prices
Multi-node clusters designed for failover and mission-critical Magento commerce.
| Plan | HA StarterDesigned for failover | HA ProMission-critical commerce |
|---|---|---|
| Price per month (ex VAT) | £799 | £1,299 |
| Resources | Multi-node web tier + HA database options | Multi-node + redundancy across tiers |
| Security | Sentinel Pro (active tuning during attack) | Sentinel Pro (active tuning during attack) |
| Backups | On-server (Bastion off-site add-on available) | On-server (Bastion off-site add-on available) |
| Stack | nginx, Varnish, Redis or Valkey, OpenSearch and PHP-FPM on NVMe, built to your setup after ordering | nginx, Varnish, Redis or Valkey, OpenSearch and PHP-FPM on NVMe, built to your setup after ordering |
| Monitoring | 24/7 monitoring + failover-ready design | 24/7 monitoring + failover-ready design |
| Staging | Staging + release process support | Staging + release process support |
| Performance | Redis or Valkey + cache + search (architected) | Redis or Valkey + cache + search (architected) |
| Support | 24/7 UK support + architecture support | 24/7 UK support + named technical lead |
| Migration | Managed migration included | Managed migration included |
| Order | Talk to Sales about HA Starter | Talk to Sales about HA Pro |
Prices ex VAT. UK VAT at 20% is added. The exact build is confirmed with you before you order.
What high availability means for a Magento store
Adobe's reference architecture sets out its recommended setup for a scalable Magento site, including sites that require high availability.
Adobe's documented pattern, illustrated
- Step 1Requests are spread across the web nodes by load balancing.
- Step 2If a web node goes offline, the other web nodes keep serving requests.
- Step 3Cache and sessions, the database and shared media sit outside any single web node.
Every HA cluster is built to order around your store's traffic and needs, so the parts and the number of servers vary from build to build.
- Scale web nodes for traffic and redundancy, with a master node that runs cron, or separate admin and worker nodes. Source: Adobe reference architecture.
- For sites that need high availability, use a two-tier Varnish setup with SSL-terminating load balancing. A Varnish cluster can scale to a site's traffic. Source: Adobe reference architecture.
- Hold cache and sessions outside any single web node: consider a separate Redis instance for sessions, and Redis instances can be split by cache type. Source: Adobe advanced setup.
- Set the database up for recovery: replica databases enable quick recovery and backups. Replication itself is set up separately from Magento's own configuration. Source: Adobe advanced setup.
- Share media between nodes: keeping media on each server's own filesystem is inefficient for complex, multi-server configurations, and the Remote Storage module can put pub/media in remote object storage. Source: Adobe remote storage.
- Make cache clears reach every cache node: multiple Varnish instances are supported out of the box, and every Varnish host is listed so a cache clear purges all of them. Source: Adobe multiple Varnish instances.
Web nodes serve the requests that cannot be cached. Adobe estimates that one CPU core serves about two, and up to four, Magento requests, so the cores you need are the expected requests divided by two, plus the expected cron processes. Web nodes also need a fast enough network link to the cache servers. Source: Adobe hardware recommendations.
Adobe also notes that a specialist host may recommend a different setup that is equally effective.
Our HA builds use separate web, database and cache nodes, and the exact build is confirmed with you.
Is HA right for your store? Dedicated or High Availability
A cluster is justified when a single server outage is unacceptable, or when your measured peak concurrency is more than one large server can carry with headroom.
Below that, a well-specified single dedicated server with tested backups is usually the better trade: fewer moving parts, at a fraction of the cost.
| Plan | Price per month (ex VAT) | Resources |
|---|---|---|
| Dedicated DS1Dedicated performance for revenue-critical stores | £249 | 8 cores / 16 threads • 64GB RAM • 2× 480GB NVMe (RAID1) |
| Dedicated DS2High-traffic dedicated | £399 | 12 cores / 24 threads • 128GB RAM • 2× 1TB NVMe (RAID1) |
| Dedicated DS3Peak-season resilience | £549 | 16 cores / 32 threads • 192GB RAM • 2× 4TB NVMe (RAID1) |
| HA StarterDesigned for failover | £799 | Multi-node web tier + HA database options |
| HA ProMission-critical commerce | £1,299 | Multi-node + redundancy across tiers |
The usual path as a store grows:
- A single node.
- A larger dedicated single node.
- The database and search separated onto their own servers.
- Multiple web nodes with load balancing.
The trigger for the last step is when a single server outage is no longer acceptable, or when PHP is saturating on one node.
Compare Magento dedicated servers, see the High Availability plan cards, read the Magento server sizing guide or try the Magento server calculator.
Planning for peak trading
Adobe sizes web nodes to process all incoming requests without queueing them, and says you can add web nodes or cores by hand for an active sales period. Source: Adobe hardware recommendations.
We size a cluster from measured peak concurrency, uncached request rate and database write load, not from monthly visits.
The signals to watch are:
- CPU and memory on each node.
- Replication lag, if replicas are used.
- OpenSearch heap during a reindex.
- Queue backlog.
- Cache hit ratio.
For a peak-season checklist, read our Magento Black Friday readiness checklist and Magento checkout speed at peak. If you want us to run the load test and stay on call through the peak, see Magento Surge Shield.
Security on HA: Sentinel Pro and DDoS mitigation
Sentinel is our Magento-tuned security monitoring. It covers admin password guessing and unusual sign-ins, card-skimmer changes to checkout and payment files, malware and unexpected file changes, and bots and traffic floods, which rate limiting slows. It flags missing Magento patches against Adobe's security bulletins.
Our UK engineers act on its alerts, block sources at the server firewall and tell you what happened in plain English. Sentinel is not in the request path, so it adds no delay to page loads. It does not replace Magento security patches.
HA plans include Sentinel Pro, which adds active tuning during an attack and priority response, at no extra cost. See how Sentinel protects Magento stores.
DDoS attacks are handled separately. Every server sits behind upstream, network-level DDoS mitigation, which absorbs volumetric floods before they reach the server. Sentinel and our engineers deal with smaller floods from individual sources.
Monitoring, staging and support
Every plan has uptime and resource monitoring. Dedicated and HA plans add 24/7 proactive alerting, and both HA plans come with 24/7 monitoring and a failover-ready design.
Both HA plans include staging with release process support. Changes are made staging-first, in defined maintenance windows, with a rollback plan.
HA Starter includes 24/7 UK support and architecture support. Architecture support means our engineers plan your cluster with you. We size it from your measured peak load before we build it, review it with you ahead of major sales periods, and advise on changes as your store grows.
HA Pro includes 24/7 UK support and a named technical lead. On HA Pro, a named engineer is assigned to your store and handles most of your work, so you usually deal with someone who already knows your setup. The wider UK team covers when they're away.
Support comes from UK-based Magento engineers by ticket, 24/7, through our support portal or by email to support@everyhost.co.uk, which opens a ticket. Phone: 0333 577 6191, for sales and general enquiries.
Backups
Backups are held on the server, with retention set by the disk space available, and our engineers handle restores.
Bastion off-site backup is an optional encrypted copy away from the server, priced by the storage you use.
Migrating an existing store to a cluster
Migration is free.
- We assess your current store.
- We copy it to staging.
- We test it on staging.
- We schedule the cutover with you, in your lowest-traffic hours.
Most stores are live within 24–48 hours, with minimum downtime.
See how our free Magento migration works.
The Magento stack on every node
The default stack is nginx, Varnish, Redis or Valkey, OpenSearch and PHP-FPM on NVMe, built to your setup after ordering. Redis or Valkey is set to match your Magento version. We can set up a CDN on HA builds and advise whether your store needs one.
| Release | PHP | Other components | Adobe support ends |
|---|---|---|---|
| 2.4.9 | 8.5 | MySQL 8.4 or MariaDB 12.3, OpenSearch 3, Valkey 9, Varnish 8 | 31 May 2029 |
| 2.4.8 (2.4.8-p5) | 8.4 or 8.3 | OpenSearch 3, Valkey 8.1, Varnish 8 | 31 May 2028 |
| 2.4.7 (2.4.7-p10) | 8.3 or 8.2 | MariaDB 10.11 or 11.8, Valkey 8.1 (Redis not supported) | 31 May 2027 |
Adobe publishes these support dates for Adobe Commerce. Source: Adobe Experience League, the Adobe Commerce system requirements and Adobe Commerce lifecycle policy, checked 25 September 2026.
More on each part: Redis and OpenSearch for Magento, Valkey for Magento and Magento end of life dates.
London data centre and uptime
Servers are in a Tier 3 data centre in London, so your store is hosted in the UK.
Every plan has 99.5% uptime, on infrastructure with N+1 redundant power, cooling and network.
An HA cluster usually takes at least a few days to set up, depending on hardware availability.
High availability across both sites is a custom quote: an engineer replies with a spec and a fixed monthly price, usually the same working day. Ask for a custom quote.
High availability Magento hosting FAQs
Plan a high availability Magento cluster
High Availability from £799/mo ex VAT. The exact build is confirmed with you before you order.