Skip to content

Drupal support and maintenance that keeps your site patched, backed up and watched.

Monthly Drupal support and maintenance for organizations running Drupal 10 or 11, or still on Drupal 7. We apply security updates, test backups by restoring them, monitor uptime and work through your fixes and improvements on a monthly hours plan, with response times written into the contract.

  • Drupal 10 + 11
  • Drupal 7 bridge
  • Security advisories
  • Staging-first updates
Example dashboard for a placeholder site. Drupal security releases normally come out on Wednesdays; every update goes to staging first.
A phone lighting up with an alert notification on a bedside table at night
3:12 AMA security advisory came out yesterday. Someone needs to apply it before the site becomes a target.

Why Drupal sites fall behind on maintenance.

Four ways an unmaintained Drupal site turns into an emergency. Each one is preventable.

  1. 01

    Security updates that wait

    Drupal's security team publishes advisories for core and contributed modules, usually on Wednesdays, and some are rated highly critical. In 2014 the team advised that Drupal 7 sites not patched within seven hours of one core advisory should be treated as compromised. Updates saved for a quiet month are a risk.

  2. 02

    Composer updates that keep failing

    A module pins an old dependency, a patch no longer applies, or the next core release needs a newer PHP version. So the update gets postponed, and the site drifts off the supported release. Drupal only provides security fixes for its most recent minor versions.

  3. 03

    Backups nobody has restored

    Most hosts take backups. Far fewer teams ever restore one. A database dump without the files directory, a missing private files folder or a corrupt archive only shows up on the day you need it, which is the worst day to find out.

  4. 04

    No one to call when it breaks

    The developer who built the site has moved on, small fixes wait in someone's inbox, and when the site goes down the host says it is an application problem. Without an agreed response time, every issue starts with finding someone who knows Drupal.

We check all four in the free site review

The deliverable

What your monthly Drupal support report shows

One short report each month, written for the person who signs off the budget. These are the six sections it always has.

6 components, every page

1
2
3
4
5
6
1

Security updates applied

Each advisory that affected your site, the version we installed, and the date it reached production.

2

Uptime and response time

Uptime for the month, any outage with its cause and length, and average server response time from monitoring checks.

3

Backups tested, not just taken

The date of the last restore test, how long the restore took, and what we checked on the restored copy.

4

Hours used against the plan

Hours used, hours left and what each block of time went on, so the invoice is never a surprise.

5

Tickets fixed, with notes

Every ticket closed that month, what changed, and where it was tested before release.

6

Next month's recommendations

Updates coming up, modules to replace and risks we see, ranked so you can decide what to fund first.

The fix

Drupal support and maintenance that runs on a schedule.

Every retainer is built around the verticals it serves. Below is the work — and we'll tell you on the audit call which of these actually move the needle for your situation.

8
Workstreams
90d
First ranking move
Talk to a strategist
  • Drupal security advisories checked in every Wednesday release window, with fixes for your installed versions applied within the response time in your contract
  • Core and contributed module updates run through Composer and tested on staging before they reach production
  • Configuration exported to Git with every change, so production always matches the code you own
  • Database and file backups stored away from your server, with a restore tested every month
  • Uptime and response-time monitoring, with alerts going straight to the people who can fix the site
  • A set number of hours each month for fixes, small features and editor help, tracked against the plan
  • Upgrade planning: Drupal 10 reaches end of life on 9 December 2026, and Drupal 7 sites need a route to Drupal 11
  • A monthly report covering updates applied, uptime, backup tests, hours used and what we recommend next

How we deliver

A phased rollout — not a 100-page strategy doc.

You see live work shipped every month, with quarterly executive reviews to recalibrate priorities.

1

Onboarding

Month 1

  • Site audit: versions, modules, patches, custom code
  • Git, Composer and staging set up if missing
  • First backup and restore test
  • Monitoring and alerts configured
2

Every month

Months 2–3

  • Security advisories reviewed and applied
  • Core and module updates, staging first
  • Tickets worked from your plan hours
  • Monthly support report
3

