Skip to main content
by shop owners, for shop owners

Our managed hosting architecture for your Magento / Mage-OS shop!

by shop owners for shop owners.

Our Magento hosting architecture delivers performance, scalability and security — for both small and large Magento / Mage-OS shops, even when traffic skyrockets on Black Friday or during the Christmas rush!

We design, build and operate the hosting architecture for your Magento / Mage-OS online shop!

Magento Hosting Architecture Example 1

Architecture Example 1 is essentially our standard solution and is designed so that it can be quickly expanded with additional VMs or upgraded to Example 2.

INTERNETSECURITYCACHEAPPDATACLOUDDEDICATED SERVERMonitoringBackupVM 1OPNsenseFirewall2 vCPU8 GB RAMVM 2SafeLineProxy · Bot · WAF4 vCPU16 GB RAMVM 3PARC SecurityBlocklists · IP groups · Rules2 vCPU8 GB RAMVM 4VarnishFull-Page Cache2 vCPU8 GB RAMVM 5NginxFrontend4 vCPU8 GB RAMVM 6NginxBackend / CLI / Index4 vCPU8 GB RAMVM 7RabbitMQMessage Queue1 vCPU2 GB RAMVM 8MariaDBDatabase4 vCPU24 GB RAMVM 9OpenSearchProduct Search3 vCPU8 GB RAMVM 10RedisSessions · Cache2 vCPU4 GB RAMINFRASTRUCTUREPrivate Cloud · VPSCPU & RAM RESERVEDVPS 12 vCPU8 GB RAMVPS 24 vCPU16 GB RAMVPS 32 vCPU8 GB RAMDedicated ServerPROXMOX VEVM 42 vCPU8 GB RAMVM 54 vCPU8 GB RAMVM 64 vCPU8 GB RAMVM 71 vCPU2 GB RAMVM 84 vCPU24 GB RAMVM 93 vCPU8 GB RAMVM 102 vCPU4 GB RAM
Internet
Incoming traffic such as genuine customers, search engine bots, security scanners, brute-force attacks, malicious IPs, spam bots and other background noise from the internet. Currently, over 30% of all HTTP requests worldwide are bot traffic — by 2027, bot traffic will overtake human traffic!
Security
This layer keeps unwanted traffic away from the subsequent layers, thereby conserving resources and, above all, ensuring an uninterrupted shopping experience. OPNsense, SafeLine and PARC Security complement one another: the OPNsense firewall blocks traffic at Layer 3/4 (ports, IP ranges, unwanted connections). The SafeLine Web Application Firewall with semantic attack detection filters at Layer 7 (SQL injection, XSS, bot traffic, credential stuffing). The PARC Security module provides OPNsense and SafeLine with up-to-date blacklists and supplies IP groups for both good and malicious bots, on which many WAF rules are based. Interesting to know: Traditional CDN-WAFs such as Cloudflare, Akamai or AWS CloudFront terminate TLS at their edge — the traffic is decrypted there for inspection and is therefore technically visible. SafeLine terminates TLS and decrypts on your own infrastructure!
Cache
Varnish delivers requests directly from the cache (Full-Page Cache, FPC) without the need for the subsequent layers — Nginx, PHP-FPM, database — to be activated. This not only saves resources but also has a significant impact on page delivery speed. Product and category pages, for example, are delivered in a flash.
App
In our architecture, the frontend and backend are separated by default. The customer’s shopping experience is not disrupted by indexers, lengthy cron jobs or large import/export processes. Security is also improved by this separation: the Magento backend (admin interface), for example, is only accessible via VPN or IP restrictions. Furthermore, this separation enables horizontal scaling of the frontend — as traffic grows, multiple frontend nodes are run in parallel, whilst the backend, cron and indexer remain centralised. RabbitMQ distributes asynchronous Magento tasks (bulk attribute updates, image generation, exports, ERP sync) across one or more workers to prevent the server from becoming overloaded — and is what makes clean horizontal front-end scaling possible in the first place.
Data
The main database is MariaDB — deliberately chosen over MySQL because it can be converted directly into a Galera cluster (with ProxySQL as the router) if required. OpenSearch handles product search and can be scaled horizontally in the same way using a coordination node and additional search instances. Redis manages the front-end and back-end sessions.
Infra­structure
For our infrastructure, we generally rely on a mix of cloud and dedicated servers based on Proxmox VE. Each service runs encapsulated in its own VM — optimisation, scaling and updates take place precisely where they are needed. The setup is designed from the outset to allow for expansion with additional cloud or dedicated servers at any time, in order to achieve greater reliability and performance.

Magento Hosting Architecture Example 2

Architecture Example 2 offers even greater reliability and is designed to handle very high traffic volumes.

