Feature comparison

Adobe Commerce offers three deployment models:

This comparison focuses on the differences between software-as-a-service (SaaS) and platform-as-a-service (PaaS) models. These models provide different levels of customization, extensibility, and control over your Commerce implementation.

NOTE
The on-premises model shares similar capabilities with the PaaS model, so this comparison also applies when considering SaaS versus on-premises implementations.

Store management features

The Commerce Admin UI is the primary interface for accessing features to manage backend store operations, inventory, pricing, promotions, and customer interactions. However, Adobe Commerce as a Cloud Service offers unique solutions that replace some of the well-known features available in Adobe Commerce on Cloud and on-premises projects.

The following table describes the features and replacement solutions available in Adobe Commerce as a Cloud Service:

Feature
PaaS model [PaaS only]{class="badge informative" title="Applies to Adobe Commerce on Cloud projects (Adobe-managed PaaS infrastructure) and on-premises projects only."}
SaaS model [SaaS only]{class="badge positive" title="Applies to Adobe Commerce as a Cloud Service and Adobe Commerce Optimizer projects only (Adobe-managed SaaS infrastructure)."}
Digital asset management
Media Gallery
Product Visuals
Content management
Content Management System (CMS), Page Builder, URL rewrites
Storefront Builder
Catalog merchandising
Content staging, Visual Merchandiser
Catalog Service
Payments
Payment solutions
Payment Services
B2B functionality
Full B2B capabilities available after installation
Pre-installed with core B2B features1
Experimentation
Add-on for certain tiers
Native A/B testing to optimize engagement and conversion
1 Core B2B features, like company management and quoting, are available out-of-the-box in SaaS. However, industry-specific customizations may require additional implementation considerations.

Extensibility and platform features

The following table compares platform capabilities and extensibility features to help you understand the differences and decide which model best suits your business requirements before starting an implementation.

Feature
PaaS model [PaaS only]{class="badge informative" title="Applies to Adobe Commerce on Cloud projects (Adobe-managed PaaS infrastructure) and on-premises projects only."}
SaaS model [SaaS only]{class="badge positive" title="Applies to Adobe Commerce as a Cloud Service and Adobe Commerce Optimizer projects only (Adobe-managed SaaS infrastructure)."}
Platform capabilities
Feature and security updates
Requires manual upgrade and patching. Six patch releases and one minor release per year.
Automatically upgraded by Adobe through a versionless SaaS model
Hosting infrastructure
Single-tenant
Multi-tenant
Performance and scalability
Horizontal auto-scaling for scaled architecture. Vertical auto-scaling for web tier being rolled out in early access for all merchants including non-scaled architecture.
Multi-tenant cloud-native application with full auto-scaling across the stack
Observability
New Relic access for customers to monitor and manage environment
Adobe managed. Customers can use OpenTelemetry for App Builder apps and RUM dashboards for storefront. New Relic license not included. Customers can configure API Mesh and App Builder to send data to their own New Relic account.
CDN
Fastly included
Fully managed Edge CDN tightly coupled with Commerce Storefront. BYO-CDN also supported.
Security and compliance
SOC2, PCI, ISO certifications per hosting provider, HIPAA
SOC2, PCI, ISO, GDPR. HIPAA currently not available.
Disaster recovery and SLAs
99.99% infrastructure, 99.9% application (Managed Services)
99.9% (infrastructure and application), faster RPO/RTO
Hosting regions
Azure (24 locations), AWS (22 locations), GCP (8 locations, not standard)
Globally available. For information on production environments in your region contact your customer service representative. Additional locations rolled out based on demand.
Commerce Admin customization
Admin console extensibility
PHP customization and theming, App Builder extensibility (recommended)
App Builder extensibility
Extensibility
Extensibility model
In-process (PHP customization) and out-of-process (Recommended:APIs, events, App Builder)
Out-of-process only (APIs, events, App Builder)
Extensible web APIs
Native REST/GraphQL extensibility and API Mesh with custom resolvers
API Mesh with custom resolvers
Data model extensibility
Complete data model customization
Custom attributes for core and B2B entities1
Technologies
CSS, CLI, HTML, JS, PHP, XML
CSS, CLI, HTML, JS, Node
App marketplace
[Magento Marketplace](https://marketplace.magento.com/) (PHP extensions) and [Exchange Marketplace](https://commercemarketplace.adobe.com) for App Builder apps (Recommended)
App Builder apps from [Exchange Marketplace](https://commercemarketplace.adobe.com)
Data & storage
Search index customizations
Native search customization
Requires third-party solutions
Custom email types
Full email customization
Standard email templates only
Custom data storage
DB, file, cache, queue
App Builder state library (file only)2 - Database Storage for App Builder is currently in Early Access.
1 Data model extensibility in SaaS supports extending core entities beyond product and customer, including B2B entities. However, industry-specific data models (for example, dealer-specific attributes) could require additional architectural considerations.

2 Adobe is actively working Document DB integration to address persistent storage needs for SaaS. Currently, implementations requiring long-term data storage may need to provision and maintain additional infrastructure.
NOTE
When considering migration to SaaS, Adobe recommends that you:
  • Move suitable functionality to out-of-process extensibility where possible.
  • Reduce the surface area that requires transition.
  • Consider API Mesh for extending API functionality.
  • Monitor Adobe’s ongoing platform evolution and new capability releases.
  • Evaluate industry-specific data model requirements against available extensibility options.
  • Consider adopting Merchandising Services powered by Catalog Views and Policies.
recommendation-more-help
5ecfe1a6-f74c-4745-a54a-99b24da024bb