Download websites that use Ibexa DXP

About Ibexa DXP

Open the version column for most PHP content platforms and you find a long tail: abandoned major releases, sites frozen on whatever was current when the agency handed over the keys, a scatter of point releases nobody has touched in years. Ibexa DXP does not look like that. Across the 215 sites where we detect it as of September 2026 there are only 3 distinct versions in circulation, and 4 carries the bulk of them.

A narrow version spread on an enterprise platform is a procurement signal rather than a technical accident. Deployments that stay current are deployments that are supported, budgeted and upgraded instead of left to drift, which is what happens when a content platform sits inside a maintenance contract rather than on a hosting bill. The narrow spread also makes the population comparatively coherent, so an integration built against the current major release will work against most of what is out there, which is not a safe assumption for a mass-market CMS.

The rest of the record fits. Ibexa DXP is a Proprietary platform from Ibexa, written in PHP, and our earliest year on record for it is 2012. A commercial licence over a PHP codebase is a specific combination, offering the hiring pool and engineering culture of the PHP world together with the support contract, the roadmap and the invoice of a commercial supplier. Organisations pick that combination when they need someone accountable for the platform but still want to staff the work locally and cheaply.

The buyer profile follows from the count. A few hundred detected sites is not a failure to grow for a product of this kind, it is what a considered purchase looks like: sold to institutions, agencies and mid-sized enterprises, often through partners, and lived with for years afterwards. Each detected domain is therefore worth more attention than a detection of a free CMS, because behind it sit a budget holder, an implementation partner and usually a multi-site estate rather than a single page.

Checking a single domain tells you what one organisation runs. The full extract tells you which organisations run it, and that is the input for partner recruitment, for competitive displacement, for sizing an add-on market, or for research into how enterprise content platform choices cluster by sector and by country.

Two detection limits are worth stating plainly. Enterprise deployments are often heavily themed and served behind a CDN, and a decoupled front end can hide the platform completely, so the count is a floor rather than a census. Version strings, where we can read them at all, come from public artefacts and can be suppressed deliberately, which is common on sites where a security team has a say in the configuration.