INTERNETSECURITYCACHEAPPDATALOCATION 1dedizierter ServerCLOUDvirtueller 3. StandortLOCATION 2dedizierter ServerMonitoringBackupVM 1VarnishCache2 vCPU8 GB RAMVM 2NginxFrontend4 vCPU8 GB RAMVM 3NginxBackend · CLI · Index4 vCPU8 GB RAMVM 4RedisMaster2 vCPU4 GB RAMVM 5GaleraNode 1 · Writer4 vCPU24 GB RAMVM 6OpenSearchNode 13 vCPU8 GB RAMVM 7OPNsenseFirewall2 vCPU8 GB RAMVM 8SafeLineProxy · Bot · WAF4 vCPU16 GB RAMVM 9PARC SecurityBlacklists · IP-Gruppen2 vCPU8 GB RAMVM 10Proxy SQLProxySQL2 vCPU8 GB RAMVM 11Proxy RedisHAProxy2 vCPU8 GB RAMVM 12RabbitMQQueue2 vCPU8 GB RAMVM 13OpenSearchCoordination2 vCPU8 GB RAMVM 14GaleraNode 38 vCPU32 GB RAMVM 15OpenSearchNode 38 vCPU32 GB RAMVM 16VarnishCache2 vCPU8 GB RAMVM 17NginxFrontend4 vCPU8 GB RAMVM 18NginxBackend · Admin4 vCPU8 GB RAMVM 19RedisSlave2 vCPU4 GB RAMVM 20GaleraNode 24 vCPU24 GB RAMVM 21OpenSearchNode 23 vCPU8 GB RAMINFRASTRUCTURECloud · VPSCPU & RAM RESERVEDVM 72 vCPU8 GB RAMVM 84 vCPU16 GB RAMVM 92 vCPU8 GB RAMVM 102 vCPU8 GB RAMVM 112 vCPU8 GB RAMVM 122 vCPU8 GB RAMVM 132 vCPU8 GB RAMVM 148 vCPU32 GB RAMVM 158 vCPU32 GB RAMStandort 1 · Dedizierter ServerPROXMOX VEVM 12 vCPU8 GB RAMVM 24 vCPU8 GB RAMVM 34 vCPU8 GB RAMVM 42 vCPU4 GB RAMVM 54 vCPU24 GB RAMVM 63 vCPU8 GB RAMStandort 2 · Dedizierter ServerPROXMOX VEVM 162 vCPU8 GB RAMVM 174 vCPU8 GB RAMVM 184 vCPU8 GB RAMVM 192 vCPU4 GB RAMVM 204 vCPU24 GB RAMVM 213 vCPU8 GB RAM
Security
The SafeLine WAF has one upstream server per site. If a site goes down, the WAF automatically switches to the remaining Varnish server.
App
Magento Open Source and Mage-OS can only access one DB, one Redis or one OpenSearch server—load balancing and failover are not built-in. Therefore, ProxySQL (DB), HAProxy (Redis) and the OpenSearch Coordinator (search) handle the routing. One Nginx frontend per site — for greater load capacity and reliability. The backend admin panel and backend CLI/index are distributed across individual sites.
Data
The Galera cluster replicates the database synchronously across both sites and the cloud. OpenSearch runs similarly as a 3-node cluster. Redis is present at every site.
Infra­structure
Two dedicated servers instead of one — distributed across two sites. The cloud layer is extended with routing and quorum VMs.

How we implement the Magento / Mage-OS Hosting Architecture.

What we actually do — honest, no buzzwords.

1. Concept

1. Concept

We analyse what your shop needs and design the right architecture. Size, components, scalability, multi-country — everything individually configured from our architecture toolkit.

2. Infrastructure

2. Infrastructure

The architecture requires matching infrastructure — this can be a virtualised dedicated server or cloud VPS distributed across multiple sites. Hardware maintenance and replacement is handled by the provider you contract with directly.

3. Setup

3. Setup

We prepare the infrastructure — for example, through a Proxmox installation or the provisioning of individual cloud servers — and tailor the prefabricated architecture components to your Magento shop. Monitoring included.

4. Migration

4. Migration

We migrate your existing shop cleanly onto the new architecture. DB takeover, configuration adjustments, an upstream test phase and minimal downtime are a given.

5. Operation & Maintenance

5. Operation & Maintenance

Following a successful migration, every infrastructure and architecture requires maintenance, updates and optimisations. Billed according to time and requirement.

Options

Options

On-call availability outside office hours, dev environment including CI/CD pipelines, and much more.

How much.

Below, we’ve outlined the costs for the most commonly used architectures. Specific figures depend on size, complexity and the desired setup, and may vary according to requirements.

Architecture Example 1

Hosting (monthly)
approx. €220

Example configuration at Hetzner:
1× EX63 (192 GB RAM), 2× CCX13, 1× CCX23, Cloud Backup, BX11, as of 15.05.2026

One-off (flat rate)

Provisioning and alignment of the architecture with the infrastructure

