Download websites that use OpenUI5

About OpenUI5

An open source licence on a framework published by a large enterprise software company is not a giveaway, it is a funnel. OpenUI5 has been published under the Apache 2.0 licence since 2013 by SAP, and anyone is free to take it. Almost nobody does unless they are already building against the vendor's business platform, because the control library, the layouts and the data binding all assume the shape of data that platform produces.

The dependency makes this fingerprint far more informative than a front end choice usually is. Detecting JavaScript frameworks code written in JavaScript normally tells you about a development team's taste. Detecting this particular framework tells you about a purchasing decision taken elsewhere in the organisation, at a scale where the web tier is a rounding error in the contract.

As of October 2026 we detect OpenUI5 on 110 sites, and the figure has to be read as the visible edge of something much larger. Applications built this way are overwhelmingly internal: procurement screens, approval workflows, warehouse and finance tooling, all behind corporate authentication on hostnames no crawler will resolve. What surfaces publicly is a narrow band of outward facing work, meaning supplier registration portals, customer self service areas, careers and application pages, and public sector services that had to be reachable from the open internet.

For anyone selling into that world, the narrow band is still the most dependable public signal available. An organisation exposing an application built on this framework runs the vendor's platform inside, employs or contracts developers who work in that ecosystem, and has a budget cycle attached to both. Consultancies and system integrators build pipelines from exactly this observation. Competing platform vendors use it to identify accounts worth attacking and to judge how deep the incumbent sits. Recruiters use it to find the teams. Analysts tracking enterprise software adoption need a public measure of something the vendor never publishes as a customer list.

Detection is inferential and imperfect, and the shape of the error is worth knowing. The open framework and the vendor's commercial edition share front end code, so the two are not always separable from outside, and a heavily themed or bundled application can rename the assets we match against. We record no version, country or suffix concentration for this technology, so the export supports questions about which organisations rather than about which release. A per-domain lookup tells you that one portal was built this way. The list tells you which organisations across the web expose that stack at all, and the aggregate is where both the commercial and the analytical value sits.