Weave Code
Opendxp Laravel Package
open-dxp/opendxp
OpenDXP is an open-source digital experience platform built on PHP and Symfony. It provides flexible tools and APIs for managing content, product data, digital assets, and customer experiences, making it easier to build and integrate modern web applications.
OpenDXP is an open-source data and experience management platform for building content-, product-, and asset-driven applications. Forked from Pimcore and built on Symfony, it unifies a CMS, PIM/MDM, DAM, and a digital commerce framework in a single PHP stack—giving teams one consistent data model and API across every channel.
- Unified PIM/MDM for product and master data
- DAM with asset management and media processing
- CMS for multi-channel experience delivery
- Extensible Symfony/PHP architecture with bundles
- API-first design for headless and integration use cases
Frequently asked questions about Opendxp
- Can I install OpenDXP with Composer inside my Laravel app?
- No. OpenDXP is a full-stack Symfony/Doctrine platform that expects to be the application, not a library inside one. Requiring it in an existing Laravel project typically produces an unresolvable dependency graph because both stacks pin overlapping Symfony, Doctrine, and PSR versions. Treat it as a standalone service you call over HTTP instead.
- What is OpenDXP and what does it actually do?
- OpenDXP is an open-source PHP digital experience platform built on Symfony that bundles product information management, digital asset management, a headless CMS, and commerce data in one backend. It is the community fork lineage of Pimcore, so its extension model, admin UI, and operational shape are inherited from that ecosystem. It is aimed at teams that want an API-first content and product data hub rather than a framework-level package.
- How do I integrate OpenDXP with a Laravel application?
- Deploy OpenDXP standalone, for example via its Docker Compose setup, and expose its REST, GraphQL, or Datahub-style APIs. Laravel stays the system of record for accounts, orders, checkout, and pricing, while OpenDXP owns product enrichment, media, translations, and CMS content. Sync by pulling on a schedule and on webhooks, cache responses in Redis with tagged invalidation, and fall back to last-known-good data if the upstream API fails.
- Which Laravel or PHP versions does OpenDXP support?
- OpenDXP does not target Laravel versions at all because it is a Symfony platform with its own pinned PHP and Symfony requirements. Check the repository's composer.json and release notes for the exact supported PHP and Symfony versions before deploying. Keep your Laravel host on a separate runtime; the two applications should never share a PHP process or autoloader.
- Is there an official Laravel SDK or PHP client for OpenDXP?
- No official Laravel SDK exists. The API-first posture is genuine, but you will own the HTTP client, DTOs, retries, and contract tests on the Laravel side. Build a thin service class around Laravel's HTTP client and validate the auth model, pagination, filtering, localization, and asset delivery URLs early.
- What license does OpenDXP use and can I use it commercially?
- The repository currently reports NOASSERTION, which is a blocker rather than a footnote. The upstream Pimcore lineage carries copyleft obligations, so legal should confirm the actual license, whether any commercial or enterprise bundles are included in the fork, and what obligations apply to SaaS versus distributed use. Do not ship to production until that review is complete.
- What infrastructure does OpenDXP need in production?
- Expect MySQL or MariaDB, Redis, a search engine such as Elasticsearch or OpenSearch, queue workers, and object storage or a CDN for assets. That is a materially larger footprint than a typical Laravel deployment and should be costed per environment. Validate the minimum CPU, RAM, search cluster size, and storage requirements before scoping the integration.
- How do webhooks and event syncing work between OpenDXP and Laravel?
- Use OpenDXP webhooks to push change events into a Laravel queue such as Horizon or RabbitMQ, then apply idempotent projection updates to your local cache or read models. Authenticate with service credentials and verify webhook signatures. Confirm the fork's webhook and event coverage before relying on it, since gaps will force you back to polling.
- Is OpenDXP mature enough for production, or should I worry about the fork?
- Community maturity is thin, with roughly 104 stars, an unspecified repository URL, and limited third-party documentation or Stack Overflow coverage. Release metadata such as a future last-release date should be treated as unverified until you check tags and changelog discipline yourself. Fork divergence is a real risk: upstream fixes and security patches land first, so a stalled fork becomes a liability within 12 to 18 months.
- What are the alternatives to OpenDXP for a Laravel project?
- If you need a headless CMS or product data hub, compare against Pimcore itself, Strapi, Directus, or commercetools-style composable commerce APIs. For simpler needs, Laravel Nova, Filament, or a custom content model may be cheaper than running a separate DXP stack. Choose OpenDXP only when its combined PIM, DAM, and CMS feature set justifies the operational overhead and the license question is resolved.
Weaver
How can I help you explore Laravel packages today?