# Drupal Incident Response ## 24/7 Drupal Support When Production Is at Risk ### Fast, Senior-Level Intervention for Critical Issues #### Stabilize First. Fix Safely. Prevent Recurrence. Request Incident Support When your Drupal site is down, compromised, or behaving unpredictably in production, every minute matters. Our Drupal Incident Response service provides 24/7 Drupal support with immediate, senior-level technical intervention to stabilize your platform, protect data, and restore normal operations as quickly and safely as possible. If you need a Drupal website down fix, Drupal downtime support, or an emergency Drupal developer to triage a critical failure, we help you regain control fast. This service is designed for high-pressure situations where rapid diagnosis, calm execution, and deep Drupal production support expertise are essential—including Drupal security incident response and Drupal outage recovery. #### Response Focus ##### Production outages ##### Security incidents ##### Critical bugs & data issues #### Availability * On-demand engagement * No long-term contract required * Priority handling #### Who Responds * Senior Drupal engineers * DevOps & infrastructure expertise * Incident-tested workflows #### Best Fit For * Business-critical Drupal platforms * Enterprise & high-traffic sites * Teams needing immediate expertise ![Drupal Incident Response 1](https://res.cloudinary.com/dywr7uhyq/image/upload/w_644,f_avif,q_auto:good/v1/service-drupal-incident-response--problem--sudden-production-outage) ![Drupal Incident Response 2](https://res.cloudinary.com/dywr7uhyq/image/upload/w_644,f_avif,q_auto:good/v1/service-drupal-incident-response--problem--security-breach-exposure) ![Drupal Incident Response 3](https://res.cloudinary.com/dywr7uhyq/image/upload/w_644,f_avif,q_auto:good/v1/service-drupal-incident-response--problem--deployment-failure-and-broken-pipeline) ![Drupal Incident Response 4](https://res.cloudinary.com/dywr7uhyq/image/upload/w_644,f_avif,q_auto:good/v1/service-drupal-incident-response--problem--performance-collapse-under-load) ![Drupal Incident Response 5](https://res.cloudinary.com/dywr7uhyq/image/upload/w_644,f_avif,q_auto:good/v1/service-drupal-incident-response--problem--data-integrity-and-integration-breakdown) [Related: SLA-based Drupal Support](/services/drupal-support/sla "24/7 Drupal Support When Production Is at Risk") ## When Drupal Fails in Production Drupal incidents rarely happen in isolation. A sudden outage, failed update, broken deployment, security breach, or data inconsistency can cascade across caching layers, integrations, and infrastructure—impacting revenue, reputation, and internal operations immediately. When a Drupal website goes down, teams often face incomplete signals (partial logs, noisy alerts, unclear recent changes) and must make high-stakes decisions under time pressure. In these moments, ad-hoc troubleshooting and trial-and-error changes increase operational risk. Quick fixes applied directly in production can introduce new regressions, widen the blast radius, or mask the real failure mode. Common symptoms—like a Drupal white screen of death, fatal PHP errors, or post-deploy configuration drift—can be caused by multiple interacting factors, making it hard to distinguish application defects from infrastructure or dependency failures. Security events add another layer of complexity. A suspected compromise can require containment, access review, and careful validation of what changed and what data may have been exposed. Without disciplined incident management, organizations can lose time, lose evidence, and prolong downtime—turning a recoverable disruption into a recurring reliability and governance problem. ## Our Incident Response Approach ### Rapid Assessment Immediate triage to understand impact, scope, and risk. ### Stabilization First Stop the bleeding before attempting deeper fixes. ### Safe Remediation Targeted fixes with minimal blast radius. ### Security Verification Check for compromise, vulnerabilities, and data exposure. ### Clear Communication Transparent updates during every phase of the response. ### Post-Incident Guidance Concrete recommendations to prevent recurrence. ## What This Service Covers (Drupal Downtime Support) Drupal Incident Response provides structured, high-priority Drupal support for stabilizing business-critical platforms under pressure. It combines disciplined triage, controlled remediation, Drupal security incident response, deployment recovery, and performance diagnostics within incident-tested engineering workflows. The focus is on restoring operational continuity while protecting data integrity, release governance, and architectural consistency. Root-cause analysis and targeted safeguards help reduce repeat incidents and ongoing maintenance overhead. ![Feature: Production Outages](https://res.cloudinary.com/dywr7uhyq/image/upload/w_580,f_avif,q_auto:good/v1/service-drupal-incident-response--core-features--production-outages) 1 ### Production Outages White screens, fatal errors, broken releases, or infrastructure failures can immediately disrupt business operations. We rapidly diagnose the root cause, restore availability, stabilize the environment, and implement safeguards to prevent recurrence while minimizing downtime impact—including when you need a Drupal website down fix. ![Feature: Security Incidents](https://res.cloudinary.com/dywr7uhyq/image/upload/w_580,f_avif,q_auto:good/v1/service-drupal-incident-response--core-features--security-incidents) 2 ### Security Incidents Hacked sites, malware injections, suspicious behavior, and unauthorized access require structured containment and remediation. We isolate the threat, secure compromised components, patch vulnerabilities, and harden the platform to restore trust and operational safety—including Drupal hacked website recovery and Drupal malware removal services when applicable. ![Feature: Deployment Failures](https://res.cloudinary.com/dywr7uhyq/image/upload/w_580,f_avif,q_auto:good/v1/service-drupal-incident-response--core-features--deployment-failures) 3 ### Deployment Failures Broken CI/CD pipelines, failed configuration imports, and unstable releases can block delivery or disrupt production. We analyze deployment logs, correct pipeline misconfigurations, perform safe rollbacks when necessary, and re-establish a stable release workflow—including help to fix a Drupal site after a failed update. ![Feature: Performance Collapse](https://res.cloudinary.com/dywr7uhyq/image/upload/w_580,f_avif,q_auto:good/v1/service-drupal-incident-response--core-features--performance-collapse) 4 ### Performance Collapse Sudden slowdowns, traffic spikes, caching failures, or infrastructure bottlenecks can severely impact user experience. We investigate performance metrics, optimize caching layers, adjust scaling strategies, and restore system responsiveness under real-world load conditions. ![Feature: Data Integrity Issues](https://res.cloudinary.com/dywr7uhyq/image/upload/w_580,f_avif,q_auto:good/v1/service-drupal-incident-response--core-features--data-integrity-issues) 5 ### Data Integrity Issues Corrupted content, failed migrations, sync errors, or inconsistent data structures require careful validation and recovery. We audit affected datasets, restore backups where needed, repair structural inconsistencies, and implement safeguards to protect data integrity moving forward. ![Feature: Third-Party Breakages](https://res.cloudinary.com/dywr7uhyq/image/upload/w_580,f_avif,q_auto:good/v1/service-drupal-incident-response--core-features--third-party-breakages) 6 ### Third-Party Breakages APIs, integrations, or external services can introduce instability when dependencies fail or change unexpectedly. We isolate integration issues, apply fallback strategies, restore stable connections, and reinforce monitoring to reduce dependency-related risks. Core Capabilities * Drupal 5 / 6 / 7 / 8 / 9 / 10 / 11 * Multisite & multisite factories * Custom modules & distributions * Cloud & on-prem hosting * CI/CD & deployment pipelines Who Uses This Service * CTOs & Engineering Leads * Product Owners * Digital & Platform Teams * Agencies needing backup expertise Technology Scope * Drupal core & contrib * PHP, Symfony * MySQL / PostgreSQL * Redis, Varnish, Solr * AWS, Acquia, Pantheon, custom infra ## How Engagement Works Our Drupal Incident Response delivery model is a clear engineering sequence—from intake and access through live investigation, stabilization, verification, and documented follow-up. It is designed for urgent support scenarios where Drupal downtime support, safe change control, and fast coordination with your team are required. The emphasis stays on controlled recovery in production and reducing the risk of repeat incidents. ![Delivery card for Immediate Intake](https://res.cloudinary.com/dywr7uhyq/image/upload/w_540,f_avif,q_auto:good/v1/service-drupal-incident-response--delivery--immediate-intake)\[01\] ### Immediate Intake You contact us through an emergency channel and describe the issue, impact, and urgency level. We immediately classify the incident, define severity, and initiate structured response procedures without delay. ![Delivery card for Access & Context](https://res.cloudinary.com/dywr7uhyq/image/upload/w_540,f_avif,q_auto:good/v1/service-drupal-incident-response--delivery--access-and-context)\[02\] ### Access & Context We securely obtain required system access and gather critical context, including recent deployments, infrastructure changes, and monitoring logs. This ensures we begin investigation with complete technical visibility. ![Delivery card for Live Investigation](https://res.cloudinary.com/dywr7uhyq/image/upload/w_540,f_avif,q_auto:good/v1/service-drupal-incident-response--delivery--live-investigation)\[03\] ### Live Investigation Senior Drupal engineers perform hands-on diagnosis directly in production or staging environments. We analyze logs, performance metrics, error traces, and integration signals to rapidly identify the root cause. ![Delivery card for Stabilization Actions](https://res.cloudinary.com/dywr7uhyq/image/upload/w_540,f_avif,q_auto:good/v1/service-drupal-incident-response--delivery--stabilization-actions)\[04\] ### Stabilization Actions Controlled fixes are applied to restore service safely. This may include hotfix patches, configuration corrections, cache invalidation, rollback procedures, or infrastructure adjustments. ![Delivery card for Verification](https://res.cloudinary.com/dywr7uhyq/image/upload/w_540,f_avif,q_auto:good/v1/service-drupal-incident-response--delivery--verification)\[05\] ### Verification After remediation, we confirm platform stability through functional testing, monitoring validation, and performance checks to ensure services operate normally and securely. ![Delivery card for Summary & Next Steps](https://res.cloudinary.com/dywr7uhyq/image/upload/w_540,f_avif,q_auto:good/v1/service-drupal-incident-response--delivery--summary-and-next-steps)\[06\] ### Summary & Next Steps We provide a clear incident summary outlining root cause, actions taken, business impact, and prevention recommendations. This ensures transparency and reduces the likelihood of recurrence. ## Business Impact Rapid and controlled incident response directly protects revenue, customer trust, and operational continuity. Faster recovery times reduce the financial impact of outages while preventing secondary failures caused by rushed or unstructured fixes. Structured containment of security and deployment incidents lowers regulatory and reputational risk. Clear diagnostics and documented remediation provide leadership with transparency during critical moments. Over time, disciplined post-incident analysis improves platform stability and reduces the likelihood of recurring disruptions. ### Reduced Downtime Structured triage and experienced engineering intervention shorten recovery time, limiting revenue loss and customer disruption during critical incidents. ### Lower Risk Controlled remediation prevents cascading failures and avoids introducing new instability while resolving high-impact production issues. ### Confidence Under Pressure Senior Drupal engineers handle complex outages and security events, ensuring calm, methodical decision-making during high-stress situations. ### Actionable Follow-Up Each incident concludes with documented findings and clear preventive recommendations, turning crisis moments into long-term stability gains. ### Improved Long-Term Stability Root cause analysis and corrective safeguards reduce recurrence, strengthening architectural resilience and operational predictability. ## Related Services Incident response is most effective when supported by strong operational practices and a resilient platform architecture. These related services help organizations strengthen infrastructure reliability, improve security posture, and establish long-term operational stability for Drupal platforms. Together they reduce the likelihood of future incidents while improving response readiness and platform governance. [ ### Drupal Support & Incident Response Keeping Mission-Critical Drupal Platforms Stable with Ongoing Drupal Support Learn More ](/services/drupal-support)[ ### Drupal Security & Compliance Automated Deployments. Reliable Infrastructure. Learn More ](/services/drupal-security)[ ### Drupal Performance Optimization Speed Is Not a Feature. It’s Infrastructure. Learn More ](/services/drupal-performance)[ ### Drupal Monitoring & Observability Prometheus Grafana Drupal monitoring with metrics, logs, and alerting Learn More ](/services/drupal-monitoring-observability)[ ### Drupal DevOps & CI/CD Automated CI/CD Pipelines. Reliable Infrastructure. Learn More ](/services/drupal-devops)[ ### Drupal High Availability Architecture Enterprise Drupal uptime engineering through resilient infrastructure design Learn More ](/services/drupal-high-availability-architecture)[ ### Drupal Infrastructure Architecture Kubernetes Drupal infrastructure design for Drupal workloads Learn More ](/services/drupal-infrastructure-architecture)[ ### Drupal Platform Audit Enterprise Drupal Technical Assessment & Drupal Health Check Learn More ](/services/drupal-platform-audit)[ ### Drupal Monthly Retainer Support Ongoing Drupal Support Retainer for Enterprise Teams Learn More ](/services/drupal-support/retainer) ## Frequently Asked Questions Drupal Incident Response is built for high-pressure situations where production stability, security, and business continuity are at risk. This FAQ answers common questions about 24/7 Drupal support, enterprise Drupal incident management, containment steps for security events, and what to expect during Drupal outage recovery. It also covers practical engagement topics like access, coordination, risk control, and post-incident follow-up. What qualifies as a Drupal incident requiring emergency response? A Drupal incident typically involves a production outage, security breach, severe performance degradation, failed deployment, or data integrity issue that impacts business operations. If the platform is unavailable, compromised, or behaving unpredictably in production, it qualifies as a critical situation. Emergency Drupal support is appropriate when internal teams cannot safely diagnose or stabilize the issue within acceptable business timelines. The objective is immediate containment, risk reduction, and controlled restoration of service. How quickly can you respond to a Drupal production outage? Response speed depends on availability and intake channel, but emergency engagements are prioritized for immediate triage. Initial acknowledgment and investigation begin as soon as access and impact details are confirmed. The focus during the first phase is rapid assessment of severity, scope, and potential security implications. Stabilization actions are implemented quickly, followed by structured remediation to restore full functionality without introducing additional risk. Do you collaborate with internal IT or DevOps teams during incidents? Yes. Drupal Incident Response is designed to complement internal teams rather than replace them. Collaboration includes log sharing, infrastructure access, deployment history review, and coordinated communication. Clear role definition is established early in the process to avoid duplication or conflicting actions. This ensures efficient containment, faster diagnosis, and controlled decision-making during high-pressure situations. How are Drupal security incidents handled? Security incidents follow a structured containment and remediation process. The first priority is isolating compromised components, limiting exposure, and preserving forensic evidence where necessary. Once contained, vulnerabilities are patched, permissions reviewed, and affected integrations validated. Post-incident analysis identifies the entry point and corrective safeguards to prevent recurrence. The approach prioritizes both immediate protection and long-term hardening. Can you respond to incidents on legacy Drupal versions? Yes. Emergency Drupal support can include legacy environments such as Drupal 6 or Drupal 7. Many production platforms continue operating on older architectures and still require rapid stabilization during outages. While long-term modernization may be recommended, incident response focuses on restoring availability safely within the constraints of the existing architecture. Risk boundaries and technical limitations are assessed before implementing corrective actions. How do you ensure emergency fixes do not create additional instability? Incident response follows a stabilization-first methodology. Rather than applying broad changes under pressure, targeted interventions are implemented with minimal blast radius. Wherever possible, backups are secured, configuration snapshots are preserved, and rollback paths are defined before remediation. This disciplined approach reduces the risk of cascading failures and ensures that short-term fixes do not compromise long-term platform integrity. What happens after the Drupal platform is stabilized? Once service is restored, the focus shifts to root cause analysis and prevention planning. A structured summary outlines impact, actions taken, and technical findings. Recommendations may include architectural adjustments, security hardening, deployment workflow corrections, or monitoring improvements. The objective is to transform an emergency event into an opportunity to strengthen long-term platform resilience. Is ongoing monitoring or follow-up support available after an incident? Yes. After emergency stabilization, organizations often transition to structured SLA-based support or proactive retainer models to reduce future risk. Continuous monitoring, severity-based response agreements, and preventive maintenance frameworks help prevent recurrence of similar incidents. This structured follow-up improves operational predictability and lowers exposure to repeated production disruptions. How is data integrity protected during an emergency response? Before applying corrective actions, system state and database conditions are evaluated carefully. Where necessary, backups are secured and verified prior to implementing remediation steps. Data integrity checks, audit logs, and transactional validation are performed to ensure no corruption or unintended side effects occur during recovery. Protecting data consistency is treated as equally critical as restoring availability. What is the process to engage Drupal Incident Response support? Engagement begins by contacting the emergency intake channel and providing a summary of the issue, affected environments, and urgency level. Access credentials and recent deployment context are then shared securely. Once severity is classified, investigation begins immediately. The engagement concludes with stabilization, documentation, and clear next-step recommendations to ensure sustained platform reliability beyond the immediate crisis. ## Relevant Experience \[01\] ### [Bayer Radiología LATAMSecure Healthcare Drupal Collaboration Platform](/projects/bayer-radiologia-latam "Bayer Radiología LATAM") [![Project: Bayer Radiología LATAM](https://res.cloudinary.com/dywr7uhyq/image/upload/w_644,f_avif,q_auto:good/v1/project-bayer--challenge--01)](/projects/bayer-radiologia-latam "Bayer Radiología LATAM") [Learn More](/projects/bayer-radiologia-latam "Learn More: Bayer Radiología LATAM") Industry: Healthcare / Medical Imaging Business Need: An advanced healthcare digital platform for LATAM was required to facilitate collaboration among radiology HCPs, distribute company knowledge, refine treatment methods, and streamline workflows. The solution needed secure medical website role-based access restrictions based on user role (HCP / non-HCP) and geographic region. Challenges & Solution: * Multi-level filtering for precise content discovery. - Role-based access control to support different professional needs. - Personalized HCP offices for tailored user experiences. - A structured approach to managing diverse stakeholder expectations. Outcome: The platform enhanced collaboration, streamlined workflows, and empowered radiology professionals with advanced tools to gain insights and optimize patient care. \[02\] ### [Copernicus Marine ServiceCopernicus Marine Service Drupal DXP case study — Marine data portal modernization](/projects/copernicus-marine-service-environmental-science-marine-data "Copernicus Marine Service") [![Project: Copernicus Marine Service](https://res.cloudinary.com/dywr7uhyq/image/upload/w_644,f_avif,q_auto:good/v1/project-copernicus--challenge--01)](/projects/copernicus-marine-service-environmental-science-marine-data "Copernicus Marine Service") [Learn More](/projects/copernicus-marine-service-environmental-science-marine-data "Learn More: Copernicus Marine Service") Industry: Environmental Science / Marine Data Business Need: The existing marine data portal relied on three unaligned WordPress installations and embedded PHP code, creating inefficiencies and risks in content management and usability. Challenges & Solution: * Migrated three legacy WordPress sites and a Drupal 7 site to a unified Drupal-based platform. - Replaced risky PHP fragments with configurable Drupal components. - Improved information architecture and user experience for data exploration. - Implemented integrations: Solr search, SSO (SAML), and enhanced analytics tracking. Outcome: The new Drupal DXP streamlined content operations and improved accessibility, offering scientists and businesses a more efficient gateway to marine data services. \[03\] ### [DeprexisDrupal Performance Stabilization & Secure eCommerce Payment Workflows](/projects/deprexis-digital-mental-health-platform "Deprexis") [![Project: Deprexis](https://res.cloudinary.com/dywr7uhyq/image/upload/w_644,f_avif,q_auto:good/v1/project-deprexis--challenge--01)](/projects/deprexis-digital-mental-health-platform "Deprexis") [Learn More](/projects/deprexis-digital-mental-health-platform "Learn More: Deprexis") Industry: Digital Health / Mental Health Business Need: The Deprexis mental health digital platform on Drupal required stabilization, faster performance, and a secure ecommerce payment workflow to support online services. The solution needed to meet strict reliability and security expectations common for digital healthcare products. Challenges & Solution: * Critical performance bottlenecks were identified and resolved with caching and rendering optimizations. - A secure eCommerce/payment module was implemented with ABank integration for online checkout. - Automated regression coverage was introduced to protect sensitive order workflows and reduce release risk. - Quality gates were improved through test-driven delivery and repeatable validation in CI. Outcome: The platform was stabilized, performance was improved, and secure checkout workflows were delivered with strong automated coverage to reduce operational and compliance risks. \[04\] ### [London School of Hygiene & Tropical Medicine (LSHTM)Higher Education Drupal Research Data Platform](/projects/lshtm-london-school-of-hygiene-tropical-medicine "London School of Hygiene & Tropical Medicine (LSHTM)") [![Project: London School of Hygiene & Tropical Medicine (LSHTM)](https://res.cloudinary.com/dywr7uhyq/image/upload/w_644,f_avif,q_auto:good/v1/project-lshtm--challenge--01)](/projects/lshtm-london-school-of-hygiene-tropical-medicine "London School of Hygiene & Tropical Medicine (LSHTM)") [Learn More](/projects/lshtm-london-school-of-hygiene-tropical-medicine "Learn More: London School of Hygiene & Tropical Medicine (LSHTM)") Industry: Healthcare & Research Business Need: LSHTM required improvements to its existing higher education Drupal platform to better manage and distribute complex research data, including support for third-party integrations, Drupal performance optimization, and more reliable synchronization. Challenges & Solution: * Implemented CSV-based data import and export functionality. - Enabled dataset downloads for external consumers. - Improved performance of data-heavy pages and research content delivery. - Stabilized integrations and sync flows across multiple data sources. Outcome: The solution improved data accessibility, streamlined research workflows, and enhanced system performance, enabling LSHTM to manage complex datasets more efficiently. \[05\] ### [United Nations Convention to Combat Desertification (UNCCD)United Nations website migration to a unified Drupal DXP](/projects/unccd-united-nations-convention-to-combat-desertification "United Nations Convention to Combat Desertification (UNCCD)") [![Project: United Nations Convention to Combat Desertification (UNCCD)](https://res.cloudinary.com/dywr7uhyq/image/upload/w_644,f_avif,q_auto:good/v1/project-unccd--challenge--01)](/projects/unccd-united-nations-convention-to-combat-desertification "United Nations Convention to Combat Desertification (UNCCD)") [Learn More](/projects/unccd-united-nations-convention-to-combat-desertification "Learn More: United Nations Convention to Combat Desertification (UNCCD)") Industry: International Organization / Environmental Policy Business Need: UNCCD operated four separate websites (two WordPress, two Drupal), leading to inconsistencies in design, content management, and user experience. A unified, scalable solution was needed to support a large-scale CMS migration project and improve efficiency and usability. Challenges & Solution: * Migrating all sites into a single, structured Drupal-based platform (government website Drupal DXP approach). - Implementing Storybook for a design system and consistency, reducing content development costs by 30–40%. - Managing input from 27 stakeholders while maintaining backend stability. - Integrating behavioral tracking, A/B testing, and optimizing performance for strong Google Lighthouse scores. - Converting Adobe InDesign assets into a fully functional web experience. Outcome: The modernization effort resulted in a cohesive, user-friendly, and scalable website, improving content management efficiency and long-term digital sustainability. \[06\] ### [VeoliaEnterprise Drupal Multisite Modernization (Acquia Site Factory, 200+ Sites)](/projects/veolia-environmental-services-sustainability "Veolia") [![Project: Veolia](https://res.cloudinary.com/dywr7uhyq/image/upload/w_644,f_avif,q_auto:good/v1/project-veolia--challenge--01)](/projects/veolia-environmental-services-sustainability "Veolia") [Learn More](/projects/veolia-environmental-services-sustainability "Learn More: Veolia") Industry: Environmental Services / Sustainability Business Need: With Drupal 7 reaching end-of-life, Veolia needed a Drupal 7 to Drupal 10 enterprise migration for its Acquia Site Factory multisite platform—preserving region-specific content and multilingual capabilities across more than 200 sites. Challenges & Solution: * Supported Acquia Site Factory multisite architecture at enterprise scale (200+ sites). - Ported the installation profile from Drupal 7 to Drupal 10 while ensuring platform stability. - Delivered advanced configuration management strategy for safe incremental rollout across released sites. - Improved page loading speed by refactoring data fetching and caching strategies. Outcome: The platform was modernized into a stable, scalable multisite foundation with improved performance, maintainability, and long-term upgrade readiness. ## Trusted in Critical Situations Oleksiy (PathToProject) and I worked together on a Digital Transformation project for Bayer LATAM Radiología. Oly was the Drupal developer, and I was the business lead. His professionalism, technical expertise, and ability to deliver functional improvements were some of the key attributes he brought to the project. I also want to highlight his collaboration and flexibility—throughout the entire journey, Oleksiy exceeded my expectations. It’s great when you can partner with vendors you trust, and who go the extra mile. ![Photo: Axel Gleizerman Copello](https://res.cloudinary.com/dywr7uhyq/image/upload/w_100,f_avif,q_auto:good/v1/testimonial-axel-gleizerman-copello) #### Axel Gleizerman Copello ##### Building in the MedTech Space | Antler Oleksiy (PathToProject) is demanding and responsive. Comfortable with an Agile approach and strong technical skills, I appreciate the way he challenges stories and features to clarify specifications before and during sprints. ![Photo: Olivier Ritlewski](https://res.cloudinary.com/dywr7uhyq/image/upload/w_100,f_avif,q_auto:good/v1/testimonial-olivier-ritlewski) #### Olivier Ritlewski ##### Ingénieur Logiciel chez EPAM Systems Oleksiy (PathToProject) has been a valuable developer resource over the past six months for us at LSHTM. This included coming on board to revive and complete a stalled Drupal upgrade project, as well as carrying out work to improve our site accessibility and functionality. I have found Oleksiy to be very knowledgeable and skilful and would happily work with him again in the future. ![Photo: Ali Kazemi](https://res.cloudinary.com/dywr7uhyq/image/upload/w_100,f_avif,q_auto:good/v1/testimonial-ali-kazemi) #### Ali Kazemi ##### Web & Digital Manager at London School of Hygiene & Tropical Medicine ## Need Immediate Drupal Help? If your Drupal platform is unstable, compromised, or down, contact us immediately. We’ll help you stabilize the situation and regain control — fast. Request Incident Support ![Oleksiy (Oly) Kalinichenko](https://res.cloudinary.com/dywr7uhyq/image/upload/c_fill,w_200,h_200,g_center,f_avif,q_auto:good/v1/contant--oly) ### Oleksiy (Oly) Kalinichenko #### CTO at PathToProject [](https://www.linkedin.com/in/oleksiy-kalinichenko/ "LinkedIn: Oleksiy (Oly) Kalinichenko") ### Do you want to start a project? Send