Service
Drupal support & ongoing development
We keep Drupal 7, 9, 10 and 11 platforms running in production: a German auto-parts marketplace carrying 2.4 million parts, a national newspaper archive, and a garden nursery we have maintained since 2015. Several of them we inherited from another vendor.
Most Drupal sites do not fail at launch. They rot afterwards: an advisory nobody applied, a module nobody bumped, and eventually an upgrade that costs more than the original build did. When we picked up AWHelp24 in 2025 the first pass through the codebase turned up backdoors, and credentials committed inside the webroot. That is what an unowned platform looks like from the inside, and it had been serving emergency calls in that state.
Scope
How the work is delivered
-
Security & patch management
Core and contrib advisories applied on a schedule you can audit, with SA-CORE criticals fast-tracked. Every change carries a tested rollback path and a changelog you can hand to a security review.
-
Framework currency
Minor and major updates planned well before an end-of-life date turns them into an emergency: dependency audits, deprecation fixes, contrib upgrades, and a dated runway to a supported version.
-
Drupal 7 long-tail support
Partsbit still runs on Drupal 7 because moving 2.4 million parts and 50+ custom modules is a project, not a weekend. Sites in that position get hardening, targeted backports, extended-support tracking, and GPSR-style compliance work shipped on the live platform. The migration plan comes with it, for whenever the business is ready.
-
Performance & stability watch
Structured logging, error and uptime alerting, performance budgets, and periodic health reviews. Regressions should reach us before they reach your customers.
-
Owned codebase
Config in git, CI gates, documented deploys, and the same engineer carrying context across years. When Microsoft changed the Dynamics 365 API under Walnut Creek Foods, the fix landed in an integration we had written and understood, not one we were meeting for the first time.
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.