Joomla and Drupal support: managed hosting, performance, security and updates
Joomla and Drupal kept fast, secure and up to date, with no server-side worries.
Joomla and Drupal are solid CMSes, but they need a server side that's as well looked after as the front end: caching to configure, third-party extensions and modules, an admin area exposed to the world and, on Drupal, a major to face every couple of years. We handle the side that matters - infrastructure, performance, security and updates - so the site stays fast, stable and protected without you having to think about it. A single technical point of contact, documented configurations, readable reports: the site stays yours, always.
Overview
A slow or vulnerable site is rarely down to the template: the problem is almost always a stack left on defaults, caching that's switched off or only half-configured, extensions that haven't been touched in months, a security patch put off. We work on these layers with a simple method: first we measure how the site is set up - response times, slow queries, PHP and extension versions - then we remove the bottlenecks one at a time and secure whatever's left exposed.
We're a systems consultancy, not a hosting company with its own datacentre: we can host the site on a stack we manage ourselves, or work on the server you already have, from a VPS to the cloud. Our scope is the server, the platform and the update and release process; on templates, themes and custom modules we coordinate with whoever develops the site, without stepping on each other's toes. Either way, no black boxes: every change is documented and reversible, access stays yours, and if you ever want to move on to someone else, you can do it without redoing any work. We avoid lock-in with documentation, not with promises.
Typical problems we solve
- Slow site with a high TTFB → we measure where time is being lost and work on caching, PHP-FPM and the database, without touching the template; on Drupal we put Varnish in front of the site and review Page Cache and Dynamic Page Cache.
- 500 error or blank page after an update → we read the logs, isolate the extension, module or PHP conflict responsible and restore the service.
- Admin area under brute-force attack → we restrict access, turn on 2FA and filter bots before they ever reach PHP.
- Compromised site or defacement → we clean the files, close the entry point and bring the site back online from a clean backup.
- Updates put off for fear of breaking everything, a backlog of security advisories → we run them for you on staging, in agreed windows, with testing and a rollback ready.
- A Drupal major put off for years (9→10→11) → we map modules and deprecations on staging, then upgrade with a rollback ready, without improvising on the live site.
- Manual changes made directly in production → we bring the Drupal configuration under Configuration Management and releases onto Git and Composer.
- Site email not sending, or landing in spam → we fix SPF, DKIM and DMARC and route sending through a reliable channel.
- Shared hosting that can't keep up any more → we migrate files, database and DNS to a properly sized stack, with minimal downtime.
- Backups that exist but have never been tested → we move them off the server, encrypt them, and test the restore at regular intervals.
What's included
- Managed, optimised hosting: a stack built for Joomla or Drupal on Debian or Ubuntu, with multi-layer caching and resources sized to real traffic.
- Performance tuning: system and page cache, an object cache with Redis, Varnish in front of Drupal where traffic justifies it, BigPipe, PHP-FPM, OPcache and MySQL/MariaDB tuning, compression and image/asset optimisation to bring the TTFB down.
- Security and hardening: correct file and directory permissions, admin-area protection, 2FA, a WAF, HTTPS everywhere, careful handling of
settings.phpand credentials, file-change monitoring. - Safe updates: core, extensions and contrib modules updated on staging first, tested on key pages and functions, then promoted to production with a rollback ready; on Drupal also major upgrades, prepared on a separate environment with a tested procedure.
- Environment management and deploys: separate development, staging and production; on Drupal, configuration exported through Configuration Management and repeatable releases with Git and Composer, with no manual edits on the live site.
- Verified backups: encrypted copies, stored off the production server and periodically tested on restore - a plan we know how to run, not just describe.
- Migration and troubleshooting: moves between servers or providers with minimal downtime, plus diagnosis of 500 errors, extension conflicts and outbound-mail problems.
- Monitoring and reporting: uptime, resource, log and PHP error checks, alerts that reach us before the problem reaches your users, and a readable report on what we did and why.
Stack and technologies
We work mainly on Debian and Ubuntu; on request we also manage AlmaLinux, Rocky Linux and other distributions. In front of the site we run Nginx with PHP-FPM and OPcache, on the PHP version your Joomla or Drupal release supports, and MariaDB/MySQL configured for real load, not the package defaults. For caching we combine the CMS's own caching with Redis or Memcached as object and session handler, Varnish for HTTP caching where needed, and Cloudflare as CDN and first line of defence against bots.
On Joomla, for backups and hardening we lean on the ecosystem's established tools - such as Akeeba Backup and Admin Tools - where it makes sense, without reinventing anything. On Drupal we use Drush for recurring operations, Composer and Configuration Management for code and configuration; releases go through Git and, where it makes sense, a CI/CD pipeline. On the cloud side our default is Google Cloud, with AWS and DigitalOcean as proven alternatives; Hetzner, OVH and Azure on request. Every component is configured for your site and documented.
Two real-world examples
Joomla. A trade association came to us with a portal holding thousands of articles: pages that took several seconds to open, a backend that was almost unusable, and shared hosting that suspended the site at peak times. We migrated the portal to a properly sized Debian VPS, turned on OPcache and page caching, moved sessions and the object cache to Redis, and reworked the MariaDB configuration, tracking the slowest queries down to a couple of extensions. In a second maintenance window we updated core and extensions on staging and locked the admin area behind 2FA and access filtering. The result: response times reliably under a second, a backend the editorial team could use again, and no suspensions since.
Drupal. A public body with a portal on Drupal 9 nearing end of support: dozens of contrib modules, a handful of custom modules, deploys via FTP and no staging at all. We rebuilt the project under Composer, created a staging environment identical to production, and used Upgrade Status to map deprecations and modules with no compatible version. Once the custom code was fixed together with the agency that maintained it, we repeated the migration to Drupal 10 on staging until we had a reliable procedure. The release happened in an agreed early-morning window, with a verified backup and a rollback plan: the portal stayed reachable and the editorial team was back to publishing by mid-morning. Since then, core and contrib get updated on an ordinary monthly round, with no more emergencies to chase.
Who it's for
- Businesses and professionals with a Joomla or Drupal site that needs to stay fast and reachable, without an in-house sysadmin.
- Public bodies, administrations, schools and associations running content-rich institutional portals, with roles and extensions, that need continuity and security.
- Newsrooms and editorial sites with lots of content and traffic to hold up.
- Agencies and web studios that handle templates, themes and content and want a technical partner for servers, performance, security and deploys.
- Anyone coming from shared hosting who needs a stack that can take traffic spikes and seasonal campaigns in its stride.
- Anyone facing a Drupal major who doesn't want to risk the migration straight on the live site.
How we work
We start with a check of site and server status: CMS and PHP versions, active extensions and modules, cache and database configuration, how deploys happen today, backups and security weak points. From there we set out a plan with clear priorities and a quote, always free and answered within one working day. We bill at a single hourly rate; for ongoing management there is monthly maintenance, at a fixed price, and for work needed from time to time hour packages that never expire. We cover Mon-Fri 09:00-18:00 with P1-P4 triage: our response times are written down, not promised verbally. Every change goes through staging before production and wraps up with documented configurations and a readable report. No lock-in: the site stays yours and verifiable.
Frequently asked questions
My Joomla or Drupal site is slow - can it be sped up?
Yes. On Joomla we work on system cache, an object cache with Redis, PHP-FPM and MySQL/MariaDB tuning, compression and asset optimisation. On Drupal we work on Page Cache and Dynamic Page Cache, put Varnish in front of the site, enable BigPipe where it makes sense and tune PHP-FPM, OPcache and the heaviest queries. Either way the TTFB drops sharply without touching the template.
Do you manage the hosting, or work on what I already have?
Both. We can host the site on an optimised stack that we manage, or take care of performance, security and updates on the server or hosting you're using now.
Do you update Joomla, Drupal and extensions without breaking the site?
We update on a staging environment first, test key pages and functions, then promote to production with a backup ready for rollback. If something's off, we roll back in minutes.
Do you also handle Drupal major upgrades, for example from 9 to 10 or from 10 to 11?
Yes. We check module and theme compatibility with Upgrade Status, prepare the upgrade on a separate environment, fix deprecations and custom code, then release to production with a backup ready and a way back. No blind upgrades on the live site.
How do you keep development, staging and production separate on Drupal?
With distinct environments and configuration exported through Configuration Management: changes go through staging before reaching production, the deploy is repeatable with Git and Composer, and every change stays tracked. No manual edits on the live site.
Can you migrate my site to another server or provider?
Yes: we migrate files, database and configuration with minimal downtime, verifying URLs, SSL certificates, email sending and the admin area before switching traffic over.
Do you take backups, and above all do you verify them?
Yes. We set up regular database and file backups, keep them off the server, and test the restore periodically. A backup that's never been tested isn't a backup: we make sure the restore actually works, before you ever need it for real.
How much does Joomla or Drupal support cost?
There is a single rate for every technology. For ongoing management there is monthly CMS maintenance, from €59/month; for work needed from time to time, hour packages from €58/hour that never expire are the better fit. Quotes are free, with a reply within one working day.
The site's been compromised or is unreachable - how quickly do you step in?
A breached or unreachable production site is a P1 emergency: during office hours we pick it up within one hour (Mon-Fri 09:00-18:00); out of hours within one hour with an on-call plan, otherwise within 24 hours if we already work together. We clean the files, close the entry point and restore from a clean backup.
Do you also work at night or on weekends?
Yes, for emergencies. The on-call plan extends your office hours on the days you choose: we pick up a P1 within one hour at any hour and a P2 within 4 hours during the day, and the work costs the same as in office hours. Without a plan our hours are Mon-Fri 09:00-18:00: out of hours we still pick up a P1 within 24 hours, weekends and public holidays included, at the out-of-hours rate, if we already work together; everything else is best effort. Night or holiday work planned at least 20 days ahead remains available to everyone. Plans, rates and examples are on the On-call page.
Need Joomla and Drupal support?
Tell us what's happening: we reply within one working day with the likely cause and the price.