Download websites that use Neos CMS

About Neos CMS

A content management system is usually picked by the agency rather than by the client, and it stays for as long as the relationship does. Neos CMS sits in the CMS group as a build decision rather than a purchase, chosen by developers who wanted to define content structures themselves instead of accepting someone else's. As of October 2026 we detect it on 919 sites.

The project appeared in 2010, is written in PHP and is released under the GPL v3. The platform runs on its own application framework and keeps content in a repository model that separates structure from presentation, which is the property agencies actually buy, since the same content can drive a website, an application and an export, while editors work inline on the page instead of in a form somewhere behind it. Ambition of that kind has a cost. Implementations are developer led and agency priced, so the detected estate leans toward institutions, publishers, universities and mid sized companies rather than toward the long tail of small sites.

Version data shows how those builds age. We resolve 29 distinct version strings across the installs that expose one, and the reading returned across a broad part of the footprint as of October 2026 is 8.3. A spread of that width, in a platform that supports only a handful of branches at a time, means a real share of sites are running builds nobody has touched since launch. That is what tends to happen when a project ships, the retainer ends and the agency moves on to the next client.

Caveats belong beside those numbers. Version strings come from generator metadata and asset paths, and an operator can strip both, so a portion of installs resolve as present without a version. Detection is also inferential on heavily customised builds, where templates are written from scratch and little of the default markup survives, so the site count is a floor rather than a total.

Anyone selling into this estate needs the estate itself. Competing content platforms and headless vendors treat an ageing on premise installation as a replatforming opportunity, and replatforming programmes are built by counting sites and sorting them by version, country and top level domain. Agencies deciding whether to invest in the skills want to know where the platform is concentrated and whether the base is growing. Security teams want the version distribution, because an unmaintained content management system with an editing interface exposed to the web is a target worth mapping. Checking one domain tells you what one site runs. Everything above requires the population.