€1,999
Additional, based on time
  • Initial configuration
    Firewall/WAF, Domains, SFTP, Migration, …
    approx. 8 hrs, one-off
  • Maintenance / Update
    OS, OPNsense, WAF
    approx. 1 hr per month
€100 / hr

Architecture Example 2

Hosting (monthly)
approx. €585

Example configuration at Hetzner:
2× EX63 (192 GB RAM), 6× CCX13, 1× CCX23, 2× CCX33, Cloud Backup, 2× BX11, as of 15.05.2026

One-off (flat rate)

Provisioning and alignment of the architecture with the infrastructure

€3,999
Additional, based on time
  • Initial configuration
    Firewall/WAF, Domains, SFTP, Migration, …
    approx. 8 hrs, one-off
  • Maintenance / Update
    OS, OPNsense, WAF
    approx. 2 hrs per month
€100 / hr

Optional

Monitoring including on-call (monthly)

Provision of monitoring including availability outside business hours, at weekends and on public holidays. Learn more.

€300

Additional effort billed on an hourly basis.

Magento Updates & Support

Magento maintenance, updates, security patches, performance optimisations, security audits, GDPR matters, etc. Learn more.

based on time

€100 / hr
Magento development for front-end and back-end

Bespoke customisations, modules / extensions / add-ons. Learn more.

based on time

€100 / hr

All prices net, plus VAT.

Who we are.

Do you know that feeling of being left in the lurch by your hosting provider when things get critical — only to be met with a string of excuses afterwards?

We know it all too well! We’ve been running several large Magento shops ourselves for over 16 years, and during that time we’ve heard plenty of fine promises from hosting providers — and, thank goodness, seen them vanish into thin air often enough. Yes, thank goodness: that was exactly the impetus we needed to get seriously to grips with Magento, architecture and hosting.

PARC Network — Polar bear

That’s exactly what the polar bear in our logo stands for: alone in a harsh environment — and yet you still make it through. We are polar bears!

It’s been a long journey. But at some point we realised: all we really need is a hosting provider that supplies decent hardware. Going to the data centre isn’t Louis’s thing. Luisa prefers Magento to Shopware. And Paul likes hardware. And people. But that’s beside the point here.

We’re a small team. PARC Network stands for Process and Research Centre — and that’s exactly what we do: thinking through processes, researching architectures, sharing what works. PARC Network is our second main focus alongside the Magento shops we run ourselves. That’s exactly why we don’t want just any customer — we want partners on an equal footing. The sort from whom we can also learn, even beyond Magento hosting.

We want to run your Magento, install updates and see what tricks you’ve got up your sleeve. A lively exchange is important to us.

Luisa Luisa
Louis Louis
Paul Paul

Our 10 Commandments.

So that no one has any false expectations.

  • No Shopware, no WordPress, no Joomla & Co. — Magento 2 / Mage-OS is our speciality. But if you’d like to switch or migrate from another shop system (e.g. Shopware, WooCommerce, OXID, JTL) to Magento 2 / Mage-OS, we’d be interested to hear from you.
  • No Magento Commerce / Adobe Commerce licensing. We work with Magento Open Source and Mage-OS — the community fork that continues to develop Magento independently of Adobe. No licence lock-in. But if you’d like to switch or migrate from Adobe Commerce to Magento Open Source, we’d love to hear from you.
  • No Magento on AWS, Azure or Google Cloud. We rely on European providers and dedicated infrastructure — for GDPR sovereignty, the Cloud Act and to avoid vendor lock-in.
  • No SLA promises, no response time guarantees. No one can monitor or enforce this 100% impartially — you can spend days comparing providers and doing research, only to find in the end that most issues are either covered by force majeure, scheduled maintenance, or not covered at all. And in the event of a loss? At best, a credit against a monthly fee; at worst, a few pence — neither ever covers the actual business loss. So we don’t promise it, but we do it as quickly as we possibly can.
  • No 24/7 hotline for hardware emergencies. That’s the hosting provider’s responsibility — and good hosting providers don’t need us for that.
  • No list prices, no S/M/L/XL packages, no clicking up or down on cores, RAM or storage in a configurator. We scale the architecture to suit your shop — with reserves. Even a TV advert at 8.15 pm is no problem.
  • No sales team, no marketing budget. If you’re happy with us, we’d love a recommendation.
  • No “Hyvä Hosting” — there’s no such thing. Hyvä is a front-end theme, not a hosting stack. We know our way around Hyvä, by the way — and you can use it anywhere anyway, not just with us.
  • No AI marketing. Yes, we use AI in our work — but we don’t integrate proprietary “super-AI” cloud services into your architecture just to make the pitch sound modern.
  • No ISO certificates, no wall of logos with client testimonials, no “Trusted Partner” seals. We’re not award hunters. We too have master’s degrees, bachelor’s degrees and other qualifications — but above all, we have over 16 years’ experience in Magento. Just have a chat with us and see for yourself.

Get in touch — we don’t bite :)

Würzburg dialling code — where the good wine grows :)