Adobe Commerce as a Service: versionless, faster, smarter

Adobe Commerce as a Service drops the upgrade cycle, runs on Edge Delivery Services and embeds Adobe Sensei in the platform.

Adobe Commerce as a Service: versionless, faster, smarter

Adobe used its recent Summit to announce Adobe Commerce as a Service (ACaaS). The short version: Adobe Commerce (Magento) becomes a service Adobe operates rather than a product you maintain.

That matters because the trade-off has always been the same one. Adobe Commerce gives you flexibility, power and deep customisation, and you pay for it in total cost of ownership, security management and version upgrades that can feel like starting from scratch.

No more upgrades

ACaaS is versionless. Adobe applies platform updates and security patches in the background, with backward-compatibility guarantees so your customisations and integrations keep working.

Every new version used to be a project: months of development, a full test cycle, and re-platforming whatever had been customised. That budget and that time came out of the same pot as the features that actually sell things. Removing the upgrade cycle lowers TCO and hands the development budget back.

Performance, via Edge Delivery Services

Speed still moves the number. A one-second delay in page load time can reduce conversion rates by 7%.

ACaaS runs on Adobe's Edge Delivery Services (EDS), serving storefront content — images, CSS and JavaScript — from a global network close to the customer. Adobe is quoting sub-second page loads and near-perfect Lighthouse scores. Hanesbrands, an early adopter, saw page speeds increase by a factor of four. That feeds SEO, organic traffic, engagement and conversion, in roughly that order.

Headless by default

The storefront is decoupled from the commerce engine via modern APIs. You can build a custom mobile app, an in-store kiosk or a social commerce integration without the backend having an opinion about it.

This part is not new territory for us. We have been building headless commerce for over a decade, which means we are less interested in the architecture diagram than in what it costs to run and how quickly a merchandiser can get a change live on it.

AI in the platform

Adobe Sensei is embedded in the platform rather than bolted onto it.

Merchandising. Live Search has been demonstrated to boost conversion by up to 7%. Product Recommendations can add a further ~25% by personalising suggestions on real-time behaviour.

Content. Adobe Firefly and Adobe Express are integrated, so teams can generate on-brand copy, dynamic product descriptions and image variations inside their existing workflow. That turns A/B testing into a seconds job rather than an hours job.

Scale and B2B

ACaaS supports catalogues of up to 250 million SKUs and around 30,000 unique price points per SKU. If you have ever had to explain to a finance team why a contract price list broke the catalogue, those two numbers will mean something to you.

The B2B functionality stays fully integrated: company accounts with custom roles, shared catalogues and pricing, and full quote negotiation. B2B, B2C and D2C run from a single instance.

What this means for you

ACaaS trades control for operating cost. You stop owning the upgrade cycle and the infrastructure, and in exchange you accept Adobe's release cadence and its constraints. For most merchants that is a good trade, because the upgrade cycle was never where the value was. For heavily customised builds tied into legacy systems, it is a conversation about what gets refactored first.

If you want to work out which of those you are, we are happy to go through it with you.