Setup & Care

Approved environments. What your server needs.

The hosting we set up and maintain. It stays in your name and you pay your provider directly. Meeting these requirements is what lets your care plan include server maintenance; anywhere else, care covers the application only.

The rule

A deployment never slows down checkout.

Building and deploying Shopware is heavy work for a server. Every layout below is arranged so that work never competes with the live shop.

Layouts

Two layouts, and a third when you need it.

Recommended starting specs from our sizing so far. We confirm the size for your store before setup, based on your catalogue, traffic and integrations.

01

Starter: one server

Shopware, its database, cache and the deployment tooling share one server. Builds run one at a time with limits on their CPU and memory, and deployments are scheduled outside peak trading hours. For single-brand shops with lower traffic and tighter budgets.

Recommended starting spec

One server: shop, database, cache and deployment tooling
8 vCPU · 16 GB RAM · 160 GB NVMe

02

Standard: two servers (recommended)

One server runs the deployment tooling, the other runs the shop. Builds never touch the live store, the shop keeps running if the tooling fails, and the shop server can be resized on its own. The tooling server can host staging later.

Recommended starting spec

Tooling server: deployment, and later staging
4 vCPU · 8 GB RAM · 80 GB NVMe
Shop server: Shopware, database, cache and search
4 vCPU · 12 GB RAM · 160 GB NVMe

03

Scale: defined per store

A separate database, several application servers behind a load balancer, search on its own server and object storage for media. Specified with you when traffic, catalogue size or availability needs justify it.

Requirements

What every environment needs.

Account and access

  • A hosting account in your name, paid by you directly to the provider.
  • KommandHub added as a technical user, with SSH key access and admin access to the deployment dashboard.
  • A virtual or dedicated server with root access. Shared hosting is not approved.
  • A supported Linux distribution, such as a current Ubuntu LTS release.

Backups

  • Automated database and media backups stored off the server, in object storage or a separate storage box — never on the same disk.
  • Restores tested at setup, and regularly under a care plan.

Shopware in production

  • Shopware running in production mode.
  • Background workers and scheduled tasks running as system services, not through the administration.
  • HTTP cache switched on, with Redis for cache, sessions and locks where it applies.
  • HTTPS everywhere.

Elsewhere

Not on an approved environment?

We can still help. Setup on anything else is declined or quoted as best effort, and your care plan covers the application — Shopware, plugins and code — not the server underneath.

Check your hosting.

Tell us where your store runs, or will run. We will tell you whether it qualifies, and what it would take if it does not.