OpenDXP: The Open-Source Alternative Built on Pimcore.

Since Pimcore switched the Community Edition to POCL instead of GPLv3 starting with version 12, more on that under Open Source vs. Commercial License, many existing customers face the same question: stay, upgrade, or take a different path. OpenDXP is that third path, a community-driven GPLv3 fork of the Pimcore Community Edition v11.5.13, initiated by the Swiss agency DACHCOM.DIGITAL, explicitly independent of and not affiliated with Pimcore GmbH. What matters for positioning: OpenDXP isn't a second product we're adding to our lineup. It's the same core under a different license, same codebase DNA, same craft.

What OpenDXP Is

OpenDXP carries forward a GPLv3-licensed Pimcore 11.5 codebase, including the GPL bundles (E-Commerce Framework, Web2Print, Datahub, FormBuilder, Headless) that Pimcore made enterprise-only starting with version 12. Technically, it's modernized Pimcore 11: PHP 8.3 through 8.5, Symfony 7.4, the classic ExtJS admin UI. On the license side, it runs GNU GPLv3, with no revenue threshold and no mandatory product registration. These are real, provable differences from POCL, but they don't replace operating costs: hosting, maintenance, and security monitoring apply to OpenDXP just as they would to any other self-hosted system. The maturity level is young but active: the latest release is v1.3.3 (as of June 2026), with roughly monthly release cadence and a growing, still small community.

What OpenDXP Doesn't Have

Advisory quality means saying this out loud instead of glossing over it. OpenDXP has no Pimcore Studio, the modern React interface stays reserved for the Pimcore 12 line. It doesn't have the Pimcore 12 Generic Data Index, just the search bundles from the 11 era. It has no commercial enterprise bundles such as Portal Engine, Copilot, or Data Quality Management, those live in Pimcore's proprietary repository and can't be forked. There's no commercial support, no SLA, no vendor PaaS, support means community plus your own service provider. And it doesn't automatically inherit future Pimcore 12 roadmap features.

Who OpenDXP Is the Right Path For

A hard GPLv3 requirement, whether from internal policy or a copyleft ecosystem, speaks for it. So do companies above the POCL revenue threshold who don't want or need an Enterprise subscription. Anyone satisfied with Pimcore 11.5's feature level who just needs continuity past December 2026 finds a fitting answer here, as does anyone who wants to keep using the GPL E-Commerce or Web2Print bundles that became enterprise-only in Pimcore 12.

Who OpenDXP Is Not the Right Path For

Anyone who wants Pimcore Studio has no way around Pimcore 12. Anyone who needs enterprise bundles, who weighs contractual support with an SLA and a binding vendor roadmap higher than license freedom, or who's looking for a managed cloud straight from the vendor, is better served by Pimcore Enterprise. The same goes for security-critical environments that depend on a guaranteed vendor patch cadence, a community fork structurally doesn't offer that.

Same Codebase DNA, Same Craft

Our Pimcore expertise in data modeling, object bricks, the classification store, Datahub integration, import/export, and performance carries over one-to-one to OpenDXP, because under the hood it's the same Pimcore 11.5 engineering work. No second skill set, no break in competence. That's also why we advise on OpenDXP at all: not as a new product line, but as the same core under a different license, one we know just as well as the original.

An Honest Look at the Risk

Switching to a young fork is a strategic bet, not a sure thing. OpenDXP currently counts roughly 23,000 Composer installs and just under 100 GitHub stars, a real, growing, but small community with a noticeable bus-factor risk, since the fork was initiated by a single agency. We don't hide that, because we can manage it: through a deliberate bundle audit, our own security monitoring instead of relying on a vendor, and an honest assessment of whether your use case justifies that risk. An advisor who names this risk openly is more credible than one who plays it down.