A simple framework for humans. Server-first React, running on the Cloudflare platform. Simple to build. Easy to maintain.

it's time - v1.0 in five days rwsdk.com/
10
15
237
40,827
RedwoodSDK retweeted
Replying to @appfactory
owner of my company walked into my office today completely psyched about building a RedwoodSDK app as part of the next phase of a client engagement short ephemeral attention, long eternal ideas
1
2
4
358
🔥
Linkits.xyz is now live. Built with @RedwoodJS on @Cloudflare . Thanks @appfactory for this amazing project !
1
2
824
RedwoodSDK retweeted
1
13
1,214
RedwoodSDK retweeted
I really like Cloudflare's architecture. Durable objects are amazing; and to teach myself more about them I've been playing around with building "open durable objects" that targets Bun and Node.js. Same API; but self-hostable. (It's codenamed "sourdough" to deal with my emotions during a recent crypto scandle.) github.com/redwoodjs/sdk/pul… I'll be working on "open workers," and "open bindings" in the next few weeks. The goal is to get 1:1 API parity with Cloudflare. Obviously you won't have the scaling, edge network, and reliability of Cloudflare, but that's not the goal.
5
6
57
3,826
We ported @openclaw to Workers. - Sandboxed by default - Remote storage using R2 - Zero Trust for secure access - AI Gateway for LLM analytics, cost-analysis So many interesting things to dig into here. What a weekend ship!
Moltworker is a middleware Worker and adapted scripts that allows running Moltbot (formerly Clawdbot) on Cloudflare's Sandbox SDK and our Developer Platform APIs. So you can self-host an AI personal assistant — without any new hardware. cfl.re/4k6NUmp
70
166
2,161
323,195
RedwoodSDK retweeted
For the past few months I've been working on rewriting the Applywize tutorial @selfteachme wrote for RedwoodSDK from v0 to v1. I'm pretty close to done withit. 8 of 9 parts. Just working on the last part with deploying to Cloudflare. test2doc.com/docs/tutorial-1
6
1
4
1,230
RedwoodSDK retweeted
1st day
8
1
22
2,090
Our permanent stance: * RedwoodJS/SDK is an open-source framework. That is our only focus. * We do not endorse crypto. We will NEVER create a coin. * Our mission is to build the best developer tools, not to participate in speculative markets.
1
13
290
413,902
The why:
Replying to @wesbos
I guess you could say that, but that wasn't my intention. I did not create this coin. I was essentially "tricked" into claiming it because I was trying to prevent a total stranger from taking $30k for something associated with our brand. My initial instinct was defensive: I didn't want someone else leveraging our name for their own gain. The moment I claimed it, my DMs filled up with people suggesting I read Yegge’s posts on the subject. I’ve read his work for most of my life; there was a baseline of trust there. In that moment, it genuinely felt like a "windfall" for the project. I have never used crypto. I was ignorant of the mechanics, but I clicked a button and suddenly had $30k. Even then, I remained skeptical, but the pressure in my DMs was to "share it on X" to help it grow. As the situation progressed, more people reached out to caution me. They explained the mechanics of the trap: the creator waits for the "face" of the brand to grow the coin, then they dump their holdings, leaving the founder with an angry, burned community. I realized then that I had to put a stop to it immediately. I wanted to end it in the most direct way possible to protect the people who follow my work. Regarding the ~$100k in "bags," I haven't touched them. It would be ignorant and wasteful to dump them now and cause more chaos. I’ve left them alone. If there is a way to use those funds in the future to restore our reputation or help the community, that is exactly what I will do.
2
9
7,003
RedwoodSDK retweeted
🎨 Freshening up the portfolio for '26 🎨 Using @npm_i_shaders for shaders and @RedwoodJS as the framework. OKLCH colors allow accessible theme randomization on every visit inspired by the @37signals website
20
4
15
16,878
RedwoodSDK retweeted
In 1h30 we built a nuqs adapter for @RedwoodJS, with: - Client hook (read + write) - Server-side loading - Declarative client/server state location (with the shallow option) - Full type-safe linking (pathname + search params) 📺 Link and code below ⬇️
17
3
39
12,051
Buy crypto in ChatGPT ❤️ @bitvavocom Don't buy stocks by yourself, ChatGPT can help 🤝 Built with @RedwoodJS @OpenAI @calcom #AppsSDK #AppsSDKUI
16
3
12
6,903
and it is @aurorascharff doing crazy live coding again. This time it is about @RedwoodJS.
15
4
19
5,480
RedwoodSDK retweeted
There is critical vulnerability in React Server Components disclosed as CVE-2025-55182 that impacts React 19 and frameworks that use it. A fix has been published in React versions 19.0.1, 19.1.2, and 19.2.1. We recommend upgrading immediately. react.dev/blog/2025/12/03/cr…
166
1,019
3,923
2,587,106
RedwoodSDK retweeted
Been having such a nice experience with @RedwoodJS I dread learning new libs + frameworks but redwood was so easy, no magic and I just jumped right in composing stuff for implementing @CloudflareDev @OpenAI chat apps they set the bar high, this is how code should be written
RedwoodSDK is boring. It's tiny, predictable and composable. 1. Tiny: It's just 700kb of JavaScript, compared to hundreds for competing frameworks. 2. Predictable (/w zero magic): If the Typescript can't do it then we don't do it. 3. Composable: It's just a Vite plugin, a router, and DX around Cloudflare.
8
4
26
10,846
RedwoodSDK is boring. It's tiny, predictable and composable. 1. Tiny: It's just 700kb of JavaScript, compared to hundreds for competing frameworks. 2. Predictable (/w zero magic): If the Typescript can't do it then we don't do it. 3. Composable: It's just a Vite plugin, a router, and DX around Cloudflare.
20
1
67
23,162
RedwoodSDK retweeted
scratching an itch for my mac... what do i call it cloudwidget? widgetflare?
19
6
87
10,818