We want businesses and careers built around Magento Open Source to prosper.
Magento Open Source is a mature eCommerce platform, with more than 300,000 developers and thousands of businesses worldwide depending on it.
Adobe is focused on large enterprise projects, and because of that doesn’t give many resources to supporting Magento Open Source. Moreover, Adobe is actively harming Magento Open Source businesses with false or misleading claims like “Magento is now Adobe Commerce”.
We are ensuring a bright future for Magento by enabling the development community to enhance the platform, providing merchants and agencies the long-term reliability they require, and giving newcomers an easy entry into the platform.
Mage-OS is an eCommerce platform, evolved from Magento Open Source. It can be used to build online stores, in the same way that Magento Open Source can be used.
However, because Mage-OS is focused on improving the components that make up the platform, we envision it becoming a foundation that many purpose-built variations of eCommerce systems can be built on. For example, we envision a minimal system optimized for a low resource consumption, or a system optimized for headless store fronts, or for modern server side rendered stores, or an e-procurement system, etc.
We are also driving the ecosystem by providing content for merchants and agencies to gather first hand information about the platform. This will include comparisons to other platforms, showcases, FAQs, directories, and more.
Finally, Mage-OS will focus on local representation at Magento specific events and eCommerce events at large, to engage with businesses and developers in person.
In the short term, Mage-OS will be the same but different. Mage-OS will be available for your use if and when you want it.
Our initial focus is on significant performance and usability improvements. We will be integrating changes that have been suggested as Pull Requests to Magento Open Source by the community, but haven’t been included by Adobe due to lack of resources for Magento Open Source.
Over time, those bug fixes and improvements will accumulate and become an increasingly large advantage for Mage-OS over Magento.
Magento is a very stable and feature rich eCommerce platform with a huge amount of integrations with third party services and a rich developer community. Mage-OS is and will remain intercompatible with Magento solutions and integrations, and provides further enhancements on top.
We are working on content to provide a detailed comparison of Magento to other platforms.
Mage-OS benefits from having evolved out of Magento Open Source. It offers:
- A mature and stable platform with a huge amount of existing third party integrations.
- Ownership of the platform by being able to become a member of the Mage-OS Association.
- Unparalleled flexibility and customizability.
- A large global community of developers, agencies, and support.
Mage-OS is organized by a nonprofit association, the ‘Mage-OS Association’. At the time of writing, this association is currently being registered as a legal entity.
Most financing will be through membership fees from businesses and individuals.
The membership fees for individual members will be affordable for someone working with Magento on a regular basis, regardless of their location.
Companies can become members at higher levels (e.g. bronze, silver, gold) for higher amounts, to contribute to the ongoing development of the platform.
Contributing to Mage-OS financially is directly funding the development and longevity of this platform and ecosystem.
The Mage-OS Association is not-for-profit, and will be investing the vast majority of funds directly into staffing, operations, and development of Mage-OS. Financing Mage-OS is about innovating and sustaining an awesome platform into something we can continue to rely on for the next decade or more.
By supporting Mage-OS, you will get a membership badge showing your membership level, and a listing in our membership directory, which is open to all visitors of the Mage-OS website. Show your support, and others interested in Mage-OS will be able to find you in the process.
- Direct influence and ownership of the platform by becoming a member of the Mage-OS Association.
- A stable and mature eCommerce platform, evolved out of Magento Open Source which is backed by a large corporation.
- Participation in the vibrant global Magento community.
Vision and Sustainability
Our vision for Mage-OS is to provide a high-quality, dependable, and better alternative to the Adobe-curated Magento Open Source project. We will demonstrate an ability to process contributions quickly and effectively, improve the quality and accessibility of the platform, and release updates on a regular cadence that users can plan around.
We expect these actions to have a meaningful improvement on the quality of life for all people in the ecosystem, which will in turn encourage growth and engagement among the community.
Currently we are still at the beginning. We are providing an independently built version of all releases of Magento Open Source since version 2.3.7-p3 (including all 2.4.*) through a composer repository found at mirror.mage-os.org.
We also provide documentation and tooling for others to create their own mirrors. This allows hosting providers to better support their customers, and makes the whole ecosystem more decentralized and resilient.
We also generate nightly builds of the current Magento Open Source development version, through the composer repository upstream-nightly.mage-os.org.
We are in the process of creating the infrastructure to support and release our own Mage-OS Distribution releases and accept contributions.
The roadmap is currently focused on building the required infrastructure, rather than improving the eCommerce platform itself.
In the short term, we are working on being able to process pull requests. This will be possible by the end of 2022.
Then we will work on the process of creating independent releases during the first quarter of 2023.
After that, we will begin the work to improve the platform itself.
You can start using the mirror distribution right now. All it takes is installing Magento from mirror.mage-os.org rather than repo.magento.com. However, currently there are few advantages to doing so as the resulting installation will be identical.
You can start using the improved version of Mage-OS as soon as it is available. Look for that in the first half of 2023. Stay tuned!
If or when Adobe stops supporting and maintaining Magento Open Source, Mage-OS will be well positioned to step into its place. This is an important aspect of Mage-OS: to provide certainty and a long-term plan for the ecosystem, regardless of factors outside our control.
If at some point Magento Open Source becomes unsupported, we will start considering larger changes to improve the platform, with less emphasis on preserving upstream compatibility with Magento Open Source.
In the meantime, we will make every effort to preserve compatibility with Magento Open Source, while at the same time improving performance and adding new features.
This is necessary to preserve ease of use, familiarity, and compatibility for everyone (including vendors, extensions, and developers).
We will follow an approach inspired by the Typo3 Association, which founded a limited company (Typo3 GmbH) which is owned 100% by the Typo3 association. The company provides services supporting the ecosystem, such as LTS, SLAs, certification, but does not compete with the members of the community. This means that the company will not implement Mage-OS projects nor do body leasing.
This model of a community owned commercial entity will provide the vendor based support and financial backing required for the long term success of businesses of all sizes built around Mage-OS.
We’re really into this Mage-OS thing. Also, we’re not going to do it alone! We will be hiring full-time paid staff and opening a Mage-OS development grant program as soon as circumstances allow us to do so.
No. We can’t guarantee future improvements or features won’t step into the territory of existing solutions, but our intention is to support the ecosystem, not undermine it.
Mage-OS and the Mage-OS Association will not be providing any conventional merchant services. Any requests we receive for development, integration, site builds, audits, etc. will be referred to the Mage-OS supporters list.
Mage-OS and the Magento Association both deal with the Magento ecosystem and community, but they are focused on different things.
Magento Association is focused on supporting and maintaining the Magento community through events, content, outreach, and similar programs, but they have little involvement in the development of Magento Open Source itself. One of the main purposes of the Magento Association is to represent the Magento brand, and to communicate with the Magento brand owner, Adobe.
The Mage-OS Association on the other hand is more technology-focused. We support the ecosystem by publishing an improved but compatible distribution of Magento. We are focused on growing independently of Adobe.
We look forward to collaborating with the Magento Association in the future, as we both share the same fundamental purpose of growing and supporting the Magento Open Source ecosystem.
We have an immense amount of respect for the people that built Magento and maintain it to this day. That said, we fundamentally disagree with the direction Adobe is taking the platform (as detailed in our open letter 14 Sept 2021: https://mage-os.org/blog/the-future-of-magento). In order to take the steps we see as necessary for Magento to thrive among the latest eCommerce competitors, we need control and nimbleness that is not possible in the Adobe-controlled Magento Open Source project.
For this reason, we made the difficult decision to create our own fork and distribution based on the Magento open source code. The Magento name and logo are trademarks we can’t use, so we are calling this new product Mage-OS, and the organization behind it is the Mage-OS Association.
Splitting the ecosystem is the last thing we want to do.
Mage-OS was created to revitalize and sustain the community of developers, agencies, merchants, and partners that built their business around Magento. The best way for us to do that is to stay compatible with Magento Open Source and Adobe Commerce to the greatest extent possible, for as long as we can.
- Extensions that work with Magento will work with Mage-OS.
- Extensions that work with Mage-OS will work with Magento (unless they are based on Mage-OS specific features).
- Code samples and syntax for Magento will work for Mage-OS too.
- Anyone that learns or knows Magento or Mage-OS should be able to switch to the other with minimal effort or confusion.
Mage-OS will make improvements and fixes to the core for Mage-OS Distribution, but those fixes will not break or fundamentally change the nature of Magento. It’s still going to be the same architecture, with the same incredible customizability. If we do this right, it’ll just be easier and nicer to work with.
No. Mage-OS was started by a group of companies that happened to be located mostly in Europe, but we are actively growing our member base all over the world.
For more information, please refer to our blog post on Diversity and Inclusion that focuses among other things on geographic representation.
Any people with a business that relies on Magento have a vested interest in Magento’s success. Because of that, they (and we) are committed to improve the ecosystem, and to ensure it lives long and prospers. That applies to everyone involved with Mage-OS, including the association’s board of directors.
There is a long history of ‘cooperative competition’ in the Magento ecosystem. This is based on the belief that “if the cake gets bigger, we all win”.
The Mage-OS Association’s statutes (rules of operation) have specific requirements for avoiding direct conflicts of interest while acting for Mage-OS, which all board members must abide by.
Mage-OS will not offer training as long as there are businesses in the Magento ecosystem that do so. There are many excellent resources to learn Magento as a merchant, a solution architect, or a developer.
We do not have concrete plans to offer our own certification, but it is something that might happen in the future if it serves the community.
At this time we don’t have concrete plans to organize a Mage-OS conference, because we are focused on other things, but it sure has come up already in discussions, so who knows – it might happen!
That said, members are organizing Mage-OS meetups and participate and speak at other events, including Meet-Commerce and Unconferences. If you are interested in representing Mage-OS at a conference you are planning to attend, that is great! Please let us know on Discord!
Once a year all members are invited to the General Assembly of the Mage-OS Association, an online event. The General Assembly governs the Mage-OS Association according to the association statutes.
Yes! You will just need to make some changes to your composer.json file and then update. The Mage-OS mirror is compatible with all your existing Magento code, but please test compilation and general site functionality before moving to Mage-OS on a live site.
Yes! You will just need to make some changes to your composer.json file and then update. You will lose any Mage-OS specific enhancements in the process, but if you change your mind, you can switch back just as easily.
Yes. It is very similar to moving from Magento Open Source to Adobe Commerce. You’ll lose any Mage-OS specific features in the process, but both are based on the same Magento core, so all of your data will stay intact.
Yes. You’ll lose any Adobe Commerce specific features in the process, but both are based on the same Magento core, so all of your data will stay intact. The process is very similar to moving from Adobe Commerce to Magento Open Source, so it is possible, but it does require some work.
Magento is installed using the composer command
composer create-project –repository-url=https://repo.magento.com magento/project-community-edition
You can choose to install Mage-OS by using a mage-os repository-url instead of repo.magento.com in that command:
mirror.mage-os.orgprovides any Magento Open Source version since 2.3.7-p3
upstream-nightly.mage-os.orgprovides the nightly builds based on the current develop branches.*
repo.mage-os.orgwill have the Mage-OS Distribution releases we are currently working towards.
nightly.mage-os.orghas Mage-OS Distribution nightly development builds.*
*(Technically these could also live in mirror.mage-os.org and repo.mage-os.org, but we like to keep them separate as we only keep a week of past nightly builds, and the mirror.mage-os.org repo should be idempotent, that is, any package that is available there once will stay available forever.)
Today: Join us in Discord at https://chat.mage-os.org and let us know how you’re interested in helping!
Our current main work streams are around
- The Mage-OS product
- Visibility and understanding of the Mage-OS initiative and brand (Marketing and Communication)
- Content development around Mage-OS (features, showcases, comparisons, and more)
Soon: We will open membership and supporter programs by the end of the year to allow you or your company to support Mage-OS financially. This will allow us to hire full-time staff to further Mage-OS, provide additional resources, and start a grant program for development of the Mage-OS Distribution.
Also soon: We will open the Mage-OS Distribution to contributions and pull requests.
You can contribute financially or through volunteer work. By contributing to Mage-OS, you’re directly supporting development of the Mage-OS and Magento ecosystem. You can directly influence the direction of the platform and help to keep it modern and relevant.
Soon! Follow us on Discord, Twitter, or LinkedIn for updates. We are working on the infrastructure now, and aim to start accepting pull requests on GitHub by the end of 2022.
In time we will accept contributions of any nature, but to start we are particularly interested in backwards compatible changes:
- Bug fixes
- Improvements to the developer experience
- Performance improvements
- Improvements to maintainability, for example cleaning up the package dependency graph. (mostly backwards compatible)
- Independent modules which enhance or add functionality
Yes! Please join and participate. If you just want to listen, that is fine, too – just let us know when you join.
Meetings happen in Discord, in the video/audio channel “Meeting Room 1”, at:
- Monday at 3PM CET: Content meeting
- Tuesday at 3PM CET: Tech meeting
Mage-OS is only focused on Magento 2, particularly the supported release line (2.4). For Magento 1, we’d encourage you to look at OpenMage LTS.
Currently the Mage-OS Mirror repository provides all versions of Magento 2 since 2.3.7-p3.
The Mage-OS Distribution will be based on the latest Magento Open Source version.
We are in the process of setting up repository forks specific to the Mage-OS Distribution, as well as infrastructure and instrumentation to drive those repositories and keep them in sync with changes to the associated Magento Open Source repositories.
You can find the core repository already at: https://github.com/mage-os/mageos-magento2
Ultimately, you will be able to submit PRs directly to Mage-OS repositories, just like you would submit them to Magento Open Source.
For any work that doesn’t require changes to the Magento core, we encourage those to be developed as separate modules instead. Please see further notes below.
We’ve had many informal discussions with Adobe about how to merge Mage-OS PRs into Magento Open Source. The most likely process will be that Magento will cherry-pick commits they are interested in.
Regarding divergence: Our goal is to maintain backwards compatibility for as long as possible, but yes, Mage-OS and Magento will diverge over time.
There’s a public GitHub project that details tasks to be completed before we accept PRs: https://github.com/orgs/mage-os/projects/3
For new features we will likely follow an approach of delivering these as separate packages.
We have three stated technical improvement goals for MageOS currently:
- Fix the package Graph and use a Graph build to improve the time it takes to run tests.
- Avoid breaking changes.
- Make it easier to get started as a junior developer. This means making a package that “just works” on a WAMP/MAMP/LAMP environment. This is important to keep the influx of new developers into the ecosystem alive.
There are other ideas that come from this (like delivering different metapackages other than project-community-edition).
Regarding new features: We plan to take an approach similar to Adobe, by implementing new features as new packages, rather than directly in the core. This allows for an independent release schedule of features, as well as making it easier to keep upstream compatibility with Magento Open Source intact.
So new features = new modules, but improvements to the core that are backwards compatible can go into the Mage-OS core.
Yes, add-on modules are the plan for enhancements and additions to the platform. This has numerous advantages, including easier maintenance, separate release schedules, and keeping the main repository closer to the upstream Magento core.
Only slightly. The meta package might be called differently, perhaps mage-os/project-community-edition, but the packages will still use the “magento” vendor name for compatibility reasons.
We are aware of the close connection between the Hyvä company and Mage-OS and would like to take the opportunity to be transparent about the situation, and highlight actions we are eager to take to diffuse any impression that one party has too much influence over the Mage-OS initiative.
Hyvä is a front end framework for Magento, which means it is very reliant on the stability and longevity of Open Source. It’s a fact, the Open Letter was initiated by the founder of Hyvä among many other passionate and active members of the Magento Community.
As it happened, Vinai Kopp (CTO at Hyvä) was appointed President in the establishment of the first Board of Directors for the Association. He is leading the technical efforts of Mage-OS, and engaging the Community in the weekly tech meetings as well as Magento meet ups and events. In his own time he also dedicates a lot of his architecture and coding mastery to enrich the Mage-OS product infrastructure.
Although the Vice President Thien-Lan Weber is now also a Hyvä employee, she was CMO at OneStepCheckout when she joined Mage-OS, with a clear objective to defend interests of Magento Extension providers who also heavily rely on the eCommerce Platform. She helps build the brand awareness and comprehension of the Mage-OS project by contributing to content and marketing efforts. She is a strong advocate for diversity and inclusion.
One rule we set for our Association early on was to avoid two people from the same company sitting on the Board of Directors. This will be a consideration when the elections to nominate the new Board of Directors comes up in 2024.
In addition to contributing with employees’ work hours, the Hyvä company has also provided brand assets design (logo, visual identity), and funded marketing material such as button badges and roll up banners. Some might also see the success of Hyvä and its popularity among the Magento Community as a booster for Mage-OS exposure, credibility, and momentum.
All that being said, the board of Mage-OS is interested to reduce the dependance on Hyvä and actively reach out to more companies who heavily rely on the success and strength of the Magento Open Source platform, including frontends such as Vue Storefront, Breeze, Front Commerce, GraphCommerce and others. We invite you all to reach out and join us. Diversity of perspectives and tech stacks can only make our codebase better, more extensible, more relevant, and more useful for our end users: eCommerce merchants.
We also would like to draw more attention to how much sweat and contribution are provided by companies other than Hyvä, including Agencies, Extension Vendors, Solution Providers, and Freelancers in the Magento ecosystem. Our Contributors Page is a dedicated section to thank them and give them the recognition they deserve.