The modern web stack shouldn't be 15 different tools held together with duct tape. Redwood SDK integrates: 🔗 React (with Server Components) 🔗 Cloudflare One framework. Everything connected. No hidden magic.

Built with RedwoodSDK!

RedwoodSDK is going to backtrack a bit on our decision to use Prisma in the standard starter. There is absolutely nothing wrong with Prisma. But as a framework: 1. We do not want to select vendor-specific solutions. 2. Type generation is something we do not believe in. It's a source of support-pain and a source of failure. Therefore, we are going to introduce a fully typed solution for DO SQLite. This will form the backbone for our add-ons, and will ensure that we will remain backwards compatible no matter what choice you make for your ORM. You are still more than welcome to install Prisma or Drizzle or whatever floats your boat!

React Server Components let you render on the server without shipping JavaScript to the browser. In RedwoodSDK, they’re built in — no setup, no ceremony. It just works.

React Server Components used to feel abstract. Then we used them in RedwoodSDK. •Fetch data without wiring up APIs •No client bundle •Works locally and at the edge Sometimes simplicity is the magic.

RedwoodSDK gives you built-in support for React Server Components. That means: •Async DB queries inside your component •No extra APIs •Less JS shipped Here’s a quick demo of what that looks like 👇

Writing API endpoints. Fetching from your own server. useEffect to display the result. We’ve all done it. But React Server Components in RedwoodSDK, you just write:

RedwoodSDK makes React Server Components click: •Ship less JavaScript •Write async/await right inside your JSX •Skip the loading spinners It’s fast, clean, and you don’t need dedicated API routes, fetch calls, or useEffect.

"I can't tell I'm using a framework." That's the point. 💡 Write pure React components. Get full-stack superpowers. → No special APIs to learn → No framework-specific patterns → Just React, enhanced The best framework is the one you don't fight.

I have been using @CloudflareDev Turnstile in my production apps. And since we are all talking about it, here's a video showcasing various mode (yes, there is an INVISIBLE mode), and how to implement it. youtu.be/QKFiN_cyeMc

What if your router let you organize your way? In RedwoodSDK, routing is config-based — no fragile file system tricks. You stay in control. Come try it. Move things around. Break nothing.

You don’t write routes for the file system. You write them for your users. RedwoodSDK’s router is designed for how requests actually work. It’s one file. One lifecycle. Infinite flexibility. Just clean code.

Most routers force you to organize your project their way. RedwoodSDK doesn’t. With a config-based router, you control the flow — not your folders. Logic-first. Request/response modeled. This is what routing should feel like 👇

Well here you go... Cloudflare Sandboxes npmjs.com/package/@cloudflar…

Most routers feel like puzzles — one wrong move character and you’re using the wrong layout. RedwoodSDK’s router is a flowchart. You define the logic. You control the layout. Flexible imports. Clean configs. Request-response thinking. Build with confidence.

RedwoodSDK’s router isn’t file-based. It’s a single config that reflects the request/response lifecycle. 🗂️ Change route names — imports won’t break. 🧩 Routes are colocated where it makes sense. 🧘‍♂️ More flexibility. Less surprise. Your app, your structure.

now imagine a fullstack framework that makes it trivial not just to build but to deploy and scale with a simple ‘pnpm release’ if only there was such a framework 😉

♥️what I have been able to do w/ @Cloudflare & @RedwoodJS SDK! Here I upload @threejs library+module to R2, cache it, worker checks if in cache & serves it. Serving cached content = only paying cheap R2 costs + CF CDN speed! 600kb saved in worker! Example and repo in comments!

You don’t need to learn GraphQL. You don’t need magic files. You don’t need to fight your tools. You just need code that works, deploys fast, and makes sense. That’s what we built. Come try RedwoodSDK v0.1 — and tell us what you think: 🔗 rwsdk.com/ 💬 discord.gg/redwoodjs

We built RedwoodSDK to reduce friction and bring joy back to fullstack dev. You get everything you need — in one command. 🔹 React Server Components 🔹 Auth + DB 🔹 Deploy to the edge This is what shipping should feel like.