Skip to content

Published 5 min read

Is Magento 2 dying? Adobe Commerce at eleven

Magento 2 turns eleven this month. The dates Adobe has published, what its new hosted product changes, and how to decide whether to stay, move or leave.

NT Founder of Pitstop Technologies. Junior engineer to CTO.

A shop owner holding van keys stands between a red van being serviced on a lift, a blue tram gliding past outside and volunteers building the same van from a crate of parts.

Magento 2 became generally available on 17 November 2015. I remember it arriving. After Magento 1 it felt like a different class of platform: a modern codebase, a proper checkout, tooling that developers actually wanted to use.

It turns eleven this month, and the question I hear from shop owners is whether it is dying.

The short answer is no. The longer answer is that "Magento" now means three different things, and they are heading in different directions. Which one you are on decides what you should do.

Three things share one name

Adobe's hosted product. In mid-2025 Adobe launched Adobe Commerce as a Cloud Service, together with a product called Commerce Optimizer. Adobe runs the application, the infrastructure and the upgrades. You no longer install PHP modules inside it. You extend it from outside, through its APIs and Adobe's App Builder. Adobe's release notes show where its new work is going.

The 2.4 line you already know. This is Adobe Commerce on Adobe's cloud or your own servers, and Magento Open Source. Same PHP application, same extension model. Version 2.4.9 was released on 12 May 2026.

The community. Mage-OS is a community distribution built on Magento Open Source; its version 3.0 came out in May 2026, built on 2.4.9. And the Hyvä theme, a widely used way to give a Magento shop a fast modern storefront, has been free and open source since November 2025.

The dates that matter

Adobe gives each version at least three years of standard support, sometimes a little more. These dates are from Adobe's own lifecycle policy:

VersionReleasedStandard support ends
2.4.912 May 202631 May 2029
2.4.88 April 202531 May 2028
2.4.79 April 202431 May 2027
2.4.614 March 202311 August 2026
2.4.59 August 202212 August 2025

Two things to read from that table. If your shop runs 2.4.6 or older, standard support has already ended, and that is the urgent problem, well ahead of any question about the platform's future. And a shop on 2.4.9 has published support until the end of May 2029.

One thing the table does not say. The policy is written for Adobe Commerce, the paid product. It does not mention Magento Open Source, and I have not found a public Adobe roadmap for the 2.4 line beyond 2.4.9. That is an open question, which is different from an end date.

What "dying" gets right

Adobe's new effort is going into the hosted product, and that product is extended in a different way. The skills, the extensions and the agencies built around PHP modules matter less to where Adobe itself is going. If you pay for an Adobe Commerce licence, expect the conversation with Adobe to keep moving towards the hosted version.

It is also true that a Magento shop is not something you can leave alone. A three-year support window means an upgrade is a regular cost, and skipping two of them is how shops end up unsupported.

What it gets wrong

The code is open. Adobe Commerce 2.4.9 has published support into 2029. A community distribution exists and is releasing on its own schedule. And modernising the storefront, which used to be the most expensive part of keeping a Magento shop competitive, no longer starts with a theme licence.

A platform with all four of those is not disappearing. What is changing is who decides its future.

What I would do

Your situationSensible directionCheck first
On 2.4.8 or 2.4.9, the shop works, your team knows itStay and keep currentIs an upgrade budgeted every year, with extension updates included?
On 2.4.7Plan the upgrade now, before 31 May 2027Which extensions need updating first?
On 2.4.6 or olderUpgrade now, then decide the rest calmlyWhich extensions block the upgrade, and are they still maintained?
Paying for Adobe Commerce, mostly standard featuresEvaluate the hosted productCan each customisation and extension be rebuilt through the APIs? That is the real cost.
On Open Source and wanting a faster community paceLook at Mage-OSIt supports only its latest release, so can you keep up with it?
Small catalogue, simple needs, Magento is more than you useA simpler platform may cost less to runWhat happens to your URLs, search rankings, integrations and order history?

Whichever row you are in, I'd ask whoever maintains the shop five things. Which exact version are we on, and when does its support end? When was the last security patch applied? Which extensions are no longer maintained? Is there a working copy of the shop where an upgrade can be tested? And who decides when we upgrade: us, or an incident?

The lesson from last time

Moving from Magento 1 to Magento 2 was never an upgrade. It was a rebuild, and many shops left it until Magento 1's support ended on 30 June 2020. The ones that planned a year ahead chose their timing. The ones that waited had it chosen for them.

Nothing in Adobe's published dates forces that kind of decision today. But the dates are public, and the next one that applies to you is in the table above. If you'd like a second opinion on where your shop stands, that is part of my Magento 2 and ecommerce development work.

A useful next step, for your business.

Tell me what your website needs to do. I’ll help define the scope, responsibilities and next step.

Calls are in English or Romanian, whichever you prefer.