Download websites that use Cloudrexx

About Cloudrexx

The years around 2004 produced a long tail of PHP content management systems, many of them built by an agency that needed one for its own client work and then sold it to peers. Cloudrexx belongs to that generation, and the record still shows the pattern: an open codebase under GPL v2, a named company behind it in Cloudrexx AG, and a CMS label that stretches from a brochure site to an intranet.

A content system with a company attached behaves differently from a pure community project. Releases follow a commercial roadmap, support is something you can buy, and the typical installation arrives through a partner rather than through a download. Presence on a domain therefore implies a relationship, usually with an agency that builds and maintains the site, and usually under a retainer. The site owner may not be able to name the software running their own pages.

Operations are the other implication. The vendor runs the platform as a hosted service and keeps the servers, the PHP runtime, the database and the update schedule on its own side, so an agency buys an operated environment rather than a stack it has to look after itself. Hosting providers, security vendors and agencies pitching a replatform all want the same thing from an entry like this one: the list of domains where an ageing installation is still in production.

Geography is where care is needed. The vendor publishes on a generic commercial domain, and our record for Cloudrexx carries no country or top level domain breakdown, so we make no claim about where its users sit. Older write ups of this software circulate with a country of origin attached, and none of that is something the structured data supports. The honest answer is that the domain list is itself the evidence, and a reader who needs the geography can derive it from the rows instead of trusting a sentence written by somebody who never checked.

Detection limits are worth stating too. Recognition depends on markup, asset paths and generator hints that a determined integrator can strip, and a site whose front end has been rebuilt on top of the same backend can pass unnoticed, so the count is a lower bound rather than a headcount.

As of October 2026 we detect Cloudrexx on 121 sites. A population that size will not carry a market model on its own, and it does not need to. The value of a small, precise set is that you can work through all of it: check which domains are still updated, which sit on shared hosting, which belong to the same agency network, and which run alongside a shop or a booking tool that suggests a budget. A per-domain lookup answers one of those at a time, which is fine right up until the question is about the group.