Hosting PrestaShop.
Sklep instaluje się sam, Ty dodajesz produkty.

1. PrestaShop is in a different league than WordPress, so it needs different hosting.

PrestaShop is a standalone e-commerce platform, not a CMS plugin, and requires more resources right from the start than a basic WordPress site. On Saplo, installation uses the official prestashop/prestashop Docker image (PHP and Apache in a single container), with automatic configuration on first startup and no need to complete a multi-step installer manually.

The app manifest in the Saplo catalog requires at least 1 GB of RAM and 5 GB of disk space for the PrestaShop installation alone. In practice, a sensible starting point is Box M (2 GB RAM), not Box S, where 1 GB of RAM would have to run the operating system, database, and store itself with no headroom.

During installation, you can choose the store's language (Polish or English). The MySQL database is shared with the Box infrastructure, so you do not need to run a separate database container for a single store, which leaves more RAM for the application itself.

2. PrestaShop resources: How much RAM to start with

Box M ($69/year, 2 GB RAM, 30 GB SSD, full SSH access with sudo) is a practical minimum for PrestaShop because the application container with Apache and PHP needs significantly more memory than WordPress under similar traffic. You also need additional capacity for caching and customer cart sessions.

Box L ($149/year, 6 GB RAM, 60 GB SSD) makes sense for a store with a broader product catalog, high-resolution images, and real traffic from ads. With many concurrent sessions, PrestaShop uses RAM much more heavily than a static site or a simple blog.

The Box L backup (7-day retention) means more for PrestaShop than for a simple brochure site. The product catalog, stock levels, and order history change every day, so without an up-to-date copy, a failure means actual loss of transactional data, not just site content.

Full SSH access with sudo from Box M lets you run Symfony Console commands (bin/console). PrestaShop 9 requires these for some administrative tasks and module updates, something you cannot do from the store's admin panel alone.

3. PrestaShop hosting in the Polish market

Competitor A promotes its investment in purpose-built servers for WordPress and PrestaShop (provider press release, 2026-10-10). This shows that Polish providers treat PrestaShop as a separate category with different resource requirements from standard shared hosting for brochure sites.

Another provider lists PrestaShop hosting as a separate product line alongside WordPress and Magento, but has not published a clear price list with specific figures as of the review date (2026-10-10). A numerical comparison is therefore not possible without making up data.

Some competitors do not offer a dedicated PrestaShop plan, only general shared hosting or VPS packages where customers have to install and configure PrestaShop themselves. For anyone without server administration experience, this is a genuine barrier to entry.

The difference with Saplo is that PrestaShop is a ready-to-deploy app in the catalog, not something you have to install yourself on a bare VPS. Choose the store language, click Install, and the Saplo engine handles the rest (container, database, domain, SSL).

4. SSL, domains, and transaction security

