Download websites that use ContentBox

About ContentBox

Ortus Solutions did not build ContentBox for the open CMS market. The platform grew out of the vendor's own framework ecosystem and was aimed at developers already committed to that stack, so the install base reads less like a general content management audience and more like the customer list of one engineering community.

The Apache 2.0 license sits oddly with that shape at first glance. Anyone may take the code, and yet adoption stays inside a defined circle, because the cost of running this CMS is not the license but the server environment it expects. Choosing it means accepting a runtime that a shared host will not have configured by default and that a new hire is unlikely to have used before. Teams accept that trade when the surrounding application already runs on the same foundation, which is the normal path onto the platform and the reason the count moves slowly in either direction.

Our record lists JavaScript as the language for ContentBox, which illustrates what that field actually measures. A crawler sees what a page ships to the browser, not what assembled the page on the server. For a CMS whose interest lies almost entirely in its server side runtime, the language column describes the visible surface and should not be read as a statement about the backend.

As of October 2026 we detect ContentBox on 14 sites, a population small enough that every domain in the list is individually meaningful. Since 2012 the project has occupied a niche rather than competing for share, and a fingerprint here is a strong signal about the organization behind the site. An in house development team, a long lived application, and a deliberate decision to stay on a foundation the wider market moved away from.

The profile gives the list commercial value out of proportion to its size. Hosting companies that support the underlying runtime can see in one file which live sites depend on it. Consultancies and staffing firms working in the same ecosystem get a directory of organizations that still need those skills. Migration vendors get the inverse, a set of candidates with a well understood reason to move.

Detection limits apply and are worth stating plainly. A CMS that renders plain markup can be configured to reveal nothing, so our figure counts the sites we can confirm rather than every deployment that exists. Internal and intranet installations, a normal use for a developer oriented CMS, are outside the reach of any crawler. A per domain check confirms one site and stops there. The downloadable list is what lets you see the whole visible community at once, cross it against country, TLD and the other technologies on each domain, and watch whether the community is being maintained or quietly retired.