Loading…
Your Full-Service Digital Agency & AI Strategy Partner
Real strategists. Real AI tools. Real growth. — 1Digital® since 2012
Workspace by 1Digital® — the agency platform we built. Coming to select agencies. Join the early-access list →
SLA-backed Magento Open Source and Adobe Commerce retainers — quarterly patching, platform upgrades, B2B portal maintenance, indexer health, Varnish + Redis tuning, and incident response from a senior 14-year Magento bench.
Trusted by 400+ Brands · Certified Partners
Of results, scale, and quality at the enterprise level.
Specialists across SEO, AI SEO, PPC, design, dev, and strategy.
US core team for clear communication; vetted global specialists for international client work.
Rated 4.9/5 across 941+ verified client reviews.
Reviewed by the 1Digital® Engineering TeamLast updated:
Who It's For
Magento support gets messy when patch windows slip, indexers stall, and the freelance dev who knew the custom modules moves on. We run it as one engineering bench with 14 years of continuous Magento focus, a named PHP engineer, and defined severities. Need new build work? Loop in our Adobe Commerce, Magento developer, Magento design, or Magento SEO teams without re-onboarding a vendor.
TL;DR
Three Retainer Tiers
Most clients start on Maintenance or Growth and step up to Mission-Critical SLA ahead of a major Adobe upgrade, a B2B portal launch, or peak season. Tiers move both directions.
Steady-state coverage for stable Magento Open Source and Adobe Commerce stores. Patch tracking, monthly indexer + cron health, Core Web Vitals review, and a named PHP / Magento engineer with full context.
Maintenance plus a roadmap. Reserved sprint capacity for B2B portal iterations, custom module work, GraphQL endpoint changes, Hyvä / PWA Studio storefront tuning, and integration changes alongside ongoing ops.
For Adobe Commerce / Commerce Cloud storefronts where downtime is measured in lost revenue. Defined severities, response and resolution targets, after-hours pager rotation, and direct escalation paths with Adobe support.
What's Covered
Adobe ships Magento / Commerce security patches roughly quarterly (March, June, September, December) plus emergency out-of-band releases. We track every advisory, schedule patch windows around your peak calendar, and run a regression pass across PDP, PLP, checkout, and any custom modules before production deploy.
Major version transitions (2.4.x line cadence), security-only patch lines, and Hotfix windows — handled end-to-end. We maintain a documented composer.json baseline, run upgrade compatibility passes for every paid Adobe extension, and keep custom modules ahead of the deprecation curve.
Adobe Commerce B2B features (Company accounts, shared catalogs, negotiable quotes, requisition lists, purchase orders, credit limits) get first-class coverage — workflow regressions, ACL drift, and approval-routing breakage caught before your buyers notice.
Varnish full-page-cache tuning, Redis session + cache health, Elasticsearch / OpenSearch index reindex windows, New Relic + Blackfire profiling, MySQL slow-query reviews, and asset pipeline (RequireJS / Magento 2 layout XML) optimization. Targets: TTFB <300ms, LCP <2.5s on PDP.
All 11 Magento indexers (catalog_product_price, cataloginventory_stock, catalogsearch_fulltext, design_config_grid, etc.) monitored with alerting. Cron consumer queues (async indexers, RabbitMQ if attached) instrumented so you don't hit a stuck index at 3pm on Black Friday.
Coverage extends across Hyvä Themes (Tailwind + Alpine.js front end), PWA Studio (React storefront on Magento GraphQL), and bespoke headless setups on Next.js. Same severity model, tuned to the rendering layer.
Defined P1 / P2 / P3 severities with response and resolution targets, structured incident logs, root-cause writeups, and post-incident remediation tickets so the same outage doesn't happen twice. New Relic + uptime monitoring included.
Modules built by us — and modules inherited from prior agencies — kept compatible across Magento upgrades, PHP version bumps (PHP 8.2 → 8.3 → 8.4), and Adobe extension updates. Composer-managed, version-controlled, and documented.
Most retainers start as post-launch handoffs from a build engagement — ours or someone else's. We onboard with a stack audit, a documented runbook, and a 30-day stabilization period before SLA clocks start.
Mission-Critical SLA
Severity definitions and targets are written into the retainer so there's no ambiguity when a Black Friday indexer stalls at 2am.
P1 — Storefront down, checkout broken, or admin lockout
Under 1 hour
Mitigation under 4 hours
P2 — Core feature degraded (search, layered nav, B2B approval flow, indexer stuck)
Under 4 business hours
Fix or workaround under 1 business day
P3 — Non-blocking issue (cosmetic, single category, single SKU, theme regression)
Next business day
Triaged into the next sprint
P4 — Roadmap request or enhancement
Next business day
Scoped + prioritized with you
Adobe Commerce B2B
Adobe Commerce's native B2B features are powerful and unforgiving — Company hierarchies, shared catalogs, negotiable quotes, requisition lists, and credit-limit logic interact in ways that quietly break when extensions update. Our retainers maintain the entire B2B surface area as a first-class concern, not a side quest.
Onboarding & Lifecycle
The first 30 days are stabilization — audit the stack, document the runbook, and surface anything that'll break before it does. SLA clocks start after handoff, not at contract signature.
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. 14 years on Magento means we've inherited every kind of legacy.
Related Magento Services
14 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.
Tell us your edition, your stack, and where it hurts — we'll come back with a retainer scope and SLA.