Download websites that use RedwoodJS

About RedwoodJS

Framework adoption is one of the few things in a technology profile that behaves like a leading indicator. Tooling chosen for a new build tends to stay in place for years, so counting the sites on a young framework means watching a decision that has not finished playing out. RedwoodJS arrived in 2020, recent enough that most of what we see is first builds rather than migrations away from something older.

The project is MIT licensed and written in JavaScript, and it is a full-stack framework rather than a view layer. A site built on it comes with a defined project structure, a data layer and a build pipeline attached, so presence implies an application with a backend and a team that accepted a set of conventions in exchange for not assembling the pieces itself. A brochure site does not end up here by accident, and neither does a page someone dragged together in a builder.

Detection deserves an explicit caveat. A compiled frontend does not announce its framework the way a content management system announces itself in a meta tag. The available fingerprints are build output, asset naming, runtime globals and error signatures, all of which a bundler can flatten and a custom deployment can hide. Counts for frameworks of this kind are lower bounds, and the gap between the visible and the real population is wider than it is for server-rendered software.

As of October 2026 we see RedwoodJS on 81 sites. The absolute figure matters less than its composition and its direction of travel. Developer tooling vendors, hosting platforms and component library authors use lists of this sort to decide whether a framework has crossed from enthusiasm into production work, because the domains attached to it can be inspected: you can see what those companies are, roughly how large they are, and what else they run beside the framework.

Frameworks in this age band can also stall, get absorbed into a successor project or lose their maintainers, and a single snapshot cannot tell you which is happening. Repeated observation of the same population can, which is an argument for treating a framework list as a time series rather than a fact.

Recruiters and consultancies read it from another angle, since a framework choice describes a team's skill profile more reliably than a job advertisement does, and an ecosystem this young is small enough that the list approaches a directory of the people working in it. None of those questions can be answered one domain at a time. Each is comparative by nature, a matter of how many, of what kind and against which alternatives, which is precisely the shape a downloadable list has and a lookup does not.