Magento Open Source vs Adobe Commerce: what the licence actually adds
The comparison shows that Adobe Commerce chiefly adds commercially supported tools for B2B, content, audiences and operations, while Magento Open Source retains the shared core.
Same Magento core, different commercial envelope
Magento Open Source and Adobe Commerce share the Magento codebase. That is the useful starting point: a choice between the editions is not a choice between two unrelated storefront platforms, and most of the underlying catalogue, checkout, customer-account and administration framework remains recognisable.
The difference is what surrounds that core. Adobe Commerce is the licensed edition. Magento Open Source is free to download, while Adobe Commerce requires a licence and adds commercially packaged modules, content tools and an Adobe support entitlement. Adobe acquired Magento in 2018, but the open-source project continued alongside the commercial edition.
This distinction matters when a licence comparison starts with feature tick boxes. The sensible question is not whether Adobe Commerce contains more screens. It is which additional capabilities would otherwise have to be built, bought, maintained or abandoned.
What the Adobe Commerce licence actually adds
| Area | What the licensed edition adds | What it saves the merchant from doing |
|---|---|---|
| B2B commerce | Company accounts, requisition lists and quoting | Building organisational customer structures, purchasing workflows and negotiated-order handling from scratch |
| Content production | Page Builder | Depending on a developer to turn page specifications into storefront layouts |
| Customer audiences | Customer segmentation and targeted content | Assembling rules, content variations and administrative controls without dedicated tooling |
| Content operations | Staging and preview | Creating a safe route for content changes before they reach the live storefront |
| Support | Adobe support within the applicable release and entitlement terms | Relying entirely on an agency, developer or hosting provider for Magento-specific support |
These are distinct from the ability to customise the open-source edition. Magento Open Source can be extended and a capable team can reproduce many of these outcomes. The commercial question is whether that work would cost more than the licence, deliver a more dependable result, or occupy people who should be doing other work.
It is also distinct from an extension purchase. An extension can solve a narrow requirement without carrying the wider Adobe Commerce licence, while the licensed edition provides a commercially supported package for organisations that need several of its capabilities together.
B2B: who needs the module and who merely thinks they do
The B2B module has a habit of attracting attention because “B2B” sounds enterprise-level. The relevant test is not the size of a company or the wholesale ambitions of the business. It is whether the buying process departs materially from a consumer checking out an account.
Company accounts are useful when customers need a shared organisational identity, designated buyers and purchasing roles. Requisition lists matter when employees need to assemble an order for approval or for another person to buy. Quoting becomes relevant when orders require negotiated terms, a formal quote or a sales process that cannot be reduced to a basket and payment.
That combination commonly justifies the module when several departments buy from the same merchant, administrators need to manage purchasing limits and account hierarchies, or most orders require intervention by a sales or credit-control function. The expense is not the label on the module. It is the operational complexity surrounding the order.
A merchant with occasional trade buyers may need none of it. If a buyer can place a normal order against a customer account, the handful of exceptions can be handled through ordinary account and pricing tools, or a narrow extension, the full B2B workflow may add administration without removing any meaningful work.
The practical test is to list the exceptions before buying the module. How often must price, approval, buyer identity or payment terms vary? Who is allowed to approve an order? Can a quotation contain the commercial terms the customer expects? If the answers describe a few rare cases, bespoke configuration may be more proportionate.
If exceptions are routine, involve multiple roles and must remain traceable, building the equivalent workflow in Magento Open Source becomes a substantial data-modelling and maintenance project. At that point, the B2B module is not a decorative badge for a wholesale store. It is a packaged answer to a recurring operational problem.
The other licensed tools have a narrower, clearer purpose
Page Builder changes who can produce layouts. A developer is no longer the only route from a design brief to a storefront page, although developers remain relevant for advanced components, data sources and integrations. Its value is greatest where merchandising teams need to publish and revise pages without waiting for development capacity.
Customer segmentation and targeted content make audience rules part of the content operation. They help merchants serve different groups with relevant messages, offers and experiences rather than maintaining every variation manually. The test is whether the business has meaningful audience differences and enough content variation to justify managing them.
Staging and preview address a familiar failure mode: a content change looks harmless in the administration system but breaks a live page, navigation rule or purchase journey. A staging route provides separation between preparation and publication; preview provides a closer view before release. Merchants with frequent campaigns, fragmented content ownership or a history of accidental publication gain more from this than those publishing a small, stable catalogue.
These tools should not be confused with an automated content strategy. They give merchants the means to create, target and rehearse content. Deciding what to publish, maintaining content quality and preventing business rules from decaying remain operational work.
Cost the licence against the alternative, not against zero
Adobe does not publish list pricing for Adobe Commerce. Any licence figure encountered elsewhere is either an estimate or a quotation from a seller. That does not make comparison impossible, but it changes what should be compared.
Start with the actual quote for the required scope, then compare it with the work avoided. The alternative is not simply “free Magento Open Source”. It is free Magento Open Source plus development, extension costs, maintenance, testing and the time taken to release changes safely.
Bespoke B2B work is particularly easy to underestimate. The visible forms are only part of it. Underneath sit permissions, company structures, account ownership, approval states, quote records, price relationships, administration and exception handling. Each feature also has to survive Magento upgrades and changes in surrounding integrations.
Include salary cost when evaluating that work. A developer assigned to internal B2B functionality cannot work on performance, conversion, integrations or the next release. A capable operations person managing approval and quoting by hand cannot focus on a process the system should handle. The relevant comparison is therefore licence cost against avoidable labour and delayed delivery, not licence cost against a monthly fee in isolation.
Then price the risk of maintaining a custom implementation. An internal team may produce a better fit than a packaged module, but it also carries the cost of documenting that knowledge, testing it, supporting it after staff changes and keeping it compatible with supported releases.
Support is a release entitlement, not an unlimited promise
Adobe support is one of the clearest differences between the editions, but its dates need reading precisely. At the 13 November 2026 check, Magento Open Source and Adobe Commerce had a current general release of 2.4.9, released on 12 May 2026. The 2.4.10-alpha1 build appeared on 13 October 2026, but it was a pre-release and not suitable for production.
The listed support position for the relevant releases was:
| Release | Regular support | Extended support |
|---|---|---|
| 2.4.9 | To 31 May 2029 | None listed |
| 2.4.8 | To 31 May 2028 | None listed |
| 2.4.7 | To 31 May 2027 | To 31 May 2028 |
| 2.4.6 | Ended 11 August 2026 | No current extension listed |
A release window is not the same thing as a lifetime of support for a store. It tells the merchant how long Adobe lists regular support for that release, with the additional extended window shown for 2.4.7. Licence and support terms still need to be checked for the specific agreement, but the version dates provide the essential planning boundary.
Magento Open Source merchants can obtain excellent support from agencies, specialist developers or hosting providers. What the commercial entitlement adds is access to Adobe’s own support route for the covered release and agreement. That may be decisive for a merchant without an experienced Magento team, particularly one operating across a complex catalogue or custom modules.
It may be redundant for a merchant whose internal developers already handle Magento issues and whose agency includes Magento support in its service. Paying for the same operational knowledge twice is not automatically value. The test is whether Adobe support provides capabilities, accountability or coverage the existing arrangement genuinely lacks.
For merchants still on Magento 1, there is no modern support bridge to preserve. Magento 1 reached end of life on 30 June 2020. Any current requirement must be assessed as a migration and replatforming decision, not as an extension of the old platform’s support.
The licence does not solve the surrounding platform
Choosing Adobe Commerce does not make unsupported infrastructure supported. For 2.4.9 on-premises installations, Adobe lists only these supported combinations:
- PHP 8.5
- MariaDB 12.3 or MySQL 8.4
- OpenSearch 3
- Valkey 9 for cache and sessions
- RabbitMQ 4.3
- Composer 2.10
Elasticsearch and Redis are not listed as supported for 2.4.9. A store carrying either from an earlier release cannot treat the upgrade as a routine application update. The search, cache and session layers need to be assessed separately, whether the merchant chooses Magento Open Source or Adobe Commerce.
The front end is another boundary. Luma remains the default Magento storefront theme, built with LESS, Knockout.js and RequireJS, with Blank as its parent theme. Hyvä is built with Tailwind CSS and Alpine.js instead. Hyvä became free and open source on 10 November 2025, although Hyvä Checkout, Hyvä Commerce and Hyvä Enterprise remain separate paid products.
Neither edition’s licence automatically supplies a front-end rebuild or headless implementation. PWA Studio is Adobe’s React-based headless storefront toolkit, but adopting it is a separate architectural project with its own integration and maintenance demands. The commercial edition can remove barriers; it cannot remove the work. front-end and speed
Which edition deserves the licence?
Adobe Commerce earns its place when several commercial capabilities apply at once. A retailer with genuine company buying, requisitions and quoting needs the B2B module. A merchant with frequent content production needs better publishing tools. A team without reliable Magento support gains value from an Adobe entitlement. A business considering a large internal build can use the licence quote as a disciplined ceiling against that investment.
Magento Open Source remains the rational choice when those needs are narrow or uncertain. It is also rational for teams with the skill and capacity to own the work they need. The free download removes licence cost, but it does not remove hosting, extensions, development, upgrades, security or operational responsibility.
The best comparison is therefore not feature count. It is the cost of the licence plus implementation and support, weighed against the cost and risk of the work that would otherwise be funded internally. Adobe’s lack of published list pricing makes that comparison less comfortable, but not less necessary.
Ask for a written quotation, define the editions and support terms in it, and compare those costs with the actual people, hours and release delays required by the alternative. If the licensed route replaces a programme rather than merely adding convenience, it may be justified. If it mainly puts a familiar set of Magento features behind a licence fee, Magento Open Source may already provide enough. platform choices
Questions this page answers
- Is Magento owned by Adobe?
- Adobe acquired Magento in 2018, but the open-source project continued alongside the commercial edition.
- Is Magento 2 free?
- Magento Open Source is free to download, while Adobe Commerce requires a licence and adds commercially packaged modules, content tools and an Adobe support entitlement.
- How much does Magento cost?
- Adobe does not publish list pricing for Adobe Commerce. Any licence figure encountered elsewhere is either an estimate or a quotation from a seller.
- Is Magento now Adobe Commerce?
- No. Magento Open Source and Adobe Commerce share the Magento codebase; Adobe Commerce is the licensed edition, while Magento Open Source is free to download.