← Back to blog

Guides

Adobe's SaaS Pivot: What ACCS and 'No Magento 3' Mean If You Own Your Store

June 25, 2025 - by Alexandru-Manuel Carabus

In 2025 Adobe made its direction clear: SaaS with ACCS, and no Magento 3. Here is what that split means if you own and self-host your Magento store.

A navy rail splitting into two paths: on the left an open modular structure, on the right a smooth sealed capsule glowing blue, with an orange accent at the fork, illustrating two diverging platform lanes.

In June 2025, Adobe Commerce as a Cloud Service and Adobe Commerce Optimizer reached general availability. Around the same time, Adobe made another thing clear: there is no Magento 3 coming. The 2.4.x line is the long-term architecture. Put together, these two facts define the platform for the next several years.

There are two Adobe Commerces now

The platform has split into two lanes. One is the self-managed lineage you already know, Adobe Commerce and Magento Open Source, code you host and control. The other is Adobe Commerce as a Cloud Service, a SaaS product Adobe operates for you. They share a heritage, but they are different products with different trade-offs.

'No Magento 3' is good news, not bad

Some merchants read the absence of a Magento 3 as decline. It is closer to the opposite. Adobe committed to the 2.4.x line as long-term support, with each release now carrying a three-year support window. That means no forced rewrite, no repeat of the Magento 1 to Magento 2 migration pain. Stability is the underrated feature here.

What the SaaS pitch gives, and what it takes

ACCS trades control for convenience. You get less infrastructure to manage and a faster launch. You give up direct access to the full codebase and the ability to change anything you like. That access is exactly what makes a self-hosted store adaptable, and it is worth being honest that a managed platform narrows it by design.

Who ACCS actually fits

The SaaS path suits merchants who want to standardize, who have limited engineering appetite, and who do not need deep customization. Self-hosted Magento still fits merchants whose store is the business, who need control over the checkout, the data and the roadmap. Neither is wrong. They serve different bands.

If you own your code, you keep your options

The advantage of owning your stack is optionality. When we rebuilt Vitacom on a stack they control, the store went from a PageSpeed score of 12 to 100 and a time to first byte of 15,814ms down to 12ms, on eight times less hardware. That kind of result depends on being able to touch every layer. Adobe adding a SaaS lane does not remove that lane. If you want help deciding which one your business belongs in, read our Vitacom case study or book a free strategy call with LIQUIDLAB.