Download websites that use Varbase

About Varbase

Varbase is less a content management system in its own right than a set of decisions made in advance on top of one. A Drupal distribution bundles modules, configuration and a theme layer into a starting point, which means every site running it is also a Drupal site, and the information is in the narrowing rather than in the platform.

Which is exactly the kind of question a full technology census is for. Knowing that a site runs Drupal tells you very little, because the population is enormous and heterogeneous. Knowing that it was built from a particular distribution tells you who probably built it, roughly what it cost, which modules are almost certainly present and what the upgrade path will look like. As of October 2026 we detect the distribution on 214 sites in the CMS category, and the set is deliberately a subset of a much larger one.

The buying pattern behind a distribution is agency-shaped. Distributions are chosen by integrators standardising their delivery, not by site owners comparing products, and the practical consequence is that detected domains cluster around the agencies and institutions that adopted the stack. Vardot maintains the project, which has been developed in the open since 2014, written in PHP and released under the GPL v2 licence. Adoption follows the sectors that pick Drupal in the first place: government, higher education, media and large multilingual organisations with content workflows and accessibility requirements.

For a commercial reader that shapes what the list is good for. A hosting company can use it to find sites with a predictable resource profile and a known deployment pattern. A competing agency can use it to find properties built by somebody else and approaching a rebuild. A module or service vendor can use it to reach an audience already committed to the ecosystem. In every case the value comes from combination with other columns on the same row: the platform version, the web server, the hosting country, the analytics and the payment layer.

Detection deserves a plain caveat. A distribution leaves fainter traces than a platform does, because most of what distinguishes it is configuration rather than public markup, and a site that has been heavily customised eventually looks like plain Drupal to any external observer. Our figures should be read as sites where the distribution is still recognisable from the outside, which is a lower bound and is biased toward less heavily modified installations. Where the underlying platform is detectable and the distribution is not, the row will simply show the platform.

That is the honest shape of the signal, and it is still more than a lookup service will give you, because the question here is not whether one domain uses it. The question is who all of them are, what they were built with, and which of them are due for the next rebuild.