--- title: "Hosting per CMS: Magento, PrestaShop, Sylius — Fast-Mage" description: "E-commerce hosting and managed services per CMS: Magento, PrestaShop, WooCommerce, Sylius, Drupal, Akeneo, Symfony, Front-Commerce." url: "https://www.fast-mage.com/en/solutions-2" type: static generatedAt: "2026-08-11T15:49:26.285Z" --- SOLUTIONS / PER CMS STACK / E-COMMERCE # Hosting and managed services, tuned per CMS. We are sysadmins and senior developers running Linux infrastructure for e-commerce. Each CMS gets its own stack profile: Varnish VCL, Redis topology, OpenSearch tuning, PHP-FPM pools, queues. No generic shared template. | Code | Stack | Profile | Jump | | --- | --- | --- | --- | | M2 | Magento Open Source | Core business since 2009. 75 percent of active fleet. | [#magento](#magento) | | PS | PrestaShop | French open source, SMB and mid-market. | [#prestashop](#prestashop) | | WC | WooCommerce (WordPress) | High-traffic Woo with PHP-FPM tuning. | [#woocommerce](#woocommerce) | | SY | Sylius | Symfony-native, often forgotten by generic hosts. | [#sylius](#sylius) | | DR | Drupal (Commerce, Content) | Editorial-heavy and Drupal Commerce. | [#drupal](#drupal) | | AK | Akeneo PIM | Product Information Management at scale. | [#akeneo](#akeneo) | | SF | Symfony (custom apps, APIs) | Custom Symfony projects, API Platform, internal tools. | [#symfony](#symfony) | | FC | Front-Commerce (headless) | Headless PWA on top of Magento, Sylius or BigCommerce. | [#front-commerce](#front-commerce) | Core business since 2009. 75 percent of active fleet. Mid-market and large catalog stores. We run Magento Open Source on tuned LAMP stacks sized for catalogs of 10k to 500k+ SKUs, with B2B price lists, multi-store, multi-website and EAV pressure on MariaDB. field notes, Typical footprint: 12k to 200k SKUs, 50 to 1 200 orders/day, 10 to 60 concurrent admin users. Audits show recurring wins on N+1 collection loads, layered nav cache key cardinality and indexer fragmentation. tech.profile 4 layers - 01 Full Page Cache on Varnish, custom VCL with tag-based purge wired to Magento's cache.refresh and product save events. - 02 Redis split for session, default cache and FPC backend. Sentinel option on HA tier for automatic failover. - 03 OpenSearch (Elastic-compatible) cluster for catalog and search, with synonym sets and stopword tuning per store view. - 04 PHP-FPM pool per project, dedicated Unix user, opcache and JIT tuning, RabbitMQ for async consumers and indexers. French open source, SMB and mid-market. PrestaShop 1.7 and 8.x in production across agencies and direct merchants. We handle module-heavy stores where SmartyCache, ObjectModel hydration and admin tab leaks dominate the perf profile. field notes, We see strong gains by killing legacy /override/ patches, moving HTTPS cache rules to Varnish and pinning PHP 8.2+ with strict memory limits per FPM pool. tech.profile 3 layers - 01 Varnish in front with PrestaShop-aware VCL, ESI for cart and customer block. - 02 Redis as cache backend (PrestaShop\PrestaShop\Core\Cache) plus session offload, OPcache file_cache for hybrid containers. - 03 OpenSearch optional via dedicated connector for catalogs above 30k references. High-traffic Woo with PHP-FPM tuning. WooCommerce on hardened WordPress. Catalogs from 500 to 50k SKUs, marketing pressure (PSD2, Stripe, Klaviyo, multi-currency) and heavy plugin stacks. We treat it as a real e-commerce workload, not a blog. field notes, Common rescues: removing transient autoload spikes, isolating the admin from front-end PHP-FPM pool, pinning High-Performance Order Storage (HPOS) where available. tech.profile 3 layers - 01 Varnish FPC with WooCommerce cookie rules (woocommerce_items_in_cart, woocommerce_cart_hash), per-route cache TTL. - 02 Redis Object Cache with persistent connection, configured to bypass cart, checkout, my-account. - 03 MariaDB tuning for wp_options autoload bloat, wp_postmeta indexing, transient cleanup cron. Symfony-native, often forgotten by generic hosts. Sylius 1.x on Symfony 6/7. Built for headless and custom catalog logic. We run it with the same rigor as Magento: queues, search cluster, dedicated cache layers, deploy pipeline. field notes, Most Sylius incidents we field are deploy-related (cache:clear in prod, missing APP_ENV=prod, RoR file ownership). Our Ansible playbooks fix that by construction. tech.profile 3 layers - 01 Varnish for the Shop bundle with VCL aware of Sylius channels and locales. - 02 Redis backend for Symfony cache pools and HTTP sessions. - 03 OpenSearch via SyliusElasticsearchPlugin, Messenger transports on RabbitMQ or Redis Streams for async indexing. Editorial-heavy and Drupal Commerce. Drupal 10/11 for content-driven sites, institutional portals and Drupal Commerce shops. We handle the same cache and search topology as on Magento, with Drupal-specific hardening. field notes, PHP-FPM pool per site, dedicated config sync workflow, drush in CI for cache rebuild and updb. tech.profile 3 layers - 01 Varnish with Drupal cache-tag invalidation (purge module, Symfony HttpCache headers). - 02 Redis for Drupal cache bins and form state. - 03 Search API + OpenSearch for facets and aggregated views. Product Information Management at scale. Akeneo Community and EE on Symfony, for clients syndicating product data to multiple Magento, PrestaShop or marketplace endpoints. We host the PIM and operate the export jobs. field notes, We pair Akeneo hosting with the merchant's storefront hosting on the same private network when possible. Sync latency drops, security perimeter shrinks. tech.profile 3 layers - 01 MariaDB tuned for high write throughput on product, attribute and completeness tables. - 02 OpenSearch as the PIM search backend, isolated from the storefront cluster. - 03 Background queue workers on Symfony Messenger, monitored per job type. Custom Symfony projects, API Platform, internal tools. Symfony 6/7 applications: B2B portals, API Platform backends, internal tooling for clients who already run their storefront with us. Same operational standards as e-commerce projects. field notes, Frequent use case: a Symfony API serving a headless front-end (Front-Commerce, custom Vue/React) backed by a Magento or Sylius core. tech.profile 3 layers - 01 PHP-FPM per pool, Symfony env vars managed via Ansible vaults, Doctrine connection pooling. - 02 Redis for cache.adapter.redis and Messenger transport, Varnish in front when the workload tolerates it. - 03 API Platform with rate-limit and JWT auth at the edge (Cloudflare or Nginx). Headless PWA on top of Magento, Sylius or BigCommerce. Front-Commerce as the headless storefront, served as a Node service in front of the commerce core. We host both layers, with the same monitoring, deploy and incident process. field notes, Two-tier deployment, observability on both the Node front and the PHP commerce core, single on-call rota. tech.profile 3 layers - 01 Node service behind Varnish or Cloudflare cache, SSR with stale-while-revalidate. - 02 GraphQL layer hitting Magento/Sylius via private network, Redis cache shared across pods. - 03 Build pipeline aligned with the merchant's commerce release cycle. CROSS-STACK BASELINE ## Same operational floor, every CMS. Whatever stack you run, the operational layer is identical. Hardened Debian, audited backups, on-call, observability, EU sovereignty. | Layer | Implementation | | --- | --- | | OS | Debian 12+ hardened, Ansible-managed, isolated Unix user per project. | | WAF | Cloudflare WAF, bot mitigation, custom rules per CMS, OWASP CRS tuned. | | OBSERV | Monit, Munin, 100+ custom probes, log shipping, dashboards on console.fast-mage.com. | | BACKUP | 9+ restore points per site, 2 backup providers in 2 EU countries, distinct from production host. | | SLA | 24/7 on-call. 30 min contractual response on high-priority during business hours. | | DATA | EU-hosted, GDPR-compliant. Providers: OVH, Scaleway, Hetzner, UpCloud, GCP, AWS. | Full disaster-recovery plan (RPO, RTO per scenario, HA topology) is available on request as a written annex to the service contract. 120+ active clients 10,000+ req/s peak per cluster 99.9 % availability SLA 2009 running since FIELD FEEDBACK ## What our clients say. > "La réactivité des équipes nous permet de faire évoluer nos sites rapidement, et de réagir vite en cas d'incident." > "La réactivité et l'efficacité de Fast-Mage nous permettent d'améliorer notre infrastructure." > "Une équipe compétente sous Magento, des projets livrés dans un délai très court, et un support qui nous assiste à toute heure." > "Entreprise sérieuse, service fiable et stable. Le technicien est compétent et capable de répondre à toutes nos questions techniques." NEXT STEP ## Pick the infrastructure layer or the offer that fits. The hosting page details the four resilience tiers (single bare-metal, vertical cloud, advanced vertical, horizontal auto-scaling) and the optional HA module (Galera, Redis Sentinel, multi-DC). The pricing page maps each tier to a profile. [Hosting infrastructure →](/en/hosting) [Plans and offers →](/en/prices) [Talk to an engineer →](/en/contact-us)