You can't cheat the game. It knows how much you've invested. It won’t give you anything you haven't worked for.

The only "Effect" we have is on your productivity

I like this @RedwoodJS Haven't got a chance to try, but something I am excited to try soon! docs.rwsdk.com/core/database…

This is nice bc websockets take a little time to connect. Client side nav over websockets means super-quick nav without re-connecting AND server-driven UI updates for collaboration e.g. with Agents. 🏎️🏎️

A web where high value content is rewarded? Someone figure this out

At RedwoodSDK we pick the browser, the network, and the platform (@CloudflareDev) as our integration partners. We don't innovate, we extricate: So when you pick us you're picking standards - that you can carry forward for the rest of your career. We have an early preview of "databases on DO" available: docs.rwsdk.com/core/database… Complete with migrations and type safe SQL!

ngrok is such a mess, everyone should just switch to @Cloudflare tunnel already. I tried it last night and wow, no acc/tokens, no setup BS, it just works. never going back

you can just do things meow

I just deployed an app to Cloudflare with a single prompt! 🤯

👀 built on @Cloudflare

We disable right click on all RedwoodSDK websites so we're secure.

Coming soon: Client side navigation (ViewTransitions), rendered on the server, and transported over websockets.

Rewriting my side project stackblocks.app in rwdjs 😁

I'm impressed with how well RSCs with @RedwoodJS just works. RedwoodSDK is a pleasure.

Routing shouldn’t be magic. RedwoodSDK’s router is written like code — not inferred from folders. 🧩 Define your routes 🧱 Compose middleware 🧘‍♂️ Understand the full request lifecycle It’s not just clever. It’s clear.

One of our favorite parts of RedwoodSDK: Middleware doesn’t live in some deep folder structure. It’s colocated with your routes — so you can see the full request lifecycle, top to bottom, in one place.

You don’t need plugins or workarounds to run request logic. With RedwoodSDK, just write: That’s real middleware. Scoped, readable, and interruptible.

In RedwoodSDK, define auth, headers, or session logic right in your router. It’s composable, readable, and runs before your component renders — exactly where it belongs.

Interruptors in RedwoodSDK let you block or redirect a request before it hits your page. No hacks. Want to check for a session and redirect to login? Just return a Response — it’s that simple.