Service · Cloud and hosting

Hosting for Bitrix24 and web shops

A shop copes perfectly well on a shared plan until the first genuine traffic peak. After that the symptoms always arrive in the same order. The product page takes four seconds to draw. The feed pushing the catalogue to the marketplaces stops halfway through without telling anybody. And on Black Friday visitors meet a 503 error where the basket should be. Bitrix24 installed on your own server tells the same story: on an undersized machine, the whole sales department waits. We build the environment so that those days pass without needing you.

Caching
tuned to your page and product volumes
Feeds
an alert the moment a sync stalls
Database
copied several times a day
EU
customer data held inside the Union

Where this service reaches

PrestaShop, WooCommerce, Magento and Bitrix24 all publish precise requirements. We build to those requirements from the start, instead of patching things up once the first round of complaints arrives.

Put your scope to an engineer

Versions and settings

PHP, database and web server on releases the vendor still supports, with memory limits and execution times set against your catalogue imports rather than left at the defaults.

Self-hosted Bitrix24

A machine that meets the vendor requirements, copies of both database and files, and updates applied only after a trial run on a clone. The CRM and intranet then run on your server, in the region you picked.

Response times

Full page caching, OPcache, Redis holding sessions and objects, images delivered through a CDN and converted to a modern format. The product page appears quickly, including on a phone away from wifi.

Feeds and scheduled jobs

Catalogue sent to Amazon.fr, Cdiscount or Rakuten through Lengow or Shoppingfeed, labels for Colissimo, Chronopost or Mondial Relay, orders passed back to Sage or Pennylane. An alert fires as soon as a job fails to finish.

Shop security

Admin reachable only from known addresses or over a VPN, TLS certificates renewed automatically, common attacks filtered, plugins and themes kept current. Card data stays with Stripe, PayPlug or your acquirer and never touches the server.

Backups

The database every few hours, files once a day, at least one copy away from the server, and a regular trial restore into a test environment.

The way an engagement runs

How long it takes depends on catalogue size and on how many feeds have to be rebuilt. A full rehearsal always precedes the real move.

01

Measuring

Visits, products and variants, database weight, portal users and sync frequency together give the starting specification.

02

Build and load test

The environment goes up, a clone of the shop is deployed on it, and we simulate the traffic of a promotion day. Expensive plugins reveal themselves there, not in front of real customers.

03

Moving day

Files, database, domain name and certificate cross during the quiet hours, usually the night from Sunday into Monday.

04

Checks after go-live

We walk the checkout again, put through a real payment of a few euros, print a label, exercise the feeds and the admin, then watch response times over the following days.

Black Friday is prepared the week before, not on the Friday morning. Resizing the plan takes minutes, yet the cache still has to fill, and only real traffic makes a load test reveal the expensive plugins. So we ask for your commercial calendar, sales periods and year-end campaigns included, raise the resources ahead of time, and bring them back down to the everyday size once the period is over, so the peak is not paid for all year round.

Questions and answers

No, and there is no need: those are subscription platforms, and their vendor runs the servers. Our hosting is for platforms you install yourself, meaning PrestaShop, WooCommerce, Magento, Sylius and self-hosted Bitrix24. On a subscription shop we can still take on integrations, the domain name and the feeds going out to marketplaces.

The cloud edition suits most companies and asks nothing of you operationally. Hardware of your own earns its place when you want to control the hosting region, keep changes made to the code, or connect the portal to internal systems that never leave your network. We compare the two against your user count before deciding.

Nine times in ten, power is not the culprit. A plugin issuing two hundred queries per page, a cache switched off during some intervention and never switched back on, a scheduled job that rebuilds the entire catalogue once a minute. Profiling names the culprit within hours and saves you paying for a bigger machine that would change nothing.

Every few hours once orders arrive during the day. Losing an afternoon means paid orders you have no record of, tracking numbers sent to customers and untraceable at your end, and refunds to work out blind. Images and documents move far less: a daily copy is ample for them.

It stays online. The new environment is built alongside the old one, the database is synchronised one last time overnight, and then the domain name switches. Order taking pauses for a few minutes at most, and the old hosting stays live for several days in case a step back is needed.

Ready the shop for traffic peaks

Tell us the platform, the number of products, monthly traffic and the feeds you run. We propose a specification and a timetable for the move.

When we are around
Weekdays, 8:00 to 18:00 CET; answers land inside one working day
Talking it through
A call on Teams or Google Meet, whenever writing is not enough

We set strictly necessary cookies only: they keep the site running and remember the city you chose. Nothing here is used for advertising or tracking. More in our privacy policy.