Magento hosting in the Netherlands

Magento is not a website with a basket.

A Magento shop runs on seven parts that have to fit together. Standard web hosting has only a few of them, and you notice it in load times and at checkout.

We set up the whole stack for your shop, on hardware we own and know. When something falls over, we find out where: in the server, in Magento or in a module.

What runs.

Varnish The page cache: Keeps ready-made pages. A visitor opening a category or product usually gets it from Varnish, without PHP or the database doing any work.
Nginx and PHP-FPM Web server and Magento itself: Everything that cannot come from the cache: the basket, the account, the checkout. We match the number of PHP processes to your shop, with OPcache on.
OpenSearch Search and the catalogue: Magento 2.4 needs a search engine for the search bar and the filters in categories. Ours runs next to the shop, on the same hardware.
Valkey Cache and sessions: Holds Magento’s internal cache and visitor sessions in memory. Valkey is an open source fork of Redis and works with Magento 2.4.
RabbitMQ Queues: For work that does not have to happen right away: bulk actions in the admin, exports, and messages to and from integrations. If something fails, the message is kept.
MySQL The database: Products, customers, orders. We watch the tables that grow on their own in Magento and clean them up before they slow the shop down.
Cron The work in the background: Indexers, emails, sitemaps, price rules. When cron stops, you only notice through odd stock levels or emails that never arrive. We measure whether it runs.

What comes as standard

Staging

A copy of your shop to test updates and new modules on. Without real customer data in it, if you prefer.

Backups

Database and media to separate storage, kept for a period we agree. We test restoring them too.

Updates and patches

The operating system, PHP, the databases and Magento’s security patches. Staging first, then live.

Protection against bots

Search and login pages are heavy in Magento. We limit bots that hit them in bulk, so a scraper does not slow your shop down for real customers.

Deploys with as little maintenance mode as possible

A new version is built next to the running shop. We only switch over when everything is ready. Only a database change still needs a short maintenance moment.

Public status

Every minute we measure whether our services can be reached, from a server outside our own network. What goes wrong is on the status page.

See the status

For web agencies.

You build Magento shops, we host them. Client contact stays with you; we are the party behind the scenes that handles the servers, the updates and the outages.

A staging environment per shop and access for your developers. Moving a complete hosting portfolio works too, one shop at a time, with a trial move for each shop.

How switching works

Questions

Where does our Magento shop live when you host it?

On hardware we own, in a data centre in Hengelo. Your customer data and orders stay in the Netherlands, on machines we manage ourselves. We know exactly which machine your shop runs on, and exactly who has access to it.

Which Magento versions do you host?

Magento 2.4, both Magento Open Source and Adobe Commerce. For Adobe Commerce you arrange the licence with Adobe; we host the software. If your shop runs an older 2.x version, we plan the upgrade first, because older versions no longer get security updates.

Can your hosting handle busy days such as Black Friday?

We prepare for them together. Beforehand we look at last year’s traffic and the promotions you have planned, and make a plan with you. Varnish takes most of the visitors, so the server mainly has to cope with the baskets and the checkout.

How does moving from our current host work?

With a trial move. We set up a copy of your shop with us and test it with you, while the old environment keeps running. At an agreed moment we sync the latest orders, switch the DNS and keep the old environment for a while as a safety net.

Do our developers get access to the server?

Yes. Your developer or agency gets SSH access with their own key, and a staging environment to test on. We prepare new versions next to the running shop and only switch over once everything is built. That keeps the shop available during a deploy as much as possible.

What happens if the shop goes down at night?

As standard we are available on working days from 09:00 to 17:00, and the measurement on the status page runs every minute. If you want someone to step in outside office hours, you agree on-call as a paid extra. What that covers is then written down in the contract.

From the knowledge base

More about Magento

Tell us what you run.

An introduction costs nothing. You talk straight away to one of the two people who will actually do the work.

Get in touch

or email [email protected]

Magento hosting, on our own hardware.