1 websites made with Remix

Not in the form these sites were built with. In November 2024 Remix v2 merged into React Router v7, which became the next major version of both projects — Remix’s full-stack features live there as framework mode. Remix 3, which shipped in beta in April 2026, is a different project that drops React entirely and builds on web primitives. So the name continues, but a site built on Remix v2 is on a lineage that now runs through React Router.

Use React Router v7 in framework mode if you want the Remix model — loaders, actions, nested routing, progressive enhancement — since that is where it is maintained. Next.js is the alternative with the larger ecosystem, more hosting options and more people who have already solved your problem. Remix 3 is worth watching but it is a beta and it is not React, so it is not a migration target for an existing React codebase.

It bet on web standards when the rest of React tooling was building abstractions over them. Forms post as forms, so a mutation works before JavaScript loads and still works if it never does. Data loads per route, not per page, so nested layouts fetch in parallel instead of waterfalling. Error boundaries are scoped to a route, so one failing section does not blank the page. Those ideas turned out to be right, which is why they survived the merge into React Router.

Shopify bought Remix in October 2022 and has kept funding the work instead of absorbing it — the React Router merge and Remix 3 both came out of that period. Shopify’s own storefront framework, Hydrogen, runs on React Router 7 rather than Remix 3, which is a reasonable signal about where the production-ready path sits. The practical effect for everyone else is that the team has been paid to keep working on it.

Next.js has the larger ecosystem, more deployment targets, and Server Components as its structural bet. Remix bet on web standards and progressive enhancement instead, with a simpler mental model — loaders and actions rather than a rendering-boundary system to reason about. Since Remix v2 became React Router v7, the honest comparison is React Router versus Next.js, and that one comes down to a choice between the smaller, more predictable model and the larger ecosystem.

Yes. A deployed Remix v2 application keeps running, and React Router v7 is a deliberate upgrade path, not a rewrite — the migration is mostly imports and config. The framework’s habit of leaning on web standards helps here too: the parts that do the work are forms, HTTP and HTML, none of which are going anywhere. The sites in this collection were picked for their design, and none of this history shows on the page.