RedwoodJS

RedwoodJS
Name	RedwoodJS
Developer	Tom Preston-Werner, community
Released	2019
Programming language	JavaScript, TypeScript
Operating system	Cross-platform
License	MIT License

RedwoodJS RedwoodJS is an open-source full-stack web application framework combining React, GraphQL, and Prisma with conventions inspired by Ruby on Rails, Model–view–controller, and Jamstack practices. It emphasizes developer productivity, opinionated project structure, and integration with cloud deployment platforms such as Netlify and Vercel, aiming to simplify building CRUD applications, serverless APIs, and single-page applications. The project was initiated by contributors connected to the Ruby and JavaScript ecosystems and has been shaped by conferences and talks at events like JSConf and React Conf.

History

RedwoodJS originated from efforts by engineers including Tom Preston-Werner and contributors from the GitHub and Netlify communities seeking Rails-like productivity for JavaScript developers; early work began around 2019 and was publicly promoted through meetups and presentations at Jamstack Conf and React Conf. Its early releases integrated technologies such as React, GraphQL, and Prisma while adopting deployment patterns from Netlify and Vercel; the project evolved through community-driven RFCs influenced by practices from Ruby on Rails and patterns discussed at Strange Loop. Over successive versions the framework incorporated features shaped by feedback from users at Startups and companies featured at TechCrunch Disrupt, and the roadmap has been influenced by contributors active in Node.js and TypeScript communities.

Architecture

RedwoodJS applies a monorepo layout that separates code into conventional folders for frontend and backend concerns, reflecting ideas from Monorepo usage popularized by Google and Facebook. The framework routes client interactions to a GraphQL API using Apollo or similar GraphQL servers, backed by a database layer managed via Prisma which itself connects to databases like PostgreSQL, SQLite, or MySQL. Serverless functions and edge deployment integrate with providers such as AWS Lambda, Netlify Functions, and Vercel Serverless Functions while build orchestration borrows patterns from Webpack and esbuild tooling used in Create React App and Next.js. Authentication and authorization patterns are commonly implemented with adapters to identity providers like Auth0 and Okta.

Core Concepts

RedwoodJS centers on Cells (data-fetching UI units), Services (backend business logic), and a clear separation between the "web" and "api" sides; these concepts echo design patterns from Model–view–controller and component-driven development popularized by React. Cells encapsulate GraphQL queries and map onto UI components similar to patterns discussed at React Conf and in literature from Kent C. Dodds. Services expose functions that call into Prisma and external APIs; these functions mirror approaches advocated in Domain-driven design talks at QCon. The routing layer uses file-based conventions inspired by Next.js and Ruby on Rails routing, while forms and inputs draw on accessibility guidance from WAI-ARIA and patterns highlighted by Inclusive Design 24.

Development Workflow

Typical development uses a local monorepo with hot-reloading front-end tooling from Vite or Webpack Dev Server and a local GraphQL server akin to setups discussed for Apollo Server. Database migrations are managed through Prisma Migrate and development databases frequently mirror production engines such as PostgreSQL; CI/CD pipelines are commonly configured with services like GitHub Actions and CircleCI to run tests and deploy to Netlify or Vercel. Debugging and observability practices integrate with providers and tools showcased at DevOpsDays and in talks from SREcon, while end-to-end testing strategies borrow from frameworks such as Cypress and Playwright.

Ecosystem and Tooling

The RedwoodJS ecosystem includes integrations for ORMs like Prisma, UI libraries such as Tailwind CSS, component libraries referenced at React Summit, and authentication providers like Auth0 and Okta. Tooling reflects interoperability with package managers like npm and Yarn, bundlers discussed at JSConf such as esbuild and Webpack, and testing tools from Jest and Cypress. Deployment adapters and examples are provided for cloud platforms including Netlify, Vercel, and the AWS serverless ecosystem, and community plugins mirror patterns showcased at Open Source Summit and Node Interactive.

Adoption and Use Cases

Organizations from startups featured at TechCrunch to engineering teams spotlighted at InfoQ use the framework for SaaS dashboards, internal tools, and marketplace backends that require rapid iteration and serverless deployment. Use cases often cited mirror examples from Ruby on Rails success stories and include prototyping MVPs, building admin panels, and integrating third-party APIs like Stripe and SendGrid. The framework’s conventions appeal to teams migrating from Monolith architectures or combining frontend-focused companies showcased at SmashingConf with API-centric teams that follow practices from API World.

Community and Governance

The project governance combines maintainers and community contributors who coordinate via platforms such as GitHub and discuss direction in community forums and chat rooms similar to those used by projects presented at Open Source Summit. Decision-making follows community RFC-style proposals reminiscent of processes used at Rust and Python core projects, with contributors from companies and independent developers who have spoken at JSConf, React Conf, and Jamstack Conf. The community organizes workshops, meetups, and conference talks; sponsors and participating companies include entities active in the Jamstack ecosystem.

Category:Web frameworks