Download websites that use WebsiteBaker

About WebsiteBaker

Software of a certain age stops being chosen and starts being inherited. A site built on a CMS that was current in the middle of the last decade rarely gets rebuilt on the same platform, so what remains in the wild is surviving stock, kept because it works rather than because anyone would pick it today. WebsiteBaker belongs to that stock.

Released in 2004 and written in PHP, WebsiteBaker was one of the small template driven publishing tools that filled the gap between hand written HTML and the heavyweight systems which eventually took the market. The GPL v2 licence means there is no company behind it in the ordinary sense, no sales record, no renewal list and nobody able to say how many installations exist. For open source of this kind, a crawl is not one source among several. A crawl is the only census there is.

As of October 2026 we detect WebsiteBaker on 51 sites, and the honest caveat is that older PHP systems are identified largely through generator metadata, admin paths and characteristic asset locations, all of which an administrator can remove and a hardening plugin can strip. Hardened installations drop out of the count. The bias runs in one direction, so the real population is larger than the figure and skews toward installations nobody is watching, which is itself a finding for anyone thinking about security.

The commercial value sits in that last point. A legacy CMS still serving pages today implies a site nobody has rebuilt, an administrator who may or may not still apply patches, and an owner who has spent nothing on their web presence in a long while. Agencies selling migrations use lists like this to find rebuild candidates. Security researchers use them to size the exposure of an unsupported stack. Hosting companies use them to learn what their PHP customers are actually running before deciding which platform versions to keep supporting.

Assumptions about where this system is used circulate freely, and our country and top level domain fields are empty for it, so a regional concentration can be neither confirmed nor denied here. Anyone who cares about that should read it off the domains in the export instead of trusting folklore, which is precisely the kind of question a full list settles and a per domain lookup cannot even approach. Checking whether one site runs WebsiteBaker is a query. Knowing every site that does is a dataset, and only the dataset lets you size a migration market, plan an outreach campaign or measure whether a platform is fading or holding.