RedwoodJS is a full-stack framework for building web apps with React, GraphQL, and Prisma — and it ships with opinions about all of them. Where other React setups ask you to choose a router, a data layer, and a deployment target, Redwood makes those choices for you. You follow its conventions, and in return you get a complete app structure that scales from a weekend project to a real product.
What makes Redwood different is its "cells" pattern. A cell is a component that declares its own data needs: what to show while loading, what to show when the query is empty, what to show on error, and what to show on success. That single idea removes most of the loading-state boilerplate that litters React apps.
yarn create redwood-app my-app
cd my-app
yarn rw dev
A cell that fetches posts shows the pattern:
// web/src/components/PostsCell/PostsCell.jsx
export const QUERY = gql`
query FindPosts {
posts {
id
title
}
}
`
export const Loading = () => <div>Loading...</div>
export const Empty = () => <div>No posts yet</div>
export const Failure = ({ error }) => <div>Error: {error.message}</div>
export const Success = ({ posts }) => {
return posts.map((post) => <h2 key={post.id}>{post.title}</h2>)
}
Redwood is a great fit for startups and solo builders who want a real full-stack app without assembling ten libraries first. Its generators scaffold pages, cells, services, and tests in one command, and its built-in Prisma integration keeps the database layer boring in the best way.
The limits are real. Redwood's ecosystem is smaller than Next.js, and its opinions can feel rigid if you already have strong preferences about your stack. It also assumes you are comfortable with GraphQL. But if you want to move fast with a complete structure, Redwood's opinions start to look like a feature, not a burden.
Try it once: generate a project, scaffold a cell, and run the dev server. The speed of that loop is the whole point of Redwood.
Top comments (0)