Magento & Adobe Commerce Support

Security patching cadence (Adobe's quarterly releases plus out-of-band hotfixes), platform version upgrades, B2B portal maintenance, indexer + cron health, Varnish / Redis / Elasticsearch tuning, custom module compatibility, Core Web Vitals monitoring, defined incident response, and a named PHP / Magento engineer with context. Growth and Mission-Critical tiers add reserved sprint capacity and after-hours pager coverage.

We monitor every Adobe Security Advisory (PSIRT) the day it ships, score impact against your stack, and schedule a patch window — usually within 72 hours for high-severity advisories, faster for actively-exploited CVEs. Every patch goes through a regression pass on staging across PDP, PLP, checkout, and custom modules before production deploy. We do this every quarter and out-of-band when Adobe ships a hotfix.

Yes — most retainers we run start that way. We open with a stack audit (composer.json review, extension inventory, custom module spelunking, Varnish + Redis config check, indexer state), document a runbook, and run a 30-day stabilization period before SLA clocks start. 15 years on Magento means we've inherited every kind of legacy.

15 years of continuous Magento focus — from Magento 1 (now fully sunset) through the Magento 2 transition, the Adobe acquisition, and the current Adobe Commerce / Commerce Cloud / Open Source split. Senior Magento bench, in-house, not contract-flipped.

We instrument all eleven Magento indexers (catalog_product_price, cataloginventory_stock, catalogsearch_fulltext, customer_grid, design_config_grid, and the rest) with alerting on stuck consumers, schedule mode lag, and reindex duration. Cron consumer queues — including RabbitMQ-backed async indexers when configured — are monitored separately so a stalled queue doesn't cascade into stale prices or missing stock counts.

Yes. Hyvä's Tailwind + Alpine.js front-end has dramatically different operational characteristics than Luma — much less JS, much faster paints — and we run support for it with CWV targets and theme upkeep tuned to that stack. PWA Studio (React on Magento GraphQL) is also supported, though Adobe's PWA Studio roadmap is now in maintenance mode and we'll be honest about that with you.

Open Source (formerly Community), Adobe Commerce (formerly Enterprise), and Adobe Commerce on Cloud (managed Magento on AWS) are all supported. The patching cadence and security tooling are identical; Commerce Cloud adds Fastly, managed Varnish, and Adobe-side infrastructure escalation paths. We tailor the runbook to your edition.

Yes. The PHP 8.2 → 8.3 → 8.4 transition (Magento 2.4.7+ requires PHP 8.2; 2.4.8 supports 8.3 and 8.4) is a regular line item. We test against the new PHP version on staging, scan every custom module and paid extension for incompatibilities, and roll forward only when the regression set is clean.

On Mission-Critical SLA, P1 incidents (storefront down, checkout broken, admin lockout, stuck indexers affecting catalog) get a response under one hour and mitigation targets under four hours, with after-hours pager coverage. Growth tier is same-day for priority issues. Maintenance is business-hours response. Every tier has clear severity definitions written into the retainer.

Maintenance tiers are flat monthly retainers; Growth tier adds reserved sprint capacity priced per hour; Mission-Critical SLA is priced on response targets and after-hours coverage. Adobe Commerce stores typically sit higher than Open Source due to B2B feature surface area. You'll see a band on the first call after we audit the stack.

Named PHP / Magento engineer with a named backup, plus a delivery lead who owns the retainer. The queue is internal infrastructure — you talk to the same two people every week.