Adobe Commerce now comes in three options. Here's how to tell which one is yours.

The landscape has shifted

For a long time, "Adobe Commerce" meant one thing. You knew what you were getting: a powerful, enterprise-grade ecommerce platform built for businesses with complex needs. The conversation was usually about whether you needed it - not which version you should choose.

That's changed.

Adobe now offers three distinct Commerce options. If you've been researching Adobe Commerce lately, you've probably come across "SaaS" and "cloud service" more than once. This blog cuts through the jargon so you can make sense of the options - and figure out which one fits where your business is headed.

A quick orientation

Adobe Commerce is an ecommerce platform built for businesses with genuinely complex requirements: large or multi-brand catalogues, B2B capabilities, high customisation, and the kind of scale that outgrows a standard off-the-shelf setup.

Many of you will remember it as Magento. Adobe acquired Magento in 2018 and has been building on it since. What's changed recently is that Adobe has expanded the product into three options, each with a different model for how the platform is hosted, maintained, and extended.

The three options are not just different pricing tiers. They represent meaningfully different approaches to how your commerce platform lives in your organisation.

Option 1: Adobe Commerce on Cloud (PaaS)

This is the one most people mean when they say "Adobe Commerce." It's a Platform-as-a-Service model - Adobe provides the cloud infrastructure, and you (or your implementation partner) manage the application layer on top of it.

You have deep control over how the platform is configured, extended, and integrated with other systems. That control is its biggest strength. It's also where the complexity and the responsibility sit.

Upgrades, patches, and performance tuning are things your team plans and executes. The platform can be customised extensively - custom modules, third-party integrations, unique checkout flows, complex B2B pricing logic. If your commerce requirements are genuinely specific to how your business operates, PaaS gives you the room to build for that.

Well suited for businesses that:

• Have complex or unique commerce requirements that need custom development

• Have in-house technical capability or a reliable implementation partner for ongoing work

• Need deep control over integrations with existing ERP, PIM, or CRM systems

• Want flexibility over when and how platform upgrades are applied

PaaS is mature. It has a strong ecosystem of developers, extensions, and third-party integrations built up over years. Adobe has been clear this option isn't going away - it remains a core, fully supported product with a published long-term roadmap.

Option 2: Adobe Commerce as a Cloud Service (SaaS)

This is the newer model. It's a fully managed, cloud-native platform - Adobe handles the entire infrastructure, and updates happen automatically. You're always on the latest version without needing to plan, test, and execute upgrade cycles yourself.

The storefront uses a headless, decoupled architecture powered by Edge Delivery Services - fast performance and flexible front-end development. AI-powered merchandising tools like live search, product recommendations, and catalogue services are built in, along with generative AI tools for content creation and experimentation.

The trade-off is customisation. In a SaaS model, you work within the boundaries Adobe defines for how the platform can be extended. For businesses with deeply bespoke requirements, that's a real constraint. For businesses whose needs sit within what Adobe has built, it removes a meaningful maintenance burden and keeps total cost of ownership lower over time.

Well suited for businesses that:

• Want to reduce ongoing operational and development overhead

• Can work within a more standardised extensibility framework

• Are prioritising speed-to-market and access to the latest Adobe capabilities

• Don't have complex legacy customisations that would need to be rebuilt

One thing worth knowing: the SaaS ecosystem is still maturing. The range of third-party extensions, specialist developers, and proven integration patterns is growing - but PaaS has a significant head start. If your business relies heavily on specific third-party tools or customised workflows, it's worth investigating SaaS compatibility carefully before committing.

Option 3: Adobe Commerce Optimizer

This one tends to catch people off guard, because it isn't a full commerce platform.

Commerce Optimizer is a set of Adobe's front-end and merchandising capabilities - AI-powered search, product recommendations, a high-performance headless storefront - that sit on top of an existing commerce setup. The key detail: that existing setup doesn't have to be Adobe Commerce.

Optimizer is designed for businesses that already have a working commerce platform they're not ready or willing to replace, but who want to improve the customer experience without a full backend migration.

Well suited for businesses that:

• Are invested in an existing commerce platform and want to enhance it, not replace it

• Want to improve storefront performance, search quality, or conversion rates incrementally

• Are looking to access Adobe's AI merchandising capabilities without committing to a full platform rebuild

• Are exploring Adobe's ecosystem gradually before a larger future decision

How to think about the choice

No option is universally better. The right one depends on a few honest questions about your business.

How much do you need to customise? If your commerce requirements are genuinely complex - multi-region operations, intricate B2B pricing, deep integrations with existing business systems - PaaS gives you the flexibility to build for those needs. If your requirements are closer to standard, SaaS removes significant overhead without sacrificing what you actually need.

What does your internal team look like? PaaS requires ongoing technical investment. Someone needs to manage upgrades, monitor performance, and handle development as the business evolves. SaaS reduces that load considerably. If your team doesn't have strong in-house development capability, a platform that manages more of itself isn't a compromise - it's the right call.

Where are you in your commerce journey? A business five years into Adobe Commerce, with existing customisations and integrations, is in a very different position from one evaluating a platform for the first time. Optimizer makes most sense for the former. PaaS or SaaS is the conversation for the latter.

What does the next three years look like? A platform decision isn't just about where you are today. If you're expecting significant growth, new markets, or new sales channels in the near term, the scalability model matters. SaaS handles scale automatically. PaaS gives you more control, but requires more planning.

What we've seen

The conversations that tend to get complicated are the ones where the platform model was decided before the business requirements were properly mapped. It's easy to follow what's being promoted at any given moment. That doesn't mean it's wrong for you - it means the decision deserves more than a product pitch.

We've worked with businesses that underestimated the operational weight of PaaS - the upgrade cycles, the accumulating technical debt, the development overhead that comes with deep customisation. We've also seen businesses hesitate on SaaS because of customisation limits that, once examined properly, didn't actually affect what they needed to build.

Both are strong platforms in the right context. Getting to the right context requires asking the right questions first.

Not sure where you land?

We're an Adobe partner who works across Commerce implementations - you can read more about how we work with Adobe. If you'd like to think through the options for your specific situation, we're happy to have that conversation.

👉 Talk to us