Feature comparison
Adobe Commerce offers three deployment models:
- [SaaS only]{class="badge positive" title="Applies to Adobe Commerce as a Cloud Service and Adobe Commerce Optimizer projects only (Adobe-managed SaaS infrastructure)."} Adobe Commerce as a Cloud Service (SaaS)
- [PaaS only]{class="badge informative" title="Applies to Adobe Commerce on Cloud projects (Adobe-managed PaaS infrastructure) and on-premises projects only."} Adobe Commerce on Cloud (PaaS)
- Adobe Commerce (on-premises)
This comparison focuses on the differences between software-as-a-service (SaaS) and platform-as-a-service (PaaS) models, which 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:
Details
A robust digital asset management (DAM) system that integrates with Adobe Experience Manager for managing rich media content. Alternatively, the default digital file and asset management feature provides basic asset management tools for storing and managing digital assets.
A CMS allowing users to create and manage storefront content easily using document authoring or a Visual Editor and includes native experimentation capabilities.
A rich view-model (read-only) service for managing catalog data and rendering product-related storefront experiences.
An integrated payment service that facilitates secure and efficient transactions.
Extensibility and platform features
The following table compares platform capabilities and extensibility features to help you understand the differences and make an informed decision about which model best suits your business requirements before starting an implementation.
Feature
Platform capabilities
B2B functionality
Full B2B capabilities available after installation
Pre-installed with core B2B features1
Experimentation
Add-on for certain tiers
A/B testing to optimize engagement and conversion
Feature and security updates
Requires manual upgrade and patching
Automatically deployed
Hosting infrastructure
Single-tenant
Multi-tenant
Commerce Admin customization
Extensible core Admin screens
Complete layout and functionality customization
Preset filters, visibility controls
Extensible new Admin screens
Standard Admin UI integration and external app injection (Admin UI SDK)
External app injection (Admin UI SDK)
Customizable Admin theme
Extensible theming framework
No theming framework
Extensibility
Extensibility model
In-process (PHP customization) and out-of-process (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 entities2
Technologies
CSS, CLI, HTML, JS, PHP, XML
CSS, CLI, HTML, JS, Node
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)3
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.
2 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.
3 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.
2 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.
3 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