Support and maintenance
Ongoing support and maintenance for your Drupal project: security updates automated from advisory to tested fix, support for your editors, and development capacity when you need it.
Once the new site has been launched and the intense development phase has come to a slower volume, we usually switch to a maintenance contract. This covers all upgrades needed to the content management system, optimization of the new site, and addressing any glitches found after the launch.
We propose to allocate fixed work hours per month with guaranteed response times. This provides us with a decent amount of capacity to deal with support issues, or even smaller tweaks and improvements on top of the regular security updates.
Security updates that keep pace with AI-era disclosure
Drupal security advisories have more than doubled in 2026: 306 by the end of October, against 134 in the whole of 2025. AI-assisted vulnerability discovery is behind the surge, and release days now bring dozens of advisories at once. A fix only protects your site once it is installed, so the pressure lands on maintenance.
Nobody can answer twice as many advisories with twice as many people. We built our own tooling to take the mechanical part of security patching off our developers' desks, so every site we maintain gets a tested fix within hours:
- Security monitoring. The drupal.org advisory feed is checked every 30 minutes and a full
composer auditruns on every project every six hours, against each project's own lock file. We know within minutes which sites are affected. - Ticket creation. For each affected project a Jira ticket is opened with the advisory, the CVE, the smallest safe version bump and the exact update steps. Patch releases are preferred and a major version is never crossed automatically.
- AI-assisted resolution. An AI coding agent applies the update in its own copy of the project, runs the database updates, exports the configuration they change and keeps every patch the project depends on, one commit per package.
- Test environment and automated tests. Every fix gets a live preview environment. The project's test suites and the Drupal status report run before and after the change, so the pull request shows exactly what changed.
- Human review. A pull request is only opened when verification passes. A developer reviews and merges; AI does the legwork, people make the decision.
From advisory to tested fix
Flat-rate security maintenance
Automating the routine work keeps maintenance costs down even as the number of advisories keeps growing, so we offer security maintenance at a flat monthly rate: predictable costs for keeping your Drupal site patched and secure. It includes:
- Continuous monitoring of Drupal core, contributed modules and Composer dependencies.
- Tested security updates within hours of an advisory, with a preview environment and test results on every pull request.
- The same rules on every project: the smallest change that closes the vulnerability, no silently dropped patches, tests before and after.
- Developer review of every fix, and hands-on work for the hard cases: major upgrades, dependency conflicts, end-of-life modules.
- A monthly report of what was patched, when, and what is coming.
As a Gold-tier Drupal Certified Partner we contribute to Drupal ourselves and follow the work of the Security Team closely, so when the way advisories and security releases are handled changes, our processes and tooling adapt early.
Agile and maintenance
we use the Kanban methodology for this purpose which maximizes the throughput and minimizes the reaction time of the team. When there is a higher maintenance and development plan we also set monthly goals and work towards them while keeping an eye on the monitoring system and client support requests.
Our support process
- We delegate a primary contact person, who is in touch with the client.
- We provide a central email address per client for new requests.
- In some cases we open Slack channels for our clients as well.
- First we always verify confirm the incoming issues back to the client, then based on assessment we create a ticket.
- We use Jira track support tickets on Kanban boards.
- The client is notified about the status updates of the tickets.