Adobe Commerce SaaS vs PaaS, On-Premise and Optimizer: 2026 Decision Guide, category: Platform comparisons.

SHORT ANSWER

Adobe Commerce SaaS is Adobe Commerce as a Cloud Service (ACCS), a versionless platform. Adobe runs the application, and you extend it through APIs and App Builder only. PaaS (Adobe Commerce on Cloud) and on-premises keep full PHP control, but you must upgrade them. Optimizer adds a SaaS storefront to a backend you already run. Elogic Commerce matches the choice to your customization depth and your Cloud deadline.

Key takeaways

• Adobe sells four options: ACCS (SaaS), Adobe Commerce on Cloud (PaaS), Adobe Commerce on-premises and Adobe Commerce Optimizer (ACO). ACO is a SaaS layer over an existing backend. Adobe introduced ACCS and ACO in June 2025.
• On ACCS, all custom logic runs out of process through App Builder, events, webhooks and API Mesh. PHP modules, Luma themes and Magento Marketplace PHP extensions do not move over.
• From June 1, 2027, Adobe will suspend traffic to Cloud environments that still run 2.4.4 or 2.4.5. For 2.4.6 and 2.4.7, the date is June 1, 2028.
• The first Cloud dependency deadline is October 30, 2026, for MariaDB 10.5 or older, Elasticsearch and RabbitMQ 3.9 or older.
• The ACCS base license includes 250,000 SKUs, 1,000 catalog updates per minute (up to 100,000 per day), and one production and two sandbox environments. HIPAA is not currently available on SaaS.
• Adobe states that it has no end-of-support plans for PaaS. An upgrade to 2.4.8 or 2.4.9 is a valid path, but it does not stop future upgrade obligations.

This guide is for Adobe Commerce merchants who must select a deployment model before their next Cloud deadline. The Adobe Commerce development team at Elogic Commerce, whose Adobe partnership status is Adobe Commerce Silver Solution Partner, wrote it from Adobe’s current documentation, product descriptions and lifecycle policy.

What are the four Adobe Commerce deployment options in 2026?

Adobe Commerce has four deployment options: Adobe Commerce as a Cloud Service (SaaS), Adobe Commerce on Cloud (PaaS), Adobe Commerce on-premises and Adobe Commerce Optimizer. Optimizer adds a SaaS storefront and catalog layer to a backend that you already run. Elogic Commerce compares them by who upgrades, where custom code runs and what you must rebuild.

Table 1. Adobe Commerce deployment options compared. Sources: Adobe feature comparison, migration overview and product descriptions. Compiled by Elogic Commerce, September 2026.

Adobe calls ACCS the recommended long-term destination for all Adobe Commerce on Cloud customers. In March 2026, Adobe also stated that it has no end-of-support or end-of-life plans for Adobe Commerce on Cloud. Both statements are true at the same time: PaaS stays, but its upgrade obligations stay too.

In this guide, “on-premises” means any self-hosted Adobe Commerce installation. Many teams call it “on-premise”.

What is Adobe Commerce SaaS (Adobe Commerce as a Cloud Service)?

Adobe Commerce as a Cloud Service is the SaaS edition of Adobe Commerce. Adobe manages the core application, infrastructure, security patches and upgrades, and you cannot change the core code. You extend it with App Builder, API Mesh, events, webhooks and the Admin UI SDK, and you sell through the Edge Delivery Services storefront. Elogic Commerce calls it the no-upgrade option.

• Updates. Adobe sends in-app notices for new releases. You get 30 days to test them in a sandbox before Adobe applies them to production. Adobe guarantees backward compatibility for customizations that follow the API-first extensibility model.
• Availability. Adobe states 99.9% availability. One instance supports B2B and B2C, several brands and several regions.
• Environments. The base license includes one production and two sandbox environments. Sandboxes are available only in North America, and you cannot change the region of an instance after you create it.
• Included services. Commerce Admin, the EDS storefront, Catalog Service, Live Search, Product Recommendations, Payment Services and Product Visuals powered by AEM Assets.
• B2B. Core B2B features, such as company management and quotes, come pre-installed.
• Not supported. Luma storefronts, in-process PHP customization, Magento Marketplace PHP extensions, native search index customization, custom email types and HIPAA.

