Download websites that use BookStack

About BookStack

Documentation software rarely lives on a company's marketing domain. BookStack tends to appear on a subdomain, a staff portal or an internal knowledge base that happens to be reachable from the public internet, so the sites carrying it look unlike the rest of the Documentation field. As of October 2026 we detect BookStack on 340 sites.

The software behind that pattern is a self-hosted wiki written in PHP and published under the MIT license, with a first public release in 2015. Nobody arrives at it through a sales process. Someone inside the organization decided to run a documentation server, attached it to a database, and has kept it upgraded since. Detecting the platform on a domain therefore says as much about the team as about the stack: there is an operations or platform function with the autonomy to stand up a service and the discipline to write things down.

For a commercial researcher, that inference is the value. Self-hosted documentation is a reasonable proxy for in-house engineering capacity, and companies selling identity, backup, monitoring, managed hosting or developer tooling use signals of exactly this kind to separate organizations that build from organizations that buy. A security researcher reads the same list differently, as an inventory of internally focused applications that ended up exposed, which is a class of host patched on a slower clock than the public website beside it.

Detection here is inferential. We identify the platform from markup, asset paths and response headers on pages we can reach, so an install sitting behind single sign-on, an allowlist or a corporate network never enters the count. The figure should be read as a floor rather than an installed base. Release strings are not part of what we can extract for these hosts, so the dataset answers where the software runs and not which version is running.

A per-domain lookup answers whether one company you already suspect uses it. The downloadable list inverts the question. You get every domain where the fingerprint was seen, with the rest of the technology profile for each host attached, which is what you need to size a segment, watch it move over successive exports, or feed a prospecting pipeline that starts from observed behavior rather than from a purchased contact file.