Adobe Commerce 2.4.6/2.4.7 End of Support: Upgrade, Mage-OS, or SaaS?

The Dates That Matter

Regular support for Adobe Commerce 2.4.6 ends August 11, 2026, with extended support running through August 30, 2027 and a security-only transitional period after that until May 31, 2028. Adobe Commerce 2.4.7's regular support ends April 9, 2027, with extended support through May 31, 2028.

If your store is on either version, that's not an immediate cutoff, but it is a forced decision inside the next 12-18 months: stay and eventually lose full support, upgrade to a currently supported version, or move to a different platform entirely. Adobe is also offering one year of additional no-cost support for stores on 2.4.6/2.4.7 covering quality and security patches, which buys some room but doesn't remove the decision.

Path 1: Upgrade and Stay on Adobe Commerce

The straightforward option is upgrading to a supported release (2.4.8 and newer). If your store's extensions and customizations are in reasonable shape, this is usually the least disruptive path, and it's what we help merchants plan and execute as part of Adobe Commerce performance optimization and cloud hosting engagements. The real cost here is usually extension compatibility testing, not the core platform upgrade itself.

Path 2: Move to Mage-OS

Mage-OS is an independent, community-governed distribution of Magento Open Source, run by the nonprofit Mage-OS Association and not affiliated with Adobe. It aims to stay compatible with existing Magento 2 extensions and integrations while merging community improvements that Adobe hasn't had the resources to include in Magento Open Source.

For merchants who want to keep full control of their infrastructure and don't need Adobe Commerce's enterprise features (B2B modules, Adobe Sensei recommendations, page builder), Mage-OS is a practical way to stay on a Magento-compatible codebase without being tied to Adobe's licensing or roadmap. Since Mage-OS shares the same core architecture as Magento Open Source, the hosting, caching, and performance work is identical, we support Mage-OS stores the same way we support Adobe Commerce Open Source ones.

Path 3: Move to Adobe Commerce as a Cloud Service (SaaS)

In June 2025, Adobe launched Adobe Commerce as a Cloud Service (ACCS), a fully managed, multi-tenant SaaS platform. Adobe handles hosting, scaling, security patches, and upgrades, and the storefront runs on a headless architecture with a separate backend Commerce Foundation. This removes infrastructure work entirely, but it also means giving up direct server access and the kind of deep customization self-hosted Adobe Commerce or Magento Open Source allows. License costs for ACCS run roughly $22,000 to $125,000+ per year depending on gross merchandise volume, on top of implementation costs.

How to Decide

The choice mostly comes down to how much you value infrastructure control versus how much you'd rather not think about infrastructure at all:

• Stay self-hosted (upgrade or Mage-OS) if your team wants control over hosting, caching, and customizations, or if the ACCS license cost doesn't make sense at your GMV.
• Move to Mage-OS specifically if you want to stay off Adobe's licensing and roadmap entirely while keeping the Magento codebase you already know.
• Move to ACCS if you'd rather pay for a fully managed platform and don't need deep backend customization.

None of these are one-size-fits-all, and the right call depends on your extension list, customization depth, and budget. If you want a second opinion before the 2.4.6 deadline, get in touch and we'll help you figure out which path fits.