For the frontend side of this choice, see our guide to headless Adobe Commerce.

How do SaaS and PaaS compare, feature by feature?

PaaS gives you full control: PHP code, a custom data model, native search tuning, full email customization and HIPAA. SaaS removes upgrades and infrastructure work, but it limits you to out-of-process extensions, custom attributes, standard email templates and third-party search tuning. Elogic Commerce recommends that you map each gap to an App Builder app or a managed service before you commit to a migration.

Table 2. Adobe Commerce SaaS vs PaaS. Source: Adobe “Feature comparison”, updated September 11, 2026. Compiled by Elogic Commerce.

One row has a direct SEO effect. On SaaS, Storefront Builder replaces the Admin CMS, Page Builder and URL rewrites, and redirects move to the storefront layer. Edge Delivery Services allows up to 100,000 redirects per site and no wildcard rules, so plan the redirect map before the migration, not after.

What is Adobe Commerce App Builder?

Adobe Developer App Builder is Adobe’s serverless extensibility platform. On Adobe Commerce, it runs custom logic outside the core application and connects through events, webhooks and APIs. On SaaS, it is the only way to extend Commerce. Elogic Commerce recommends that you scope App Builder work first in an ACCS migration plan, because Adobe calls it typically the most significant engineering effort.

App Builder for Adobe Commerce has these main parts:

• Adobe I/O Runtime for serverless actions.
• API Mesh, which combines several APIs into one GraphQL endpoint.
• Adobe I/O Events and Commerce webhooks, which react to Commerce events or change a process in real time.
• The Admin UI SDK, which adds pages and menus to the Commerce Admin.
• Starter kits for integrations and for checkout, including out-of-process payment and shipping methods.
• App Builder Database, in early access, for custom data.

Table 3. App Builder entitlements per pack. Source: Adobe Developer App Builder product description, effective March 9, 2026.

Adobe adds App Builder packs automatically for Adobe Commerce on Cloud customers. Self-hosted customers can buy packs. For ACCS, your Sales Order sets the number of packs, and Adobe configures App Builder with each instance. Adobe does not offer App Builder trials.

Table 4. What replaces in-process PHP on SaaS. Elogic Commerce mapping based on Adobe extensibility documentation.

Most rows in this table are rebuilds of existing modules, so treat them as Magento extension development, not as configuration. The ERP and PIM rows are systems integration work and need the same testing as the original integration project.

What limits apply to Adobe Commerce SaaS and Optimizer?

The ACCS base license includes 250,000 SKUs, 100 catalog variations, and 1,000 catalog updates per minute, up to 100,000 per day. It also includes one production and two sandbox environments and 1 TB of storefront storage. Optimizer adds hard ceilings such as 50 catalog sources and 10,000 variants per product. Elogic Commerce recommends that you test these numbers against your peak catalog updates.

Table 5. Base limits of ACCS and ACO. Sources: Adobe product descriptions (effective October 13, 2025) and ACO limits and boundaries. Compiled by Elogic Commerce.

Note 1: Adobe’s product descriptions list SKU packs of 10,000 SKUs, and the Optimizer limits page lists packs of 100,000 SKUs. Confirm the pack size in your Sales Order. Note 2: The Optimizer limits page documents 500,000 updates per day for the 5K pack and 1 million per day for the 10K pack. The ACCS product description lists the same pack names.

Two licensing details surprise many teams. First, one storefront content request is one page view or five API calls, and JSON calls from a headless frontend count. Second, if you use your own CDN, you must send Adobe an auditable usage report every six months. Without the report, Adobe can calculate usage from origin logs with an assumed 95% cache rate.

What does the June 1, 2027 Cloud enforcement mean?

From June 1, 2027, Adobe will stop maintaining Adobe Commerce on Cloud environments that run unsupported versions. Adobe will suspend their traffic, so the storefront goes offline, and it can then decommission the environment and delete its data. Stores on 2.4.4 or 2.4.5 must upgrade or move to SaaS by that date. Elogic Commerce advises Cloud merchants to start now.

Table 6. Adobe Commerce lifecycle and Cloud enforcement dates. Source: Adobe Commerce lifecycle policy, updated September 18, 2026.

