Core Persistence Laravel Package

Product Decisions This Supports

• Platform selection, not library selection. This is an internal decomposition artifact of Ibexa DXP, not an adoptable library. The decision it informs is "do we standardize on Ibexa DXP as our content platform?" — everything else is downstream of that.
• Build vs. buy on content persistence. The package is the storage layer (persistence SPI + Doctrine/DBAL-backed handlers) behind Ibexa's content model. Reimplementing equivalent capability — content model versioning, multi-language, multi-repository, field-type storage — is a multi-quarter engineering effort with no product differentiation. It argues strongly for buy.
• Custom field type roadmap. If we commit to Ibexa, any feature that needs new content attributes eventually lands here as a custom field type with custom storage. That is a real, plannable workstream with schema-migration and upgrade-testing cost — worth sizing before committing to a content model.
• Upgrade and migration planning. This is where schema changes concentrate. Major DXP upgrades carry non-trivial migration risk; roadmap should reserve capacity around them.
• Procurement and licensing. Dual-licensed under Ibexa BUL (requires a paid DXP subscription) or GPLv2. The registry reports NOASSERTION, so automated compliance tooling will flag it. If we distribute proprietary software, GPLv2 copyleft is likely a blocker and BUL becomes mandatory — a budget line, not a technical detail.
• Stack fit. Note the mismatch: this is Symfony-based, not Laravel. If our roadmap is Laravel-centric, this package is out of scope by default, and that is itself the decision.

When to Consider This Package

Consider it only when:

• We already hold (or are actively evaluating) an Ibexa DXP subscription and need to extend persistence — custom field types, custom storage handlers, or legacy eZ Publish data migration.
• We are deliberately building a GPLv2 open-source product on Ibexa and copyleft is acceptable.
• We are doing architecture due diligence on Ibexa internals ahead of an upgrade or a content-model redesign.

Look elsewhere when:

• The stack is Laravel or a non-Symfony PHP framework — there is no integration path here.
• The intent is to consume it as a standalone persistence library. The README offers no install path other than "install Ibexa DXP"; there is no independent versioning contract outside the DXP release train.
• Legal/compliance cannot absorb a custom license review — NOASSERTION will block automated approval.
• You need community support or ecosystem depth: 3 stars, 0 dependents means zero third-party leverage. Support comes exclusively from the commercial subscription.
• You want generic PHP persistence — reach for Doctrine ORM/DBAL or Symfony's Doctrine bridge directly instead.

How to Pitch It (Stakeholders)

To executives: This is not a product we adopt — it is internal plumbing inside Ibexa DXP, published as a split repository. There is no incremental cost and no standalone ROI. The only real decision on the table is whether we license Ibexa DXP; treat this as a due-diligence line item in that evaluation, not a separate initiative. The commercial license requires an active subscription, so it is a recurring budget commitment, not a one-off.

To engineering: It is Ibexa's persistence layer — SPI definitions plus Doctrine/DBAL storage implementations. Do not vendor, fork, or pin it independently; track the DXP release train instead. Extend through supported custom field type storage rather than patching core. Expect schema migrations on major upgrades and budget regression testing accordingly. The dual BUL/GPLv2 license will trip license scanners, so secure legal sign-off before any code enters the tree.

On maturity: Low stars and zero dependents are not a health signal about the platform — Ibexa is a long-established commercial DXP with a regular release cadence. They are a signal about this repository: it has no independent community, no external consumers, and no support channel outside the paid subscription. Plan resourcing accordingly.