Service
Legacy & long-term support
Long-term ownership for sites that need to keep running — security patches, framework updates, performance tuning, and operational stability across years, not weeks. Includes Drupal 7 long-tail support after EOL.
Most Drupal sites do not fail at launch — they rot afterwards: unpatched, un-updated, un-owned. We take that ownership: security on time, framework updates before they are forced, performance watched, and an engineer who knows the codebase when something breaks at 2 a.m. Drupal 7 sites still in production after EOL included.
Scope
How the work is delivered
-
Security & patch management
Core and contrib security advisories applied on a schedule you can audit — SA-CORE criticals fast-tracked — with a tested rollback path and a changelog you can hand to a security review.
-
Framework currency
Minor and major Drupal updates planned before end-of-life forces a panic migration: dependency audits, deprecation fixes, contrib upgrades, and a clear runway from where you are to a supported version.
-
Drupal 7 long-tail support
For sites that cannot move yet — extended-support tracking, hardening, targeted backports, uptime maintenance — plus an honest migration plan for when the business is ready.
-
Performance & stability watch
Structured logging, error and uptime alerting, performance budgets, and periodic health reviews — so regressions surface in a dashboard, not in a customer complaint.
-
Owned codebase
Config in git, CI gates, documented deploys, and an engineer who carries context across years — not a ticket queue staffed by whoever is free. You always know who fixes it.
Recent builds
Where we shipped this
Talk through the build
Send the platform, constraints, and timeline. We'll reply with the engineering questions that decide scope.
- Reply within one business day, weekday hours UA / EU.
- 30-minute discovery call when it is useful.
- Scope written around deliverables, risks, and ownership.