Download websites that use Redis

About Redis

Redis is not a web technology in the sense that most entries in this dataset are. A cache and in memory data store runs behind the application, on a private network, and a well configured deployment is invisible to anyone looking at the site from outside. The obvious question is how a site level dataset comes to list it at all, and the honest answer shapes everything else on this page.

Detection is inferential. We record Redis when a site leaks evidence of it: a framework or platform header that names the cache, session and queue artefacts that identify it, a build manifest or configuration file left reachable, an error page that spells out the backend, or an operator who publishes the stack themselves. None of that happens on a properly locked down deployment. The consequence should be stated before any number is quoted. Presence is evidence, absence is not, and the real installed base is far larger than anything a crawler can see.

With that framing in place, the figures are still useful. As of September 2026 we detect Redis on 249,790 sites, with 172,928 assigned to United States and the domain mix leaning towards .com. The population should be read as a sample of stacks that expose their backend rather than as a market share measurement. The sample is biased in a knowable direction, towards self hosted deployments, towards teams that publish their architecture, and towards applications whose framework advertises its cache layer by default.

Written in C and available since 2009, the store became infrastructure for session storage, rate limiting, queues, leaderboards and caching in front of a slower database, and Redis Ltd. now develops it alongside a managed cloud service and the hosted versions offered by the large cloud providers. Licensing has changed more than once over the project's life, and our record carries a single value, RSALv2 / SSPLv1 / AGPLv3, across the whole of it, so the terms covering any particular deployment have to be checked against the release actually installed rather than read off this page. No version data appears in our record, since a backend store has no reason to announce its release number to a browser.

Who needs the list rather than a lookup is worth spelling out. Vendors selling databases, caching layers and managed infrastructure use it to find teams already running the technology in a discoverable way, which is a warmer audience than a cold list of companies. Security researchers use it because exposure of the cache layer is itself the finding, and a population of sites that reveal their backend is a population worth studying on its own. Developer tool companies use co-occurrence with frameworks and languages to size an audience. In each case the value comes from the shape of the whole set and from how it changes between refreshes, not from confirming one domain, which any engineer could do faster by asking the team that runs it.