Table 7. Cloud dependency deadlines. Source: Adobe “Required actions and deadlines to secure Commerce environments”, updated September 18, 2026.

• Adobe upgrades these services for you through a support ticket. Open the ticket at least 30 days before your deadline.
• Elasticsearch to OpenSearch and Redis to Valkey are changes of software, not version upgrades. Custom code and extensions can need changes.
• PHP 8.2 reaches end of life on December 31, 2026. Adobe flags a PCI compliance risk for stores that stay on it.
• The enforcement applies to Adobe Commerce on Cloud versions 2.4.4 to 2.4.9. It does not apply to ACCS or to on-premises deployments.
• If a Cloud environment stays non-compliant after traffic suspension, Adobe may terminate the service. Decommissioning deletes all data, environments and branches permanently.

Track your own dates in the Commerce Platform Upgrade Risk Tracker. The What Is Magento guide explains the editions and the enforcement policy in more detail. If you only need the upgrade, a Magento support and maintenance retainer covers the 2.4.9 upgrade, security patches and the dependency tickets.

Should you upgrade PaaS or move to SaaS?

Upgrade PaaS to 2.4.9 if your checkout, pricing or data model depends on PHP modules, or if you need HIPAA. Move to SaaS if your custom logic already runs through APIs and you want to stop upgrade projects. The Elogic Commerce SaaS Readiness Score below turns this decision into ten yes-or-no questions.

An upgrade to 2.4.9 resets the clock but does not stop it. Standard support for 2.4.9 ends on May 31, 2029.

Elogic Commerce SaaS Readiness Score

Answer each question. Give one point for each “yes”.

Table 8. Elogic Commerce SaaS Readiness Score (10 questions).

Read your score:

• 8 to 10: SaaS-ready. Plan the ACCS migration and start with Adobe’s Migration Assessment Tool.
• 4 to 7: Hybrid. Upgrade PaaS to 2.4.9 now, add Optimizer for the storefront and move logic to App Builder over time. Calculate the score again in 12 months.
• 0 to 3: Stay on PaaS or on-premises. Upgrade to 2.4.9 and reduce in-process PHP code before the next release line.

If the answers are unclear, an Adobe Commerce (Magento) consulting engagement or a Magento code audit gives you the module inventory that the questions need. To check team capacity for the deadline, use the Capacity Gap Assessment.

What is Adobe Commerce Optimizer, and when does it make sense?

Adobe Commerce Optimizer is a SaaS layer on top of a commerce backend that you already run. It adds an Edge Delivery Services storefront, Catalog Service, Live Search, Product Recommendations and catalog views. It makes sense when the storefront is the problem and the backend is healthy, because checkout stays where it is. Elogic Commerce sees it as the lowest-risk first step toward SaaS.

• Connector. The Adobe Commerce Optimizer Connector syncs catalog and pricing from Adobe Commerce on Cloud or on-premises, and Adobe Commerce stays the system of record. The base rate is up to 1,000 products and 50,000 prices per minute. The connector sends feeds in one thread, and the ingestion API accepts up to two requests per second.
• Other backends. A Commerce Salesforce Connector, built on App Builder, syncs Salesforce Commerce Cloud B2C catalog and price data into Optimizer. The Data Ingestion API accepts catalog data from any source, and you can connect a third-party cart and checkout through API Mesh and App Builder.
• Catalog model. Catalog views and policies replace the website, store and store view model. This helps multi-brand, multi-region and dealer-specific catalogs.
• Headless option. The Optimizer Headless package leaves out the EDS storefront, so you can use your own frontend.
• Pricing and B2B. Optimizer is priced by GMV tiers, and you report your GMV to Adobe each year. On PaaS, B2B drop-ins need the Storefront Compatibility B2B Package, so confirm the B2B scope with Adobe before you sign.

Elogic Commerce expects most storefront work on Optimizer to carry forward to ACCS, because both use the same storefront and merchandising services. The connector setup does not carry forward. For a storefront-first plan, see our headless ecommerce development service.

When does on-premises still make sense?

On-premises fits when you must control the infrastructure, the data location or the network access. It also fits when your customization goes deeper than any managed option allows. You carry hosting, patching, dependency upgrades and PCI scope. The June 1, 2027 enforcement does not apply to on-premises, but Adobe’s lifecycle dates do. Elogic Commerce recommends it only with a named owner for patching.

