Loading today’s stories
Build1 distinct publisher2 min readPublished
The change landed with platform release 2025.1, so a PIM shortlist assembled from 2024 comparisons describes terms Pimcore no longer offers. The only GPLv3 continuation is a fork Pimcore does not back.
The Engineer · Build desk
Compiled by The EngineerSomething wrong?How this is made
A revenue ceiling puts the buyer's finances under scrutiny rather than the install itself, and that moves the check out of engineering. The trigger is the annual revenue figure and what you sell to third parties, regardless of how you model attributes or where you host [3][5]. Those are numbers that change without anyone touching the codebase, which means the license standing of a running system can lapse during a good quarter.
So a shortlist has to carry two conditions forward instead of one, and they fail independently. A company under the line that runs the core for clients meets the OEM trigger anyway [5]. Pimcore also covers PIM, MDM, DAM and content management in a single platform, and the comparison describes it as a developer platform rather than a finished product [16], so the surface under the license is usually the website as well as the catalogue.
The GPLv3 route has a fixed inheritance date. OpenDXP forks the Community Edition and stays on GPLv3 [7], which is possible because 2024.4 shipped under that license [14]. Everything after 2024.4 arrives under the new terms, so the fork's usefulness is a question about its own maintainers rather than about Pimcore's roadmap [7].
Two other entries on the standard list went stale without any license text changing. Akeneo set 30 September 2026 as end of support for PIM v7 [8], which shipped in March 2023 [9], a horizon of 42 months [13]. Akeneo's own Help Center says the Community Edition continues to be maintained and that the published end-of-support dates refer to the PaaS and on-premise editions [10]. Both statements hold at once, and a self-hosted five year plan has to pick which one it builds on. Ergonode's frontend and several other public repositories have been archived and write-protected since February 2023 while releases continue under a commercial model [11], and the comparison notes that Ergonode still appears unchanged as an open-source recommendation in a number of articles [12].
One caution on provenance. The comparison is written by an employee of Webkul, the company behind UnoPIM, and it discloses that [15]. That does not make the license dates wrong, but it does make them the kind of claim you confirm in Pimcore's own license file before a procurement decision rests on it. A comparison article ranks products, but a procurement decision needs to rest on the license file itself, since that is where the terms actually live.
Ranked by verification strength, evidence, and original report placement.
With platform version 2025.1, Pimcore switched the Community Edition from GPLv3 to its own Pimcore Open Core License (POCL).
Pimcore version 2024.4 was the last release published under GPLv3.
According to Pimcore's own statements, the Community Edition under POCL is free for non-productive use, for academic and non-profit institutions, and for companies with less than 5 million euros in annual revenue.
Beyond those cases, commercial production use of Pimcore requires a Professional or Enterprise edition.
Offering the Pimcore core as SaaS or a managed service to third parties requires a separate OEM license.
POCL is not an OSI-approved open source license, although the source code remains viewable and modifiable.
Distinct publishers with included, body-backed reporting in this cluster.
dev.to
1 article · September 1, 2026
Follow any of these and your For You feed starts watching them — no settings page required.
build
One company holding the copyright is the trait that predicts the next relicensing1 distinct publisher
product
Swapping a frontier API for a self-hosted open-weight model relocates the audit question1 distinct publisher
Evidence-backed comparisons of source perspectives and observed adoption signals. Read the methodology
Which Builder, Operator, and Investor concerns the observed source mix emphasized—not a truth score.
Evidence, demonstrated adoption, hype gap, incentives, and confidence are assessed independently, each on its own current evidence. How these are measured.
Checkable in an afternoon, checked by no one
The load of this story rests on facts that are unusually easy to falsify — a release number, a revenue figure, one end-of-support date, one archival month. That specificity is worth something. What it does not substitute for is a second look: dev.to attributes the license terms to Pimcore's statements and the maintenance promise to Akeneo's Help Center without quoting or linking either, so readers sit two steps from every primary document, holding the word of a single publisher.
Terms changed; nobody counted
This reporting tells us what Pimcore now charges for and when Akeneo stops patching v7. It never tells us who is affected. No install counts, no figure for how many self-hosted users sit above the 5 million euro line, not one team named as having migrated to OpenDXP or off Akeneo v7 — and Ergonode's 'regular releases' arrive without a version number or date. License terms are supplier decisions; take-up is a separate measurement, and none was taken here.
Sober prose, forward-leaning frame
Sentence by sentence this is restrained: POCL is called a factual observation rather than a criticism, Akeneo's reassurance is printed next to its end-of-support date, and the fork gets its longevity caveat. The stretch is structural. The claim that 2024-era shortlists now describe terms nobody offers is presented as settled while resting on a single interested account, with no instance yet of a company billed, blocked or forced to move — the consequence is asserted ahead of any observed case.
Disclosed, and pointing one way
The author says plainly that he works at Webkul and that Webkul's UnoPIM is in the ranking. Then the ranking lands where you would expect: Pimcore carries a revenue ceiling, Akeneo a support cliff and a feature-reduced free edition, Ergonode archived repositories — while UnoPIM is MIT-licensed with, in his words, no revenue ceiling and no cut-down community edition. AtroPIM gets similarly warm treatment, which suggests the piece is not purely a funnel. Disclosure earns trust; it does not dissolve the alignment between the findings and the writer's paycheque.
Trust the dates, verify before you sign
Confidence splits by claim type. Quotable license and lifecycle specifics — 2025.1, 2024.4, 30 September 2026, February 2023 — are the sort of thing a competing vendor is punished for inventing, and they hang together. The softer material does not travel as well: unnamed comparison articles said to be stale, a fork's future characterised as an open question, a product 'recognisably' commercialised. With one publisher and no primary text in hand, we would open Pimcore's license page ourselves before letting any of this move a shortlist.