Every quarter

Month 4+

  • Upgrade and end-of-life review
  • Performance check
  • Unused modules and accounts removed
  • Roadmap call

Why us, for this vertical

What we bring that the generic agency down the street doesn't.

Good support is mostly routine work done on time. These are the four habits we bring to every Drupal retainer.

Staging first, every time

Every update runs on a staging copy before it touches production. Composer lock files and exported configuration are committed to Git, so each release can be traced, reviewed and rolled back if something breaks.

Drupal is our main work

Drupal development is our flagship service. We built acuative.com on Drupal 11 and published a contributed module, Migrate Redirect Map, on drupal.org. Your site is looked after by people who work in Drupal code every week.

Backups proven by restoring them

A backup only counts if it restores. Each month we restore your database and files to a separate environment, check that the site loads and logins work, and record the result in your report.

Response times in writing

Response times for critical, high and normal issues are agreed and written into the contract before work starts, along with the hours they cover. You always know who answers and how quickly.

FAQ

Got questions?

The same questions every prospect asks. Don't see yours? Tell us — answers within one business day.

Ask us anything

What does a Drupal support and maintenance plan include?

Security updates for core and contributed modules, Composer updates tested on staging, backups with a monthly restore test, uptime monitoring, and a set number of hours for fixes and small improvements. Response times for each severity are agreed in the contract. Each month ends with a report showing what was updated, what was fixed, the hours used and what we recommend next.

How much does Drupal support cost?

The main drivers are the number of sites, the Drupal version, how much custom code and how many contributed modules you run, the hosting setup, the monthly hours you need and the response times you want, including any out-of-hours cover. Drupal 7 sites take more care. The free site review looks at all of this and ends with a fixed monthly quote.

How quickly do you apply Drupal security updates?

The Drupal security team publishes advisories in a weekly window, usually on Wednesdays, and gives advance notice of some highly critical core releases through a public service announcement. We check every release against the versions on your site, apply the relevant fixes on staging, then deploy to production. The exact response time for each severity is written into your contract.

Do you support Drupal 7 sites?

Yes, as a bridge. Drupal 7 reached end of life on 5 January 2025 and the Drupal project no longer publishes security releases for it, so no support plan can make it as safe as a supported version. We keep Drupal 7 sites backed up, monitored and hardened while we plan the move to Drupal 11 with our Drupal migration team.

How do the monthly hours work?

Your plan has a set number of hours each month for tickets, fixes and small improvements. The contract states which routine work counts against those hours, whether unused hours roll over, and how extra hours are approved before anyone works them. Every monthly report shows hours used against the plan, ticket by ticket, so there are no surprises on the invoice.

Can you take over a Drupal site another agency built?

Yes. Onboarding starts with an audit of core and module versions, applied patches, custom code, hosting, backups and access. If the site has no Git repository, Composer setup or staging copy, we set those up first. You keep ownership of the code, the hosting and every account; we work through the access you grant and hand it back if you leave.

Is a support retainer better than hiring a Drupal developer by the hour?

For a one-off feature, a Drupal developer for hire by the hour can be enough. Maintenance is different: security updates, backup tests and monitoring need to happen every month whether or not anything is broken, and someone has to be responsible when it is. A retainer puts that routine and agreed response times into one contract.

Should we upgrade from Drupal 10 to Drupal 11 now?

Yes, if you have not started. Drupal 10 reaches end of life on 9 December 2026. The upgrade is done in place: Upgrade Status lists deprecated code and modules without a Drupal 11 release, custom code is updated, then Composer and database updates run on staging before production. It can run inside your monthly hours or as a separate fixed-price project.

Free SEO audit

Ready to hand off Drupal maintenance?

Get a free 30-minute audit. We'll walk through your current rankings, the keywords you're missing, and what we'd do in the first 90 days. No deck, no sales pitch.

Or email [email protected]

Field Notes

Get the next one by email

Research on Drupal, WordPress and search. Measured, not guessed. New pieces straight to your inbox.

Confirmed opt-in. One click to leave, any time.