Download websites that use Sitepark InfoSite

About Sitepark InfoSite

Sitepark InfoSite belongs to the class of software that gets bought rather than adopted. Nobody installs it after reading a weekend tutorial. Software like this arrives through a procurement cycle, gets configured by the vendor or a partner agency, and then runs quietly for years inside an organisation that has no reason to advertise which content management system it settled on. Sitepark has been shipping the product since 2005, which places it in the generation of Java systems built around editorial workflow, template governance and long support horizons rather than around developer fashion.

Procurement software of that kind is hard to count from the outside. As of October 2026 the number of hosts in our index carrying a Sitepark InfoSite fingerprint stands at 1. A figure that small should be read as a floor rather than as a market measurement, because almost everything about this deployment model works against public detection.

Consider what has to survive for a match to happen. An on-premises Java CMS is normally fronted by a reverse proxy or a caching layer that rewrites headers, its templates are hand built for the customer so the default markers get designed away, and a fair share of installations sit on staff portals and intranets that a public crawl never reaches. The license is Proprietary, which means no package registry trail, no public repository and no download counts, so the web-facing fingerprint is close to the whole of the visible evidence.

Version data behaves the same way, and in a more useful direction. A single version string is all we hold for Sitepark InfoSite, and the value we record against it is 5. On a proprietary on-premises CMS an upgrade is a funded project rather than a background package update, so version strings are sticky, and a stale one is a signal about the customer as much as about the product.

The vendor's own product page for InfoSite is published in German, which points at a German-speaking buyer base rather than an international one, although a company's home country is not something we would read out of a listing page. For a competing CMS vendor, a systems integrator or an agency that lives on migration work, the headline count is not where the value sits. The question is which specific hosts matched, what version they reported and what else runs alongside, because a niche of this size is worked one account at a time rather than by segment. A per-domain lookup answers whether a site you already care about runs it. The downloadable list answers the opposite direction, which is to hand over every matched host in the index so that a target set can be assembled without knowing the domains in advance.