Checkout @RedwoodJS RWSDK. Been real happy with it as a Cloudflare first stack. If you want to live in SPA land you can have the use client side then workers are the SSR part.

We build a framework so powerful that we couldn't release it. It would literally destroy the web as we know it. We released it to a handful of companies... and we're allowing them to try it out slowly 'n surely to make sure that they do it responsibly. Just kidding, it's open source, it's rwsdk.com

This is agent-ci.dev, it runs the same native GitHub Actions Runner in a container. The difference is the control pane: Which is a local http server. So it never communicates with GitHub.com, because of this we can do all kinds of interesting things: 1. 0ms cache restores (copy on write mounts) 2. pause-and-retry on failures (bash injection in step.) 3. 100% compatible with GH actions. (just a control pane.)

It's called Janus. Two Workers in a monorepo, connected by service bindings. D1, R2, queues, workflows, browser rendering — all cloudflare native. Patrol runs every 5 min, alerts route to Telegram, and there's a dashboard built on @RedwoodJS for when you need to dig in.

Built with RedwoodSDK bawkblock.com/schematic/DA6y…

TLDR; GH actions, but for agents. ~0ms cache, retry-on-failure, insanely fast. Agents need validation. CI is the last defense. They shouldn't bother you unless everything is green! GH Actions is usually in the top-5 expenses for dev-teams. Add agents to that mix? It'll easily double. It's the wrong tool for the right job: Slow boot, slow cache, retrieving logs is token expensive for agents, the list goes on... So I built a tool with one amazing feature: live-reload for failures. Agent-CI is a local CI runner. I tweaked the control pane and mounts to provide 0ms caching, insanely fast boots. When a step fails it pauses, provides the agent with the failure, and waits for the agent to fix and retry just that step. It uses the standard GH Actions image (via Docker), but emulates the control pane via a local HTTP server. You don't have to change any of your existing GH workflows. Tighter loops. Greener builds. Less babysitting. (Demo below.)

RedwoodSDK's docs are now built in Redwood, featuring our "brown is the new dark mode theme." docs.rwsdk.com

Built with RedwoodSDK flareup.dev/

I’ve been building on @Cloudflare for the last 8 months. I can’t stop building, and I can't stop recommending it to others. Here's why. A Cloudflare building thread 🧵

Today was the 8-year anniversary of Cloudflare Workers launching and the 9-year anniversary of me joining Cloudflare.

i feel kinda validated. we had the lock-in discussion about @RedwoodJS on cloudflare a few times i felt pretty strongly that it's not an issue. there are great frameworks out there, and we don't need to be everything for everyone

Coming to RedwoodSDK soon!

Loving this, people coming together and saying "lets make it better", so freaking exciting Thank you team for starting this story Super happy on the 1.0 launch, will keep using and contributing 🥳

Awesome to see @RedwoodJS RedwoodSDK hit 1.0! rwsdk.com/ A whole new ethos, evolved from the old RedwoodJS roots, now optimized for AI, @Cloudflare, and a server-first approach, all with no confusing magic. Ask Claude Code to write your next web app with RWSDK and feel the difference!

👀 Redwood SDK 1.0 is out

Congrats. Used SDK in a university lecture while teaching web applications. The main reasons for choosing it were its simplicity, adherence to web standards, and how easy it is for students to grasp. Used with Cloudflare, you get a lot of batteries included. Finally it is v1

Criminally underrated ♥️

This is awesome! I have been using RedwoodSDK for a while and love its simplicity. Congratulations to the whole team 🧡

A simple framework for humans @RedwoodJS SDK is now 1.0 🥳 Server-first React on @CloudflareDev Congrats @appfactory @_mjmeyer @mojombo and all contributors (i guess me too)