VPS Hosting for CMS Shopware on SSD

Shopware is an online-store platform on PHP and Symfony, built for catalogues with many options and several sales channels. With VPS hosting for Shopware from HIP-HOSTING the shop lives on a virtual server of its own, so background jobs and the search index are not squeezed by the limits of shared plans. A preinstalled Shopware is not on the order form: pick a clean Ubuntu, add PHP and a database, and install the shop with Composer. Plan the size by the catalogue and the flow of orders, and scale it from the panel when sales grow.

Get VPS from $3/mo
12 locationsFull root access
VPS for Shopware
  • Standardfrom $3/mo
  • Memoryfrom $10/mo
  • Hi-CPUfrom $5/mo

VPS / VDS PLANS

Our VPS hosting plans for CMS Shopware

Choose a location and plan line. Prices shown per month.

Tokyo, JapanAvailable

1 vCPU1 GB RAM

  • 10 GB SSD
  • 200 Mbps

$3/ mo

Order VPS

2 vCPU2 GB RAM

  • 20 GB SSD
  • 200 Mbps

$4/ mo

Order VPS

2 vCPU4 GB RAM

  • 40 GB SSD
  • 200 Mbps

$6/ mo

Order VPS

4 vCPU8 GB RAM

  • 80 GB SSD
  • 200 Mbps

$12/ mo

Order VPS

6 vCPU12 GB RAM

  • 120 GB SSD
  • 200 Mbps

$18/ mo

Order VPS

8 vCPU16 GB RAM

  • 160 GB SSD
  • 200 Mbps

$24/ mo

Order VPS

8 vCPU24 GB RAM

  • 240 GB SSD
  • 200 Mbps

$32/ mo

Order VPS

8 vCPU32 GB RAM

  • 320 GB SSD
  • 200 Mbps

$48/ mo

Order VPS

12 vCPU48 GB RAM

  • 400 GB SSD
  • 200 Mbps

$64/ mo

Order VPS

16 vCPU64 GB RAM

  • 500 GB SSD
  • 200 Mbps

$96/ mo

Order VPS

FAQ

Frequently asked questions

Yes, and the NVMe plans are the Hi-CPU ones, which the form offers in Paris, Dronten and Helsinki. Indexing and importing a large catalogue is where they show themselves: the shop reads and writes thousands of records at once. A store with a few hundred items does well on the SSD plans, Standard or Memory, available in all open locations.

IN DETAIL

Service description

The stack for the shop

Shopware runs on nginx and PHP-FPM, with MySQL or MariaDB as the database. Caching and sessions are better kept in Redis, and search in a separate engine once the catalogue is large. The document root of the site points at the public folder, not at the project root: otherwise the configuration files become reachable from outside.

Installation and settings

The project is created with Composer, and the first launch is done by the installation command of the console. In the environment file you set the site address, the production mode and the database connection. Keep that file out of the repository. After the installation, create an administrator and change the standard password at once.

Queue and scheduled tasks

Letters, indexing, price updates and cleaning work through the queue. Run the worker under systemd, which brings it back after a reboot, and add a regular launch of scheduled tasks. Look at the length of the queue now and then: if it only grows, the shop is short of memory or the worker has stopped.

Themes, plugins and cache

After a change in a theme or a plugin, rebuild the theme and clear the cache with the console commands, or visitors will see the old design. Install plugins one by one and watch the speed: a heavy extension can slow the whole storefront. Do not edit the files of the core, keep your changes in a plugin.

Copies and updates

A shop consists of the database, the folder with uploaded pictures and the project with its settings. Take the three together and keep them off the server. Update with Composer and finish with the console command. Extensions often lag behind the core, so first test the new release on a separate copy. Before a big sale, check the backup by unpacking it.

Speed and memory

Shopware gains much from the opcode cache of PHP and the cache of ready pages. Give PHP enough memory and keep the swap file as insurance only. An NVMe VPS server with Shopware speeds up indexing and import of a large catalogue, and the storefront opens faster at the peak of orders.

Mail and payments

Order confirmations leave through SMTP. Since fresh servers may close mail ports, hand the sending over to an external service, not to software on this machine. Payment modules need a working HTTPS address, or the notices about payment will never return. Place a test order from start to finish before opening the shop to customers.

Logs and the disk

The shop writes logs and cache to files, and they grow faster than expected on a busy site. Set the log rotation, clean old sessions and look at the free space each month. Pictures and the database deserve a disk with a margin, since it can be enlarged but never reduced. A full disk stops the shop at the worst moment, and orders are lost with it.

Who it suits

  • an online shop with a wide assortment and many product options;
  • a seller who runs several sales channels from one admin area;
  • a studio that delivers Shopware shops to clients;
  • a team that uses the shop as a back end for its own storefront.

Choosing a plan

Count the products, the pictures and the orders on a busy day before you buy Shopware VPS hosting. Those who rent Shopware VDS hosting take on updates, copies and the queue, and get the version and the extensions of their choice in return. The first VPS/VDS for Shopware can be modest, say two cores and 4 GB: watch memory during the first sale and expand from the panel. Cheap Shopware VPS hosting is a server where the queue does not stall at the peak, not simply the lowest price.