To use Adobe Commerce well, it helps to know how it got here. Each ownership change rewrote the platform’s economics, technical priorities, and partner ecosystem — and every one of those rewrites still shows up in the code.
Sixteen years in six moves
- 2008 — Magento 1.0 released by Varien, on top of the Zend framework.
- 2011 — eBay acquires Magento for $180 million.
- 2015 — Permira (private equity) buys Magento from eBay.
- 2015 (November) — Magento 2 released, a major architectural rewrite.
- 2018 — Adobe acquires Magento for $1.68 billion.
- 2020 (June) — End of life for the Magento 1.x line.
The three rewrites that still matter
Each owner left behind technical debt and technical gifts. Varien’s open-source philosophy is why Adobe Commerce still has a vibrant extension marketplace. eBay’s tenure pushed the platform toward enterprise capabilities — payments, fraud, scale. Permira’s period was quieter, but it’s when Magento 2 was finally released after years of community frustration with the v1 architecture.
Adobe’s acquisition reframed the platform again. Commerce is now part of a much larger product family — Experience Cloud, Real-Time CDP, Experience Platform — and the technical roadmap has shifted accordingly. Connectors, App Builder, API Mesh, and the new SaaS offerings (Cloud Service and Optimizer) all point toward the same direction: Commerce as a node in Adobe’s broader stack rather than a standalone storefront engine.
Adobe Commerce is famously compatible with just about everything, it has an amazing ecosphere of participants, and Adobe is taking their acquisition of Magento very seriously.
Adapted from the Adobe Commerce Primer, slides 6–7. Last reviewed May 2026.