Pimcore and POCL in 2026: The Licensing Decision You Cannot Postpone

A license change is a budget decision in disguise

Pimcore changed how its Community Edition is licensed, and a lot of teams filed it under "legal will look at it eventually." That is the wrong drawer. For a company over a certain revenue line, this is a procurement and budget decision with a real number attached, and it lands the moment you take your next platform upgrade.

This is a decision guide, not legal advice. Here is what changed, who it affects, and how to decide without guessing.

What actually changed

Pimcore moved its Community Edition away from the GNU General Public License v3 (GPLv3) to the Pimcore Open Core License (POCL), starting with Platform version 2025.1. Platform version 2024.4 was the final release under GPLv3.

The motivation is the part most coverage gets right: GPLv3 is "viral". Its copyleft terms create real uncertainty for companies that build proprietary extensions on top of an open-source core. POCL keeps the source open and customizable while removing that friction, so you can keep your custom Pimcore extensions private without the GPLv3 question hanging over them.

The line that decides everything: 5 million euros

POCL keeps Pimcore free for:

• organizations with less than 5 million euros in annual revenue,
• non-profits, and
• educational institutions.

If your organization is above 5 million euros in annual revenue and you upgrade to a POCL-era version (2025.1 or later), you need a commercial license to stay compliant. For a German Mittelstand company running product data on Pimcore, that 5 million euro line is usually well behind you, which means the upgrade and the license are the same conversation.

One important clarification: if you are already on a Pimcore Professional, Enterprise, or PaaS edition under a commercial agreement, nothing changes for you. POCL is about the previously GPLv3 Community Edition.

What POCL permits, in plain terms

• You can access, read, customize, and build on the source.
• You can keep your own extensions and customizations private.
• The open-core boundary is explicit, which removes the GPLv3 ambiguity that made some legal teams nervous.

POCL is not a move to closed source. It is a move to clear terms.

The three honest options

For an organization over the revenue line, there are exactly three positions, and each has a cost.

1. Freeze on 2024.4 (GPLv3). You stay on the last GPLv3 release and take no POCL-era upgrade. Cost: you stop receiving platform updates, security patches eventually thin out, and you accumulate upgrade debt. This buys time, not a future.
2. Upgrade and license. You move onto the current platform line and take the commercial license. Cost: a license line in the budget, in exchange for staying current, supported, and compliant.
3. Re-evaluate the platform. If the license cost forces the question, it is the right moment to confirm Pimcore is still the right fit at all, rather than renew by inertia. Usually it is, especially for serious PIM and DAM, but the question deserves an honest answer.

The wrong option is the fourth one teams drift into by accident: upgrade without licensing while over the revenue line. That is a compliance gap, not a saving.

How to assess your exposure in an afternoon

You can scope this yourself before any vendor conversation.

1. Version. Which Pimcore platform version are you on? Anything 2025.1 or later is POCL. 2024.4 or earlier is GPLv3.
2. Edition. Community Edition, or a commercial Professional, Enterprise, or PaaS agreement? A commercial edition means this does not apply to you.
3. Revenue. Above or below 5 million euros annual revenue?
4. Upgrade pressure. What is forcing an upgrade: a security requirement, a Symfony or PHP end-of-life, a feature you need? That timing is your real deadline.

Those four answers put you in one of the three positions above. Most of the difficulty is not the decision, it is having the inventory to make it.

Where we fit

We are Pimcore developers and we contribute open-source Pimcore work, including our Pimcore Asset Pilot bundle. When clients hit this licensing question, what they usually need first is not a license, it is clarity: which version, which edition, what the upgrade actually involves, and what it costs to stay current. We offer a focused Pimcore audit that produces exactly that: your current version and edition, your POCL exposure, the upgrade path and its effort, and a recommendation you can take to a budget meeting.

For more on how we work with the platform, see our guides on Pimcore upgrades from 10 to 12 and Pimcore enterprise workflow design, or the Pimcore services overview.

If you want the audit, start a conversation and tell us your version and edition. We will come back with a clear read on where you stand.

Sources: the Pimcore announcement, Pimcore says goodbye to GPL and enters a new era with POCL. Licensing terms can change; confirm current terms with Pimcore before a commercial decision.