The open-source PIM landscape changed twice in eighteen months. Most comparison articles still ranking for it haven't caught up. Current state, September 2026.
The date
Akeneo has published 30 September 2026 as the end of support for PIM v7. That is twenty-seven days from the date of writing.
It is worth stating precisely what that does and does not mean, because both halves are currently circulating in isolation.
It does mean a specific version reaches the end of its supported life on a specific date. Teams running v7 have an upgrade decision with a deadline attached.
It does not mean Akeneo is discontinued or unsupported. Akeneo's own help centre states that the Community Edition continues to be supported. The 30 September date attaches to v7 across editions, not to the Community Edition as a product.
Both are true simultaneously. Plan around the first. Ignore anyone selling urgency based on the second.
The change most articles missed
While attention was on Akeneo, the larger licensing shift happened elsewhere.
Pimcore's Community Edition is no longer GPLv3. With Platform version 2025.1, Pimcore moved the Community Edition to the Pimcore Open Core License (POCL). Version 2024.4 was the last GPLv3 release.
Under POCL, the Community Edition is free for non-production use, for non-profits, and for companies below EUR 5 million in annual revenue. Above that threshold, production use requires a commercial licence.
This is the change that catches teams out. An evaluation done in 2023 recorded Pimcore CE as free and GPLv3. A company that has since grown past EUR 5M has a different licensing position than the one in its comparison sheet. Source: pimcore.com/en/products/edition/community
Most ranking "open source PIM compared" articles still describe Pimcore CE as GPLv3. Publication dates are worth checking on anything in this space, including this article.
The systems as they stand
Akeneo Community Edition
Licensed under OSL 3.0. Mature, widely deployed, and backed by the largest partner and agency ecosystem in the PIM market, with a reference base going back over a decade. Hiring someone who already knows the system is easier here than anywhere else on this list.
The consideration is trajectory. The Community Edition has not been the focus of new feature development for some time, and the upgrade path points toward a paid edition. That is a legitimate commercial model. It should be a deliberate choice at selection time rather than a discovery in year three.
Pimcore Community Edition
The broadest platform here. PIM, DAM, MDM and CMS in one system. For requirements that genuinely span all four, nothing else on this list is comparable.
Three factors to weigh. The POCL licence and the EUR 5M revenue threshold, above. The implementation investment, which is substantial: the breadth requires significant developer time before there is a working system. And whether the breadth is needed at all. A team that requires product data management and nothing else acquires a large surface area it will never use.
OpenDXP
A community fork of Pimcore Community Edition, continuing under GPLv3.
For teams whose reason for choosing Pimcore CE was specifically the GPLv3 licence, this is the option the POCL change makes relevant. Smaller community than Pimcore itself. Omitted from most comparison articles entirely.
AtroPIM
Built on the AtroCore platform by AtroCore GmbH, Regensburg. GPLv3.
AtroCore's documentation states that the open-source edition ships with full functionality rather than a feature-limited free tier, which is more than several commercial community editions offer. API-centric architecture with a data model configurable without code. Strong for manufacturers and distributors with complex, deeply nested product data.
AtroCore also publishes a comparison of open-source PIM systems that ranks first for the obvious search term. Worth reading, with the same caution any vendor-authored comparison warrants.
Ergonode
Noted so evaluation time is not wasted. The public repositories were archived in February 2023. Current status is worth confirming before investing in a trial.
UnoPim
MIT licensed, with no revenue cap, no feature-gated edition and no separate enterprise build. Laravel 13. Integrated DAM in the core rather than as a paid add-on. Connectors for Shopify, Magento 2, WooCommerce and Odoo, alongside a REST API and an MCP interface. Built for high-volume catalogues, with a published account of operation beyond 10 million products. An AI agent manages the catalogue through natural language across 32+ actions, working with OpenAI, Gemini, Grok, DeepSeek and other providers.
The trade-offs, stated plainly:
- It is the newest system on this list, with no ten-year reference base.
- The community is smaller. Fewer existing answers to specific problems.
- Fewer experienced implementation agencies. A procurement process requiring three independent quotes from certified partners is harder to satisfy here than with Akeneo.
- It is a PIM with DAM, not a PIM/DAM/MDM/CMS platform. Requirements spanning all four point to Pimcore instead.
The case for it is the licence terms, the DPP support and the scale profile. It does not win on ecosystem maturity and should not be selected on that basis.
The criterion nobody had in 2023
Comparison sheets written three years ago share the same columns: attributes, variants, channels, locales, completeness, API, import and export.
There is a new column, and it arrives with a legal deadline rather than a preference.
The battery passport becomes mandatory on 18 February 2027 under EU Regulation 2023/1542, covering traction batteries, LMT batteries and industrial batteries above 2 kWh. That is under six months away.
The wider framework is the Ecodesign for Sustainable Products Regulation, Regulation (EU) 2024/1781. ESPR is horizontal: it establishes the framework, and specific obligations arrive product group by product group through delegated acts. For most manufacturers the question is not whether a Digital Product Passport requirement will apply, but when.
This is where a compliance topic becomes a system selection topic. A Digital Product Passport is mechanically a structured set of product attributes: material composition, recycled content, substances of concern, and a SCIP declaration filed with ECHA. Attributes, in locales, versioned, published to a channel.
That is a PIM's job description, not a new software category.
The evaluation question for 2026 is therefore whether passport data lives in the same system as the rest of the product data, or in a separate service to be integrated and paid for separately. UnoPim ships DPP support natively in the 3.x line, including SCIP/ECHA declaration, material composition and recycled content. Other vendors are approaching this differently and some will approach it better. The gap worth closing is an evaluation sheet that does not mention it at all.
One caveat stated rather than buried: a PIM provides the data foundation for a passport. It does not deliver compliance. Compliance is a legal and process question, and software sold as the answer to it is oversold.
Decision guide
- Running Akeneo v7. Plan the upgrade with 30 September on the calendar, rather than letting the deadline drive the decision in week four.
- Evaluated Pimcore CE before 2025 and growing. Re-read the licence. The EUR 5M threshold may now apply.
- Chose Pimcore CE specifically for GPLv3. Look at OpenDXP.
- Complex manufacturing or distribution data. AtroPIM warrants a serious look.
- Need PIM, DAM, MDM and CMS in one platform. Pimcore, accepting the implementation investment.
- Want a permissive licence with no revenue ceiling, with DPP on the roadmap. UnoPim is worth evaluating, with the maturity trade-offs above understood in advance.
Corrections are welcome in the comments and will be noted in the article. Comparison content in this space goes stale quickly, and licence terms have changed twice in eighteen months.
UnoPim: unopim.com · github.com/unopim/unopim
Top comments (0)