
Upgrading a retailer to Magento 2.4.8, and why checkout broke
Two major versions behind, a ten-megabyte home page, then checkout died. How we brought a specialist retailer's Magento current and what we found underneath.
Read →We don't just build the platform and hand you the keys. We run it — on tuned Linux servers built for high-traffic stores and newsrooms. One team, one point of contact.
Tuned Linux servers — nginx, PHP-FPM, MariaDB — built for high-traffic stores and newsrooms, not shared-hosting defaults.
Domain registration and management, DNS and certificates — set up and kept current.
Cloudflare, caching and edge tuning that keep the site fast and up under load.
Ongoing server administration, patching and monitoring. We watch it so you don't have to.
When the people who built the platform also run the servers under it, problems get fixed instead of forwarded. We tune nginx, PHP-FPM and MariaDB for the actual load, sort the domains, DNS and certificates, put Cloudflare and caching in front, and watch it — patching and monitoring so issues surface before your customers find them.
Build it, host it, run it. One number to call.
Move your platform to usManaged hosting at Chronon is not a reseller control panel. Every site runs in its own PHP pool with its own filesystem view, on nginx and MariaDB we configure by hand for that site's traffic pattern. A WooCommerce store, a Magento B2B portal and a newsroom do not want the same settings, so they do not get them.
Patching is scheduled, not hoped for. Core, plugins, PHP and the operating system are updated on a cycle, with a staging copy for anything that can break a checkout. Backups run nightly to a second host and monthly to a third location outside the data centre, and we test restores.
Security is baked in: rate limits on login and API endpoints, blocked PHP execution in upload directories, integrity checks on checkout assets, fail2ban and a firewall at the edge. When something does go wrong we have the forensics and the playbook, because we have done it before.
Domains, DNS, certificates and email routing live under the same roof, so there is one number to call when anything from a renewal to an outage needs a human.
In South African data centres for sites with a local audience, with Cloudflare in front where it helps, and in European locations where latency or compliance calls for it. We can also manage servers you already own.
All three, each on a stack tuned for it. We run high-traffic newsrooms, WooCommerce stores with subscriptions and Magento 2 stores with ERP integration on our infrastructure today.
Server, monitoring, patch cycle, nightly and off-site backups, certificate renewals, DNS and a response when something breaks. Development work is quoted separately so hosting stays predictable.
Monitoring alerts us, not you. Most incidents are handled before anyone notices. For the rest, you get a plain-language account of what happened and what we changed so it does not happen again.
Yes. Migrations are done on a staging copy first, with DNS switched only once we have clicked through the live flows. Downtime is usually zero.

Two major versions behind, a ten-megabyte home page, then checkout died. How we brought a specialist retailer's Magento current and what we found underneath.
Read →
Page views down ninety percent in a week. The site had not lost an audience. It had lost a counting error. Here is what was actually…
Read →
An unpatched extension, a fake system daemon, a backdoor and a checkout skimmer. How a high-traffic store was compromised and how we took it back.
Read →