Download websites that use SDL Tridion

About SDL Tridion

Site counts are usually the point of a technology page. For SDL Tridion the count is close to beside the point. Enterprise content management does not sell in volume, and the number of visible installations is small by construction, because each one tends to belong to a bank, a manufacturer, a government department or a global brand running many sites and many languages out of a single content repository.

The system dates from 1999, is built on Java, and is now sold by RWS Group under a Proprietary licence. Longevity of that sort changes what the marker means. A platform of that age is never chosen by a startup and is never installed casually. Somebody ran a procurement process, paid for licences and integration, trained editors and built templates the organisation now depends on daily, and the replacement cycle for an investment like that is measured in strategy documents rather than in release notes.

So each row here is worth more than a row in a larger list. Competing platform vendors treat the set as a named account list rather than as market sizing. Systems integrators and agencies use it to find organisations whose replatforming budgets are large enough to be worth chasing for a year. Translation and localisation suppliers use it because a multilingual publishing stack implies steady translation volume, and the company that owns the platform sells language services alongside it, which itself tells you what kind of customer bought in.

Fingerprinting a platform like this is genuinely difficult, and the honest position is that the count runs low. Enterprise deployments publish through a separate delivery tier, frequently as pre rendered pages behind a content delivery network, and the markers identifying the authoring system can be stripped, renamed or simply absent from the output. Large organisations also keep authoring behind the corporate firewall where no crawler reaches it. What can be detected is what a public page still gives away, so the list should be read as a confirmed set of installations rather than as a census of the installed base.

As of October 2026 the confirmed set covers 242 sites. A per domain lookup will tell you whether one company runs the platform, which is useful once. The export gives the enumeration instead, every domain where the software is visible together with the surrounding stack, which is the form anyone selling into or researching enterprise content management actually needs.