Download websites that use Saleor

About Saleor

Headless commerce creates a measurement problem that its buyers rarely think about. When the storefront a shopper sees is a separate application talking to a commerce backend over an API, the backend stops leaving marks on the page. Saleor is built along those lines, and our figures have to be read with that fact in front of them.

The server side is Python, the licence is BSD, and the company behind the project is Saleor Commerce. The combination is worth spelling out. A permissive licence lets a company take the code, run it on its own infrastructure, rewrite the checkout and never appear in any customer list the vendor keeps. A commercial vendor exists alongside that, selling a hosted edition and support, so deployments split into the ones the vendor knows about and the ones nobody does. Counting either half from the outside is hard, and counting the second half is close to impossible.

2012 is the earliest year we can attach to the project, which is a long history for something usually described as modern commerce infrastructure. The age matters commercially. A platform with that much road behind it has real migrations in its past, and the teams that adopt it are developer led rather than marketing led.

As of October 2026 we detect Saleor on 4 sites. The figure is small for architectural reasons rather than commercial ones. A headless deployment can present a front end built in any framework, served from any host, with the commerce API on a separate subdomain or an entirely different domain that a crawl of the public shop never touches. What we catch is the cases that leave a recognisable endpoint, an exposed dashboard or a default asset path. Anything hidden behind a well built front end stays invisible to us, so the count is the visible remainder of a larger installed base.

For a researcher the useful question is not how many shops run it but which shops do, and what those shops have in common. Retailers running a self hosted Ecommerce stack behave differently from retailers on a hosted platform, and they buy differently too. Development agencies, payment providers, search and personalisation vendors and hosting companies all want that segment identified rather than counted, because the pitch to a team that owns its own commerce backend is a different pitch entirely.

A per domain lookup confirms one shop you already found. The list gives you the whole visible set at once, joined to country, top level domain and every other technology detected on the same host, and that join is what turns a handful of rows into an account list you can work.