Leaving Adobe Commerce: What Mage-OS Doesn't Replace

We've made the case for Mage-OS elsewhere, and it holds up for stores already on Magento Open Source. This is the other half of it, written for the merchant on Adobe Commerce looking at a renewal quote and wondering whether the community distribution is a way out.

Mage-OS forks Magento Open Source. It does not fork Adobe Commerce. Everything you're paying Adobe for that isn't in Open Source is yours to replace, and Adobe is unusually clear about where that line falls — its documentation puts a badge on the exclusive features reading "This is an exclusive feature that is available only in Adobe Commerce and is not available in Magento Open Source."

The features with no equivalent

Mage-OS 3.0 moved two items across that line: it now bundles a returns module and an admin activity log, and we confirmed Adobe's exclusivity badge on both of those capabilities. That's the good news, and it's where the good news stops.

Still on Adobe's side, and confirmed against that same badge: Content Staging and Preview, and reward points and loyalty programs. Adobe's wider Commerce feature set also covers customer segments, store credit, gift registry, visual merchandising and rule-based product relations — we're listing those from Adobe's edition documentation generally, having checked the badge directly only on the features named above.

Replacement work for these splits three ways, and you should know which you're signing up for. Some have decent third-party extensions. Some need custom development. And for some the answer is to change how you operate, which is usually cheapest.

B2B is the one that sinks projects

Adobe lists B2B as an Adobe Commerce extension. What that covers, in Adobe's own terms: company accounts with structured roles and permissions, shared catalogs with tiered pricing, negotiable quotes, requisition lists, and company credit with pay-on-account.

Read that list against how your customers actually buy. If a purchasing manager logs in, sees contract pricing, builds a requisition list, requests a quote and pays on account, you aren't replacing a module. You're rebuilding a sales process your customers have already learned, and they will notice. Third-party extensions cover parts of the surface. The gaps tend to be the account hierarchy and the quote workflow, which are exactly the parts your largest customers touch daily.

This is where "we'll rebuild it" turns into the entire budget. Scope it first, before anything else in the plan.

The services that don't come with you

Adobe's product availability documentation lists Live Search and Product Recommendations for Adobe Commerce only. Both are separately licensed, both are AI-driven, and both are the sort of thing that quietly carries a chunk of your conversion rate.

One genuine carve-out that most comparisons get wrong: Payment Services is listed for both Adobe Commerce and Magento Open Source. If you're on it, it comes with you.

If you're replacing Live Search, price a third-party search product and its ongoing license into the comparison. Falling back to stock catalog search is also an option, and it needs to be a decision somebody actually makes.

Infrastructure is the item people forget

Adobe Commerce Cloud bundles managed AWS infrastructure, Fastly as CDN and web application firewall, and New Relic for application and infrastructure monitoring. Adobe's documentation notes that enabling the WAF is what allows production storefronts to meet the PCI DSS 6.6 requirement.

Self-hosted, every one of those becomes a line you procure, configure, operate and monitor. So does capacity planning for your peak. So does your PCI scope and the evidence behind it, which shifts from something you inherit to something you produce.

None of this is exotic. Plenty of large Magento stores have run themselves well for years and we help teams do exactly that. What goes wrong is the arithmetic: a business case that counted the license saving and left out the hosting bill, the monitoring, and the person who now owns uptime.

There's nobody to call

No SLA. No escalation path at 2am. No account manager, no vendor contract, no indemnification, and nobody to complete the security questionnaire your enterprise customer sends every year.

Mage-OS is a nonprofit association in Poznań with an elected board and publicly tracked finances, funded by memberships and donations. That's real transparency and a real organization. It is not a commercial counterparty, and it doesn't pretend to be.

For a business with an agency it trusts and an internal team that knows the store, this describes the arrangement they effectively had anyway — Adobe's SLA covers Adobe's platform, not your custom checkout. For a business whose procurement or compliance function requires a named vendor on a contract, this is where the conversation ends, and it's better to find that out in week one than after the technical plan is signed off.

One more operational difference

Mage-OS supports only its latest release for security patches. Adobe gives each release line a three-year standard support window.

That flips the maintenance model. On Adobe you can park on 2.4.8 until May 2028 and take patches; on Mage-OS you upgrade at their cadence, roughly twice a year plus security releases. Teams with a working deployment pipeline barely notice. Teams that defer upgrades for eighteen months at a time have a pipeline problem to fix first.

What you keep

A few of these get listed as losses by people selling against the move, so they're worth stating plainly.

Page Builder has shipped in Magento Open Source since 2.4.3 and is the default content editor in both editions. Inventory Management, Braintree, Google reCAPTCHA and two-factor authentication are all there. Payment Services carries over. Your database, catalog structure, theme, integrations and the entire Magento 2 extension ecosystem are unaffected, because this is the same code base underneath.

How to actually decide this

Auditing beats estimating, and the audit isn't expensive. Pull the module list from production and mark every Commerce-only module that's enabled — then go and check whether it's actually used, because enabled and used are different things. How many customer segments are live? How many staged updates went out last year? How many quotes last quarter? I've seen teams surprised in both directions by those three questions.

If B2B is in play at all, scope it on its own and scope it first, because it decides the size of everything else. Price the infrastructure properly, CDN and WAF and monitoring and the hours someone will spend on it, against your actual renewal quote and not a remembered one. And ask procurement and compliance early whether a supplier with no contract behind it is acceptable to them. That last one is a yes or no that can save you the whole exercise, and it's the question I'd ask first if I only got one.

Plenty of stores pay for Adobe Commerce and use very little of it; for those, the numbers can work comfortably. Plenty of others are paying for precisely the things that would take a year to rebuild. Two weeks of audit against a six-figure decision is not a close call.

And if the audit says stay, that's a real answer. The maintenance disciplines that make Magento work well are the same either way.

Emyrix works across Adobe Commerce, Magento Open Source and Mage-OS, including the usage audits that decide whether a distribution change makes sense. We have no commercial relationship with the Mage-OS Association and we don't resell Adobe licenses. If you want yours looked at, get in touch.

Feature exclusivity wording and service availability are from Adobe's own product documentation; association details are from mage-os.org. Where we've quoted the exclusivity badge we checked the page directly, and we've said so where we haven't.