Senior Drupal Retainers

Drupal Support and Maintenance Services

A senior Drupal team on retainer. Security patching, performance tuning, feature development, and an SLA you can actually enforce.

Plans from 10 hours per month. Unused hours roll over. No tier shuffling, no surprise invoices.

Book a Scoping Call See Plans

The agency that built your site is gone. Now what?

The most common call we get: "our original agency wound down, the site runs fine, but nobody is watching it anymore." Drupal sites do not fail loudly. They drift, and by the time someone notices, the recovery is expensive.

Security updates stop

Drupal core and contrib get security releases on a schedule. Without someone tracking and applying them, your site accumulates known vulnerabilities fast.

Small bugs turn into outages

A full cache, a broken cron job, or a crashed Solr index starts as a minor inconvenience and becomes a production fire in a few weeks.

Feature requests sit

"We just need a small change" turns into a six week negotiation with a freelancer who has to learn your codebase first. Nothing ships.

What your retainer actually buys

A retainer is not "an hourly rate on call". It is a team that knows your codebase, responds to incidents, and keeps your site healthy between feature requests.

Security patching

Every Drupal core and contrib security release applied within one business day of publication. Tested on staging, deployed to production, you get a written summary.

Minor version upgrades

Drupal core minor releases (10.1, 10.2, 10.3, etc) applied as they land. Regression tested, deployed, documented.

Bug fixing

Something broken in production? Submit a ticket. We triage, reproduce, fix, and deploy. SLA response times start at 4 business hours.

Feature development

New content types, Views, forms, workflows, custom modules, or front end changes. Scoped from retainer hours, or broken out as a fixed scope project.

Performance tuning

Quarterly performance audits: cache hit rates, slow queries, Core Web Vitals, image optimization. We fix the hot spots before they become complaints.

Monthly health report

A written summary every month: what we patched, what we deployed, what we noticed, and what you should consider next quarter.

Retainer plans

Three tiers, all including the same scope. The difference is hours and SLA response times. Every plan can be paused or cancelled with 30 days notice.

Essentials

For small to medium Drupal sites that mostly need security patching and occasional fixes.

  • 10 hours per month
  • Security patches within 1 business day
  • SLA response: 8 business hours
  • Monthly health report
  • Unused hours roll over 1 month
Get Started
MOST POPULAR

Growth

For active sites with regular feature requests and moderate traffic.

  • 25 hours per month
  • Security patches within 1 business day
  • SLA response: 4 business hours
  • Quarterly performance audit
  • Unused hours roll over 2 months
  • Monthly health report
Get Started

Enterprise

For business critical sites with strict SLAs and active development.

  • 60+ hours per month
  • Critical security patches within 4 hours
  • SLA response: 2 business hours
  • Dedicated senior engineer
  • Monthly performance audit
  • Custom SLA options
Contact Sales

Frequently asked questions

What teams ask most before signing a support retainer.

Do we need to host with you to sign up for support?

No. Support retainers work with any host. If you want hosting and support bundled we can do that too, and our managed Drupal hosting includes some support activities in the base plan. But the two are priced and scoped separately.

What happens if we need more than our monthly hours?

Overflow hours are billed at the same hourly rate as your retainer, no premium. For larger feature projects we scope them out as fixed price work so you always know the total cost upfront. We never surprise you with a bill.

Do unused hours really roll over?

Yes. Essentials plans roll unused hours forward for one month. Growth plans roll for two months. Enterprise plans can negotiate custom rollover terms. This way a quiet month stores up capacity for a busy one.

How does the SLA response time work?

SLA response is the time from ticket submission to a human engineer acknowledging the ticket with a triage plan. It is not the time to fix. For a clear bug we usually fix and ship the same day. For a complex issue the acknowledgment includes an estimated time to resolve.

Can you take over a site another agency built?

Yes, and that is most of our work. The first month includes a code handover audit: we read through the custom modules, document the architecture, get the local dev environment working, and flag any risks. After that we run the site like we built it.

What if we want to cancel?

30 days written notice, no cancellation fees, no questions. We hand off clean documentation and any work in progress. The goal is a working partnership, not a lock in.

Keep your Drupal site in good hands

Book a 30 minute scoping call. We review your site, map out what your team actually needs, and propose the right plan.

Book a Scoping Call