Adobe Commerce as a Cloud Service: what changes

Adobe has announced Adobe Commerce (Magento) as a Cloud Service: the platform run for you, rather than something you host and maintain yourself. Below is what is actually in it, and what we would want a client to understand before it changes any plan.

Scale without the maintenance overhead

The pitch is large catalogues, high traffic and complex operations handled by the platform rather than by your team. That is the part most merchants care about, because it is the part they currently pay for in engineering time — capacity planning, cache tuning, and the periodic scramble before a peak trading window.

Faster updates, and less of your time in them

Services stay current on their own. If you have ever budgeted a fortnight to move between patch versions, that is the line item this is aimed at. It does not remove the need to keep the platform healthy, but it moves a large part of that work from your roadmap to Adobe's.

AI merchandising and testing, built in

AI-driven merchandising and A/B testing come as part of the platform rather than as integrations you assemble. The Adobe pieces are designed to fit together, which is a meaningful difference if you have spent time wiring analytics, targeting and commerce into something coherent.

Worth saying plainly: built-in is not the same as configured. Someone still has to decide what to test and what "better" means for your catalogue.

Migration at your own pace

You are not being asked to rebuild. Adobe's framing is incremental — adopt features as they suit you rather than committing to a single cutover. That matches how we approach replatforming anyway: the projects that go well are the ones that do not stake the business on one launch date.

What is not changing

The question we have been asked most: Magento Open Source and Adobe Commerce PaaS are staying. Cloud Service adds an option, it does not remove one. If you are on PaaS and it suits you, nothing here forces a move.

What we think

This is the right direction, and the detail will matter more than the announcement. Managed platforms trade control for convenience, and the honest question is which parts of that control you were actually using. For a merchant with heavy customisation and a team that knows the infrastructure, the trade is genuinely arguable. For one paying an agency to babysit servers, it is not.

We will have more to say once we have run real builds on it. Adobe has since launched the service in the Americas and EMEA, and set out the versionless model behind it.

If you are mapping out the next few years on Adobe Commerce, this belongs on the whiteboard. Let's talk about where it fits.