Supported runtimes
PHP, Node.js, MariaDB or MySQL on versions still receiving security fixes; OpenSearch for Magento and Redis for sessions and cache; time and memory limits that survive catalogue imports with thousands of rows.
Take a Celje web shop selling buggies, cots and car seats through WooCommerce and through listings on Ceneje.si. When turnover dips, the products are rarely to blame. More often a category page needs five seconds on a phone, the comparison feed has been silent since Saturday night, or a plugin was upgraded straight on the live site on Monday and broke the basket. Custom software shows the same pattern, be it a Laravel portal where trade buyers reorder or a separate shopfront pulling products from your store via API. The application code is usually decent; the server under it was never configured with care. What we offer is hosting together with day-to-day operations, shaped for such setups. We tune the server to your platform, keep a staging copy apart from production, and check far more than whether the homepage answers: orders, stock levels, parcel labels and exports into accounting must actually land.
Weak spots differ: WooCommerce gathers plugins, Magento wants memory and a search engine, PrestaShop carries ageing modules, and custom apps suffer from manual uploads. The hosting follows your stack.
PHP, Node.js, MariaDB or MySQL on versions still receiving security fixes; OpenSearch for Magento and Redis for sessions and cache; time and memory limits that survive catalogue imports with thousands of rows.
A copy of the shop where updates, plugins and theme tweaks are tried first. Deploys come from Git, so every change has a history, and rollback takes minutes.
Page caching, OPcache, WebP or AVIF and a CDN. We clock mobile load times for your ten busiest pages before and after the move and keep reporting them monthly.
Ceneje.si feeds, stock sync with Metakocka or Minimax, labels for GLS, DPD or Pošta Slovenije, outgoing invoices. A stuck job alerts us, not your buyers.
Back office only via VPN or listed IPs, self-renewing TLS, bot and attack filtering, current plugins. With Bankart, Monri, Stripe or PayPal plus 3-D Secure in the usual hosted form, card numbers never reach your server.
If dozens of orders arrive each day, the database is copied every few hours and files nightly. One copy goes to another provider and test restores run in an isolated sandbox.
Laravel, Symfony, Node.js or Docker, with secrets kept out of the codebase, queues and schedulers watched and logs in one searchable place. A headless front end reading from Shopify can run here as well.
A mid-sized shop usually migrates in one or two weeks. Files are quick; connectors and scheduled tasks are what take time.
Products and variants, plugins, cron entries, feeds, courier and accounting links, traffic, and a first reading of where pages lose speed.
Live and staging servers, a copy of the shop, and a stress test at peak-day levels that quickly exposes the heaviest plugin.
Last database sync and DNS change in the quietest hours, normally Monday into Tuesday, so weekend sales stay untouched.
Real test orders by card and bank transfer, a parcel label printed, exports and order emails verified, then error logs and timings reviewed every day.
Do not update on the live shop. The typical outage is not a breach or a hardware fault but a well-intended update: a new plugin, a WooCommerce release, a theme someone bumped at nine on a Monday. We put every change through staging, confirm it with a test order and only then release it, with a restore point made moments before. One extra hour of care beats a lost day of sales.
No, those services provide their own hosting. What we can run is anything around them: a headless shopfront, a product configurator or a trade portal talking to the shop API.
Yes, and they should. Developers get Git and staging access, log in with personal SSH keys rather than a shared password, and follow an agreed path to production. Servers and operations are ours; features and design stay theirs.
From your promotions calendar. Before Black Friday, the festive rush, back-to-school or a newsletter to tens of thousands, we add capacity, prime caches and review heavy plugins, then shrink the server again afterwards.
In an EU data centre agreed with you. For your privacy notice we list every third party, such as payment gateway, CDN or mailing platform, with what each processes and where. You will need processing agreements with them, and the legal review is for your lawyer.
The server is paid by you directly to the host. Migration and operations are charged at €50 per hour plus VAT or fall within Start, Business or Premium. Migrations get a fixed quote before any work starts.
Which platform, roughly how many products, and which feeds, couriers and accounting tools are linked? From that we propose a setup and a realistic move date.
Enquiry received
An engineer will write back no later than the following working day. Faults that leave your staff unable to work are always looked at first.
No town by that name here. Check the letters, or settle for the nearest larger place. Our engineers work only over the internet, so Kočevje and Koper get precisely the same treatment.