Mage-OS 3: what we know, what we expect, what changes for merchants

1. Why Mage-OS

Quick context reminder for merchants who are discovering this. Mage-OS is a community fork of Magento Open Source, launched in late 2022 under the umbrella of an independent foundation (mage-os.org). Its raison d'être: guaranteeing a community-driven Magento independent of Adobe's commercial roadmap, without breaking compatibility with the existing ecosystem.

As of May 2026, Mage-OS 2.3.x is the latest public minor. It powers, among others, several B2B and DTC stores in Wallonia, Flanders, France and the Netherlands — including several Wimakeit clients.

Mage-OS 2 is intentionally drop-in compatible with Magento Open Source 2.4.x: a Magento store moves to Mage-OS via a simple composer.json tweak, no schema change, no module reinstall.

Mage-OS 3 marks the first intentional break.

2. The announced axes

PHP 8.4 minimum

Magento 2.4.7 supports PHP 8.1 / 8.2 / 8.3. Mage-OS 2.x follows the same line. Mage-OS 3 should require PHP 8.4 as a minimum, possibly targeting PHP 8.5 if the release agenda allows. Practical consequence: all third-party modules will have to support these newer PHP versions — which bring features (property hooks, asymmetric visibility) but also deprecations that break legacy code.

Removal of Adobe-specific code

Magento Open Source 2.4.x still contains several modules / classes that serve only in the Adobe Commerce context (analytics, residual content staging, Adobe ID integrations, certain AEM hooks). Mage-OS 3 aims to purge those dead blocks, which should reduce the codebase size by around 15-20% according to community estimates. Merchant impact: none.

Modernised GraphQL

The GraphQL layer of Magento 2.4 has aged — uneven performance, poorly documented schema, no subscriptions. Mage-OS 3 plans a major rework: migration to webonyx/graphql-php 15+, redesigned GraphQL cache, introspectable schema and strict output typing. Impact for merchants on headless / Hyvä React Checkout: expected change, to be anticipated on the front-end side.

Admin progressively de-jQuery'fied

The Magento 2 back-office is still heavily dependent on jQuery + RequireJS + Knockout.js — a 10+ year old tech stack. Mage-OS 3 would start the progressive migration to Alpine.js + Web Components for new admin screens, without breaking existing third-party modules.

Re-architected extension system

The current coupling between composer + Magento DI + setup-patches makes upgrades sometimes painful. Mage-OS 3 explores leads: formalised extension manifest, automatic detection of DI conflicts at build time, truly reversible install / upgrade / uninstall lifecycle. No final decision is public at this stage.

Performance

OPcache + JIT exploited more aggressively. Removal of unnecessary allocations in hot paths (catalog, checkout, search). Stated goal: 20% faster than an equivalent Magento 2.4.7 on standard B2C workloads.

3. The schedule (best case)

No date is officially set as of May 2026. Likely milestones:

• Q3 2026: stabilised RFC, first public alpha.
• Q4 2026 / Q1 2027: beta.
• 2027: Mage-OS 3.0 stable.

Mage-OS 2.x would continue to be maintained in parallel (security fixes, PHP compat) for at least 18 months after 3.0 ships. So merchants are in no hurry.

4. What this changes for a Magento merchant today

Nothing urgent

If you are on Magento Open Source 2.4.7 or Mage-OS 2.3.x, you have plenty of time. The Mage-OS 2 → Mage-OS 3 transition will happen as a classic major upgrade, with support overlap on both branches.

To audit right now

1. Old third-party modules — any extension not updated in 18 months is suspect. Check the module's repo for recent activity. If it's zero, plan a replacement or a fork.
2. PHP dependencies — your composer.json may pin libraries incompatible with PHP 8.4 (old Symfony, legacy Laminas, abandoned packages). A composer outdated --direct gives a first view.
3. Custom proprietary code — if you have custom code in app/code/{Vendor}/, run it through PHPStan level 8 + Rector PHP 8.4 right now. Incompatibilities will surface immediately, and they're 100x cheaper to fix preventively.

To avoid

• Migrating to Adobe Commerce now to "get ahead". Adobe Commerce and Mage-OS are diverging — investment today on the Adobe stack does not make Mage-OS 3 easier tomorrow.
• Indefinitely postponing 2.x upgrades. The longer you stay on Magento 2.4.5, the more costly the jump to Mage-OS 3 will be.

5. The Wimakeit position

All our modules are tested against Magento Open Source 2.4.4 → 2.4.7 AND Mage-OS 2.0 → 2.3 on PHP 8.1, 8.2, 8.3. As soon as the first public Mage-OS 3 alpha ships, we integrate the matching test matrix. Wimakeit Hyvä-native modules have no jQuery dependency on the frontend — they are already in the Mage-OS 3 spirit.

We support merchants who want to stay on Magento Open Source or migrate to Mage-OS 2 right now to gently prepare the transition to 3. It's foundation work: module audit, composer refactor, PHP upgrade in pre-prod, complete regression tests.

6. Conclusion

Mage-OS 3 is not a disruptive event for merchants in 2026 — it's a preparation window. Stores that do the hygiene work right now (modules up to date, modern PHP, auditable custom code) will move across painlessly. Those that stack up abandoned modules and postpone upgrades will pay more in 2027.

The community-driven Magento ecosystem enters its second decade. That's actually good news.

Mage-OS resources: mage-os.org (foundation's official site), github.com/mage-os (source code + public RFCs), Meet Magento 2025 — Mage-OS Roadmap talk (community replay).