Download websites that use Kentico CMS

About Kentico CMS

Enterprise content management is bought through a procurement process and then lived with for a decade, and the outside view of Kentico CMS shows what that looks like. A site running it was not set up by its owner over a weekend. Somebody wrote a requirements document, somebody compared vendors, and somebody signed a contract with Kentico Software.

The platform sits firmly on the Microsoft side of the web. Written in C# and running on .NET, Kentico CMS combines content management with commerce, campaign tooling, and customer data in one product, and Kentico Software has sold it since 2004. Buyers are typically mid-sized and large organizations in regulated or process-heavy industries that need editorial workflow, multilingual content, and integration with systems they already run on Windows. A detection therefore implies a stack, a hosting arrangement, and usually an implementation partner, none of which are visible from a domain name.

Sites in this population also cluster differently from the mass market. Where a small business owns one domain, an organization running an enterprise CMS often runs many: country sites, campaign microsites, portals, and product sub-brands, frequently on the same license and the same template set. Counting detections and counting customers are different exercises, and for enterprise software the gap between them is wide.

Version data is where the population becomes interesting. Across installations that expose one we distinguish 33 versions, and 4.0 (build 4.0.3328) is among the strings that keep recurring. Old builds staying in service is the normal condition of enterprise deployments rather than a scandal, because upgrades are projects with budgets attached and a heavily customized install resists them. For an integrator that backlog is a pipeline. For a security team it is exposure. For a competing vendor it is the moment a replacement can be proposed with a straight face.

Two limits apply to reading any of it. A version is recorded only when an install reveals one in headers, asset paths, or generator markup, and hardened enterprise deployments strip precisely that, so the breakdown describes the visible subset rather than the estate. The product has also been through a rename and a generational shift toward its newer experience platform, which means version strings do not line up neatly with product names and are better treated as fingerprints than as a release history.

The commercial question that follows is who else runs it. Kentico Software knows its own licensees, since the product is sold under a Commercial agreement, but nobody outside the company holds that list and the licensees are not identifiable from any registry. A .NET agency looking for migration work, a connector vendor sizing an addressable market, and a competitor planning a displacement campaign all need the same thing: the population, not a verdict on one domain. A per-domain lookup confirms a site you already suspected. A downloadable list surfaces the ones you would never have thought to check.