• Adobe Commerce on-premises. Licensed by a pricing level (GMV, AOV or order limit) in the Sales Order. You get Adobe Commerce features such as B2B, content staging and the GraphQL Application Server.
• Magento Open Source. No license fee and the same release lines. Adobe’s extended support provisions are for Adobe Commerce customers only.
• Mage-OS. A community distribution of Magento Open Source. Mage-OS 3.2.0 (July 14, 2026) tracks Magento Open Source 2.4.9 and includes Adobe’s isolated security patch from July 2026.

If an on-premises store carries years of unpatched custom code, start with ecommerce rescue and stabilization before you plan the upgrade.

What does a PaaS to SaaS migration involve?

A PaaS to SaaS migration rebuilds four areas. Customizations move to App Builder, and the storefront moves to Edge Delivery Services. Data moves through the Commerce Data Migration Service, and integrations move to SaaS patterns. Adobe starts each migration with an AI-assisted assessment. Elogic Commerce recommends that you add an SEO and URL plan, because URL rewrites and Luma pages do not carry over.

1. Assess. The Migration Assessment Tool makes an inventory of modules, extensions, integrations, database schema and custom tables. It maps each capability to an ACCS equivalent and scores the complexity.
2. Modernize the application and migrate data. The Commerce Developer Agent and the Commerce Developer MCP turn the approved plan into App Builder scaffolding. The Commerce Data Migration Service extracts, loads and verifies the core catalog, customer and order data.
3. Modernize the storefront. Rebuild it on Edge Delivery Services with the boilerplate, drop-ins and blocks.
4. Cut over and operate. Only the final data-moving stages need a maintenance window.

Adobe provides these migration tools at no cost. Data in custom tables from third-party extensions does not migrate automatically and needs custom tooling. Add these checks to the Adobe plan:

• A URL inventory and redirect map, because URL rewrites do not carry over.
• An email template review, because SaaS supports standard templates only.
• A search review, because native search index changes are not available.
• An observability setup: OpenTelemetry for App Builder apps, RUM for the storefront and your own New Relic account if you need it.
• A content request forecast for the storefront license.

In practice, a move to SaaS is a replatforming project, even though the product name stays the same.

Result example: for Zep, Elogic Commerce built an Adobe Commerce Cloud B2B platform with Epicor ERP integration. In the first year, 31% of B2B orders moved to digital channels, and manual order processing decreased by 27% (Zep case study).

How much does each Adobe Commerce option cost?

Adobe does not publish list prices for any edition. ACCS and Adobe Commerce licenses use GMV and AOV tiers or order limits in the Sales Order, and Optimizer uses GMV tiers. The real cost differences come from upgrades, infrastructure, add-on packs and rebuild effort. Elogic Commerce recommends a three-year total cost model for each option before you decide.

Table 9. Cost drivers by deployment option. Elogic Commerce analysis of Adobe product descriptions and the feature comparison, September 2026.

Use the Adobe Commerce Team Cost Calculator for the team line and our ecommerce development cost breakdown for the project line. If the deadline is close and your team is small, hire Magento developers for the upgrade window.

How Elogic Commerce helps

Elogic Commerce’s Adobe partnership status is Adobe Commerce Silver Solution Partner. The company has 200+ specialists and 500+ projects since 2009. Clients rate Elogic Commerce 5.0 across 64 Clutch reviews. Its compliance credentials are ISO 27001 · SOC 2 Type II · ISO 9001.

• Upgrade to 2.4.9 on PaaS, with the dependency tickets for October 30, 2026 and May 31, 2027.
• ACCS migration: assessment review, App Builder apps, the Edge Delivery Services storefront, data migration and SEO parity.
• Optimizer storefronts on an existing Adobe Commerce backend.
• Team extension for the upgrade window.

Result example: for Armacell, Elogic Commerce built a B2B self-service portal on Adobe Commerce with SAP S/4HANA and PIM integration. Order approvals became 5 times faster, and manual orders decreased by 40% (Armacell case study).

To test the options against your own store, start with a platform selection and architecture assessment.

PLAN YOUR 2027 CLOUD DEADLINE WITH ELOGIC COMMERCE

