Hosting provides the infrastructure your website runs on: server, storage, network and their operation. Maintenance, by contrast, looks after the application itself – updates for the shop system or CMS, security patches, plugin care and functional testing. A professionally operated website usually needs both, as each layer covers its own risks.
Hosting and maintenance are often mentioned in the same breath, but they refer to two different layers. Hosting covers the technical foundation: a server with computing power, storage and network connectivity, plus the operating system and server services such as the web server, database and PHP. It answers the question of where and how reliably your website runs – including availability, server-level backups and infrastructure protection.
Maintenance operates one layer up: at the application running on the server. Shop systems like Shopware and CMS platforms like WordPress receive a continuous stream of new releases – security patches, bug fixes and feature updates. These need to be applied, checked for compatibility with plugins and the theme, and then tested. That is exactly what maintenance agreements such as our Shopware maintenance or WordPress maintenance cover.
Tasks compared
- Hosting: server operations, operating system updates, availability monitoring, SSL certificates, server backups, infrastructure performance
- Maintenance: shop system/CMS updates, plugin and theme care, application security patches, functional testing after updates, troubleshooting
- Both together: security, stability and currency of the entire system – with each layer covering its own area
The distinction is more than semantics, because it concerns responsibilities: a managed hosting package typically keeps the server up to date – but not the shop or CMS running on it. Anyone who assumes that good hosting automatically means a well-maintained application leaves a critical gap open. In our experience, outdated shop and CMS installations with unmaintained plugins are among the most common entry points for attacks – regardless of how well the server itself is secured.
A practical example illustrates the division of labour: if monitoring reports a server outage, that is a hosting matter – the operator checks hardware, services and network. If, on the other hand, an error message appears in the checkout after a plugin update, maintenance is needed: it analyses the application, restores a backup if necessary and resolves the incompatibility. Without clearly defined responsibilities, valuable time is lost at exactly this interface in an emergency, because neither side feels responsible when in doubt.
Maintenance also includes looking ahead: monitoring vendor security advisories, checking compatibility with upcoming releases and identifying legacy issues such as abandoned plugins before they become a risk. This forward-looking care distinguishes a maintenance agreement from pure firefighting that only kicks in once something breaks.
Why a single provider for both pays off
In practice, bundling hosting and maintenance with the same service provider has proven effective. If a problem occurs, there is no debate about whether the cause lies with the server or the application – one partner is responsible for both and can align server configuration and application with each other. This also pays off in terms of performance: PHP settings, database tuning and caching work best when they match the specific shop or CMS installation.
When choosing a maintenance agreement, it is worth examining the scope of services: does it include only security updates or feature updates as well? Are updates tested on a staging environment before being applied? What response times apply in the event of an incident? The answers vary considerably between providers and packages – and determine how well your system is positioned when it matters.
Not sure which combination of hosting and maintenance suits your project? In a free initial consultation we analyse your current setup and show you sensible options.