FAQ - OpenDXP

The OpenDXP Core forms the technical basis of the platform.
It contains the core architecture, basic systems and fundamental functions.

The OpenDXP Core Bundles are modular extensions that provide additional functionalities and specifically complement the core.
They are publicly available under GPLv3, but are not installed together with the OpenDXP Core by default.

The OpenDXP Feature Bundles are proven and productively tested DACHCOM bundles that have been migrated to OpenDXP. They are not publicly available and can be purchased in various license models to support the further development, stability and security of OpenDXP

In short:

• Core = foundation
• Core bundles = public extensions
• Feature Bundles = extensions within the OpenDXP Ecosystem Supports

Yes.

The OpenDXP core is and will remain permanently open source.

It is publicly available and can be viewed transparently.
GitHub: https://github.com/open-dxp

No.

Bundles are deliberately modular and separate from the core,
so the architecture remains clearly structured and flexibly expandable.

The separation enables:

• stable core architecture
• modular extensibility
• clean versioning
• targeted further development of individual functions
• better maintainability

The OpenDXP Feature Bundles can be obtained as part of the OpenDXP Ecosystem Support.

Details can be found on the page Ecosystem Support.

The Ecosystem Support enables:

• structured further development
• professional release processes
• ongoing updates
• Core compatibility
• sustainable financing of the ecosystem

The contribution is invested 1:1 in the further development of the bundles and the core system.

The bundles have been updated to GPLv3. Find out more at Ecosystem Supports.

Yes.

The core can be operated independently.
Bundles extend the system modularly depending on the project requirements.

As part of Ecosystem Support, private GitHub access including an individual access key is provided.

This allows bundles to be versioned and cleanly integrated into existing development processes.

Yes.

Bundles can be used within your own organization and in several of your own customer projects.

An overview can be found on the page OpenDXP Bundles.

Yes.

The core is open source. Contributions via pull requests are welcome.
Please refer to the respective contribution guidelines in the repository.

Yes - as part of the OpenDXP ecosystem support.

Bugfixes can be submitted directly as pull requests. For larger features, please open an issue in advance so that the core team can coordinate the architecture and concept.

We welcome contributions from the community - either as an issue or as a pull request in the GitHub repository. All suggestions are reviewed with a view to security, stability and the sustainable further development of the platform.

Yes.

OpenDXP has a modular structure. Custom bundles can be developed and integrated.

It enables:

• long-term stability
• structured further development
• professional releases
• clear roadmap
• sustainable financing

It strengthens your projects and the entire OpenDXP ecosystem.

The publicly available code can be viewed on GitHub: https://github.com/open-dxp

Yes.

Further development is structured. Roadmap information can be found on the website at Roadmap.

Breaking changes are versioned and documented.
Migration instructions are provided.

Yes.

Security topics are prioritized and provided as part of active further development.

• Agencies
• Integrators
• Platform teams
• Companies with a long-term digital strategy
• See also page The platform

Yes.

The modular architecture, the clear core/bundle separation and the ecosystem model ensure long-term maintainability and further development.

Details can be found on the page Ecosystem Support.

For individual inquiries: contact@opendxp.io