Sources and methodology

From September 20 to September 29, 2026, Elogic Commerce reviewed Adobe documentation, Adobe product descriptions, the Adobe Commerce lifecycle policy and vendor sources. Search data comes from Ahrefs (US, September 29, 2026). All dates in this article are absolute. Elogic Commerce reviews this page every quarter. Next review: December 15, 2026.

1. Adobe, “Feature comparison” (Adobe Commerce SaaS vs PaaS), updated September 11, 2026. https://experienceleague.adobe.com/en/docs/commerce/cloud-service/feature-comparison
2. Adobe, “Adobe Commerce as a Cloud Service overview”, updated September 11, 2026. https://experienceleague.adobe.com/en/docs/commerce/cloud-service/overview
3. Adobe, “Getting started” with Adobe Commerce as a Cloud Service, updated September 11, 2026. https://experienceleague.adobe.com/en/docs/commerce/cloud-service/getting-started
4. Adobe, “Migrate to Adobe Commerce as a Cloud Service”, updated September 24, 2026. https://experienceleague.adobe.com/en/docs/commerce/cloud-service/migration/overview
5. Adobe, “Adobe Commerce lifecycle policy”, updated September 18, 2026. https://experienceleague.adobe.com/en/docs/commerce-operations/release/planning/lifecycle-policy
6. Adobe, “Required actions and deadlines to secure Commerce environments”, updated September 18, 2026. https://experienceleague.adobe.com/en/docs/commerce-operations/release/planning/security-enforcement-policy
7. Adobe, “Adobe Commerce as a Cloud Service product description”, effective October 13, 2025. https://helpx.adobe.com/be_en/legal/product-descriptions/adobe-commerce-cloud-service.html
8. Adobe, “Adobe Commerce Optimizer product description”, effective October 13, 2025. https://helpx.adobe.com/legal/product-descriptions/adobe-commerce-optimizer.html
9. Adobe, “Adobe Commerce Optimizer limits and boundaries”. https://experienceleague.adobe.com/en/docs/commerce/optimizer/boundaries-limits
10. Adobe, “What is Adobe Commerce Optimizer?”. https://experienceleague.adobe.com/en/docs/commerce/optimizer/overview
11. Adobe, “Commerce Optimizer integrations”. https://experienceleague.adobe.com/en/docs/commerce/optimizer/integrations-overview
12. Adobe, “Estimate data volume and sync time”, Adobe Commerce Optimizer Connector. https://experienceleague.adobe.com/en/docs/commerce/aco-optimizer-connector/reference/estimate-data-volume-sync-time
13. Adobe, “Continued investment and support for Adobe Commerce on Cloud”, March 30, 2026. https://business.adobe.com/blog/continued-investment-support-adobe-commerce-on-cloud
14. Adobe, “Adobe Developer App Builder product description”, effective March 9, 2026. https://helpx.adobe.com/legal/product-descriptions/adobe-developer-app-builder.html
15. Adobe, “App Builder frequently asked questions”. https://developer.adobe.com/app-builder/docs/intro_and_overview/faq
16. Adobe, “Backend options”, Adobe Commerce Storefront, updated September 11, 2026. https://experienceleague.adobe.com/en/tools/commerce-storefront/get-started/backends/
17. Adobe, “SSR and crawlability” (Edge Delivery Services platform limits). https://experienceleague.adobe.com/en/tools/commerce-storefront/setup/seo/ssr-and-crawlability/
18. Adobe, “GraphQL Application Server”. https://experienceleague.adobe.com/en/docs/commerce-operations/performance-best-practices/concepts/application-server
19. Adobe, “Adobe Commerce 2.4.6 security patch release notes”. https://experienceleague.adobe.com/en/docs/commerce-operations/release/notes/security-patches/2-4-6-patches
20. Mage-OS, “3.2.0” release notes, July 14, 2026. https://github.com/mage-os/mageos-magento2/releases/tag/3.2.0
21. Elogic Commerce, Armacell and Zep case studies. https://elogic.co/projects/armacell/

About the author

Paul Okhrem is the CEO and Founder of Elogic Commerce and a member of the Forbes Technology Council. Under his leadership, Elogic Commerce received the Magento Community Engineering Award at Magento Imagine 2019.