🧡

final day of developer week 🥲 🔸 workers vpc — we’re building on our existing networking products to allow you to connect from the cloud directly to your worker, r2 bucket, etc to build multi cloud applications 🔸 save the date & preview: containers coming this summer to @cloudflaredev 🔸 workers ai: speculative decoding, expanded lora support, new models including gemma 3 and mistral 3.1 🔸 launchpad cohort #5 is here (welcome!) 🔸 and our own stories of how we built our CT log and NCMEC reporting on workers and next ship is always around the corner — stay tuned!

🎨💻Gain new skills from @selfteachme, a lead maintainer on the @redwoodjs core team and the host of the Compressed.fm podcast. With hundreds of websites & products built for top companies and artists, Amy’s expertise is one to check out at React Summit US!

look, it's simple:

I think it's time for complete backend systems on Cloudflare. We've got major components for a backend (all on the edge) - Database - Storage - Functions - Auth (missing, but simple with libraries) We'll miss a few DB specific features because of SQLite, but we're good to go!

.@boristane and @baselimehq joined @Cloudflare a year ago and they have delivered on the promise to give customers first class observability for workers

This is what a lot of people confuse. AWS and Cloudflare are infrastructure companies and root for companies building on us!

wait wait wait.... this looks awesome!

RedwoodJS has earned over 17,600 stars. 🌲📷 Our new repo, RedwoodSDK, is starting with 80 stars and growing. We're building trust anew, not relying on past stars. If you believe in our next chapter, we'd love your support. 📷 github.com/redwoodjs/sdk

We're close to reaching v1.0.0 Our thumb-suck estimated timeline is the end of April, but because we're developers you should probably double that? IDK. Can we get a PM to chime in?

Why would you use RedwoodSDK (over other frameworks): (I have a bunch of questions that would help validate my answer; but I'll just make some assumptions right now, so take this with a grain of salt!) RedwoodSDK: - built from scratch to run on workerd: SSR, RSC, and routing all "battle-tested" in the Cloudflare environment. - We are an RSC framework. Neither I or @__justinvdm have ill feelings towards RSC. We think it's brilliant, and we've embraced it fully and openly. - You have absolute control of everything you see on the page. The `render` function allows you to define the html document, even down to how React hydrates the client side Payload. Or not! The implication here is that you can just do static site rendering. - We believe in request/response, routing is server-side (Not a SPA -- but since you control everything you could enable this): This means you get sessions, HTTP headers, all the good stuff that makes the web fast and idiomatic. - There's no magic. No special "exported functions, data loaders, etc" which means no transpilation or things you have to learn. Just write Typescript. - You can colocate API responses and pages in the same "routes.ts" file. Co-location is one of the principles that makes React feel amazing. - The entire framework is not a lot of code. We are leveraging Web APIs, web standards, and browser-based technologies. No abstractions mean that you spend less time "integrating."

the best modern stack: Framework: @RedwoodJS SDK Auth: WebAuthn Queues: @Cloudflare Queues Hosting: @Cloudflare Workers/ Workflows Analytics: @Cloudflare Web Analytics Database: @Cloudflare D1 Storage: @Cloudflare R2 AI: @Cloudflare AI/ Agents KV: @Cloudflare KV Sessions: @Cloudflare DO WebSockets: @Cloudflare DO DNS: @Cloudflare Streaming: @Cloudflare Realtime video/ audio: @Cloudflare Cost: $0 / $5 (Pro.)

sometimes the tweet says it better than anything else:

@RedwoodJS is splitting into two paths: Redwood GraphQL (current framework) RedwoodSDK (new "personal software" framework) Current users: your app is now "Redwood GraphQL" and will get security patches while they build the shiny new thing.

We just love our new branding and direction! rwsdk.com/ #RedwoodSDK

⚡️@Prisma v6.6.0 now includes early access for @Cloudflare D1 Migrations! We'll keep the workarounds in our current RedwoodSDK standard starter, and switch over once they're stable. github.com/prisma/prisma/rel…

→ @vite_js + react + workers is the new default stack. and our vite plugin is now also GA which means you can run it in workerd → our opennext adapter is now in v1.0 and GA → you can use _headers and _redirects in workers (not just pages)

Fun Redwood fact: @mojombo shared a tweet when @Netlify released functionality like this, @appfactory said it "was cool," and Tom pitched him on RedwoodJS. This tiny feature was the spark for the entire framework, and it feels amazing to be right back here!