Every Box gets a free SSL certificate (Let's Encrypt) when you connect a domain. Every payment gateway integrated with PrestaShop requires it, so your store can accept online payments from day one with no extra certificate setup on your side.

The PrestaShop Docker container is isolated from other applications on the Box at the LXC level. A bug in one store module or an outdated PHP version in another app on the same Box will not affect the security or stability of your PrestaShop store.

With no domain limit on the Box, you can connect your main store domain along with separate testing or regional subdomains without buying another hosting package for each one.

5. Who it is for

If you are migrating an existing PrestaShop store from another host, Box M or Box L, depending on the catalog size, gives you a ready-made Docker environment without any manual server configuration from scratch. Migration is free.

If you run an agency that builds PrestaShop stores for clients, a single Box L or Box XL with several store containers (one per client) simplifies billing and administration compared with managing several separate accounts across different providers.

If you are still deciding between PrestaShop and WooCommerce, Saplo lets you test both on the same Box with no extra charge for the second engine, because both are simply separate apps in the catalog.

6. Ordering and your first days with a PrestaShop store

The PrestaShop installation begins with choosing the store language in the setup options. The Docker container launches automatically with a built-in configuration process, so you do not have to work through a multi-step installer manually.

The MySQL database is provisioned automatically from the shared Box infrastructure, so you do not need to run a separate database container for the store. This leaves more RAM for PrestaShop itself.

The initial setup in the store admin panel (company details, payment methods, and shipping options) works the same as it does on any other PrestaShop host because Saplo provides the environment without modifying the application itself.

Migrating an existing PrestaShop store, including its product catalog and customer database, is free. Compared with moving a store from a competitor's bare VPS, this can be a major convenience because you avoid manually exporting and importing the database.

After the first few days, check RAM usage in the Saplo dashboard, especially if you have a larger catalog with high-resolution images. This will help you determine whether Box M is enough or you need to move to Box L.

7. What to avoid when hosting PrestaShop

Avoid installing PrestaShop on a plan with 1 GB of RAM and no headroom for the operating system and cache. The first major traffic spike will noticeably slow down both the admin panel and the storefront.

Avoid assuming that PrestaShop requires the same resources as WordPress. It is a fully standalone e-commerce platform with greater RAM requirements even during installation, as the app manifest shows.

No SSH access when a store requires Symfony Console commands (bin/console) for some administrative tasks, limiting management to the web panel.

Skipping backups for a store with a product catalog and order history that change daily, assuming you can easily recreate the data without a current copy.

Choosing a provider without a ready-made PrestaShop installation requires you to set up the Docker container, database, and reverse proxy from scratch on a bare VPS instead of using one-click installation from the catalog.

8. PrestaShop updates and ongoing maintenance

PrestaShop, like any actively developed e-commerce platform, regularly releases security updates and new features. Delaying updates increases the risk of automated attacks exploiting known vulnerabilities in older versions of the engine or its modules that have already been fixed.

On Saplo, you can update the PrestaShop Docker image using the update recipe in the app catalog. You do not need to manually track new prestashop/prestashop releases on Docker Hub or rebuild the container from scratch for every update.

Before a major update, such as upgrading to a new major PrestaShop version, use a Box backup (available from Box L) as a rollback point in case the update causes compatibility issues with installed modules or a custom store theme.

Third-party modules for payments, shipping, and marketing are often the main source of problems after an engine update because their developers do not always keep up with PrestaShop releases. Check the compatibility of key modules before, not after, a major version update.

For a store with a large product catalog and many installed modules, a regular, scheduled update window, such as once a quarter outside your peak traffic season, is safer than waiting until the old version creates real security problems.

A staging environment (available from Box XL) lets you test an update on a copy of the store before deploying it to production. For a store handling real orders, this is safer than updating a live production installation directly.

9. Documentation and technical support for PrestaShop stores

As a standalone e-commerce platform, PrestaShop can be more technically demanding than WordPress with WooCommerce. Clear documentation of the server environment, including the Docker image version, database configuration, and Symfony Console access, therefore matters when you deploy it for the first time.

The Saplo panel guides you through the basic installation options, such as the store language. You can then configure the rest in the PrestaShop admin panel using the platform's standard documentation, which is publicly available for the specific version of the store engine you are using.

Saplo support covers the infrastructure side, including container uptime, SSL, backups, RAM, and SSD resources. Configuring the product catalog, payment modules, and store theme remains the responsibility of the store owner or the development team managing the project for the client.

When migrating an existing PrestaShop store from another host, the Saplo team helps with data transfer. This is especially useful for large product catalogs, where manually exporting and importing the database without administrative experience can be time-consuming and error-prone.

For agencies building PrestaShop stores for multiple clients, a clear distinction between infrastructure and application responsibilities helps you agree with the client what the hosting provider handles and what the store developer handles. This reduces misunderstandings if a problem occurs on the platform side.

10. Planning your hosting budget for a PrestaShop store in the first year

When planning the first-year budget for a PrestaShop store, include the cost of a Box with enough headroom for traffic growth rather than the smallest plan that will work at launch. Moving between plans does not require transferring data, but it still causes brief administrative downtime while the configuration changes.

The total first-year hosting cost on Saplo is known upfront and does not change after the promotional period, making budget planning easier than with providers that offer a discounted first year and only reveal the regular price upon renewal after 12 months.

If you plan to expand your product catalog in the coming months, include the option of upgrading to a higher plan or adding resources through the hot-add add-on in your budget. Do not assume your initial Box choice will be enough for the store's entire first year.

11. Summary: choosing PrestaShop hosting

Choosing hosting for a PrestaShop store comes down to three questions: Does the platform provide a ready-made installation instead of a bare system you have to configure yourself? Are the resources (RAM, SSD) sufficient for your planned catalog size and traffic? Is backup included in the price before the store starts processing real customer orders? From Box M, Saplo meets all three needs with full SSH access and a ready-to-use Docker installation. This sets it apart from competitors that require you to deploy PrestaShop manually on a bare VPS.