The Future of Redwood Launches Today

Hello everyone!

It’s been far too long since you last heard from me. As some of you know, last October Tom, DT, and I began fundraising for PWV, which became an all-encompassing effort and led to many months of my silence here. The good news is that PWV is doing well, and I’m now a full-time VC! (pros/cons :sweat_smile:)

I’m no longer leading the Redwood project or active on the Core Team, which I’ll explain further below. I’d still love to stay in touch. I can’t help with Redwood anymore. But if you ever want to talk startups, have intros to founders, or want to catch up, reach out: david@pwv.com

Redwood Changed My Life

I hope it changed yours, too. I’m so grateful for Redwood and each of you in this community. It was a defining inflection point for me. From day one, Redwood has always been both a codebase and a collaborative community. Our culture emphasized generosity and gratitude: we believed (and proved) that by helping each other succeed, Redwood itself would be successful. You returned that trust many times over: investing your time, contributing your talents, and building your livelihoods on Redwood.

Thank you. :heart:

I still can’t believe we built a brand-new framework that so many people used to create real apps, products, and even entire startups. Some of you launched ventures, raised funding, and hired people from this community—people who themselves “leveled up” through contributing. It’s all amazing. But it’s the relationships and friendships we’ve formed that mean the most to me. Projects come and go; people remain.

I want to recognize everyone who has served on the Core Team, legends each and every one:
@rob @peterp @alicelovescake @giannelli.tech @ahaywood @ajcwebdev @PantheRedEye @chrisvdm @clairefro @danny @dthyresson @dom @forresthayes @Josh-Walker-GM @keith.t.elliott @kimadeline @KrisCoulson @noire.munich @bitshift @Robert @realStandal @simoncrypta @Tobbe @arimendelow @orta @ninasong (did I miss anyone?!?)

And none of this would have happened without you, @mojombo, whose drive to create opportunities for others is truly limitless. Thank you, Tom, for making such a huge impact on so many through your vision, ambition, and generosity!

So, What Happened?

You’ve all seen the milestones achieved across our community—there’s so much to celebrate. At the same time, we never quite reached “escape velocity” to make Redwood self-sustaining. We pivoted to big ideas, like adopting React Server Components (RSC) early to stay on the leading edge. That turned out to be as challenging as it was promising. Morale suffered with what became the long grind of 2024, and it became clear Redwood needed focused leadership right when we founders were being pulled elsewhere. Despite heroic efforts from the Core Team—especially Tobbe—the RSC milestone remained “just a couple of months away” for over a year. It’s the builder’s siren song: you keep pushing, hoping the next breakthrough is near, until your team and momentum break first. It became clear we needed to take a radically new approach.

Redwood’s Next Epoch (for realz this time)

Enter Peter! A Redwood founder from the early days, he rejoined us last September as a Core Team member after building his own startup on Redwood. He’s now leading Redwood not only as an open-source project but as a stand-alone company! He has an evolved vision for Redwood’s future—one rooted in the original ethos we’ve always cared about with new ideas for what it can become.

Things got quiet because we didn’t have a clear plan yet, and we didn’t want to sound any alarms before we knew which direction Redwood would take. That process took longer than expected. Apologies for the radio silence. The good news is that Peter has been steadily prototyping and has recently hit some exciting milestones (see links to announcements below). Yes, there’s risk ahead and more radical change in store, but it’s backed by a solid foundation and a dedicated team. Regardless, please know there is still an open invitation to participate, collaborate, and shape Redwood’s future if you wish.

Next Steps

To learn more, you’ll want to read the announcement @peterp posted on the RedwoodJS home page:

Today, we’re sharing an important step forward for Redwood. To achieve our vision of empowering the next generation of personal software, we’re aligning our efforts around two clearly defined paths: Redwood GraphQL and Redwood SDK.

From the start, RedwoodJS was built to simplify full-stack web development. We’ve seen incredible growth and community enthusiasm, but it’s clear we have an opportunity to pursue a broader challenge: enabling people to build, own, and distribute their own software without the constraints of traditional SaaS.

To fully pursue this vision, we’re launching Redwood SDK, a new framework that will become the foundation for this personal software revolution. We’ll be sharing more about this in the weeks to come.

The full announcement is here:

Then you should dive in to the new project docs and join the conversation on Redwood’s Discord Server:

Over to you, Peter :rocket:

This project is no longer in my (or Tom or Rob’s) hands. I trust Redwood will thrive under my friend @peterp’s leadership. I can’t wait to see the next chapter of Redwood’s journey—and I hope you’ll join him (and each other) in writing it.

Stay the course,
David

6 Likes

So excited to try this out!! Especially excited for the lack of framework magic - when it works, it is indeed magical, but anybody that’s dealt with bugs in any framework knows how obfuscated those errors can get.

And I love this page, it’s so pleasant to look at and is such a beautiful sentiment: RedwoodSDK | The JavaScript SDK for Cloudflare Workers

2 Likes

RedwoodSDK looks amazing. Can’t wait to see it evolve.

3 Likes

Hey David and Folk,

I just want to thank you for Redwood. While I haven’t helped out I have appreciated it a great deal from a distance as something to root for, learn from and use for my personal experiments in hopes of using it for a real personal project someday. I will still monitor and hope to help out at some point. Mainly I just wanted to say thanks both for it and for your communication here. It’s good to see both of these paths as options going forward.

Be well!

2 Likes

Man totally bummed about this. While I get everything is a business some of us just want to work and not go on a multi year journey of development with you (again).

Guess it’s time to start saving huge Vercel bills.

I can see how you would feel that way. And, by the way, we absolutely don’t take your trust in us for granted! Thank you.

However, if that’s your take away then there’s likely something wrong with our messaging.

  1. If you’re using Redwood today, just keep using it
  2. SDK is exciting and, frankly, something I see as becoming complementary
  3. All the progress and changes in motion will create more opportunities over time. For everyone.
1 Like

I find this change tremendously exciting, and it seems like a really good time to be doing it.

I wonder if this will clear the way for a potential for multiple choices on the web side

I’d like to contribute to the website page at https://redwoodjs.com/ because I think it should be easier for people to get to the GitHub - redwoodjs/graphql: RedwoodGraphQL page

While you can click on RedwoodSDK you can’t click on the Redwood GraphQL (I eventually figured out to click on the v8 button)

I can’t be the only person to show up and want to get to the old RedwoodJS easily

Thanks for Everything Everyone (who are leaving) and Thanks for Everything Everyone (who are new&staying)

Al;

2 Likes

@thedavid Kudos to the great work you + team does.

Please don’t take this the wrong way, Redwoodjs to me represents a brutalist way to focus on shipping value to customer and none of the drama that comes with frameworks.

Could you please provide a yes or no whether there will there be a Redwoodjs v9 before I decide on switching to a custom solution with fast-api & react for my current + next projects?

1 Like

I’m no longer developing Redwood, so don’t take my understanding as the actual plan. Here’s what I know and what I can deduce:

  1. Redwood (now “Redwood GraphQL”) will continue to be maintained and releases are still happening
  2. There is current work planned to make it easier to maintain and consume the repo/code (Peter calls this the “unbundling” project; separating things like Storybook, Jest, individual auth providers, etc.)
  3. There are no new features planned
  4. There will be a future opportunity for the repo to have a community leadership team

My answer = Yes
Given items 1 and 2, I assume there will need to be a v9; dependencies will have major version, breaking changes and the unbundling work will likely change package.json (e.g. likely will need to be more explicit about which Redwood packages installed).

But if you’re looking for new features in Redwood GraphQL v9, that’s unlikely. The feature “development branch” is now happening in the Redwood SDK repo.

However, if item 4 happens in the future, that could result in new features for Redwood GraphQL.

For anyone with an existing Redwood project, here’s my advice:

  • don’t change anything right now; stay the course with the current code and codebase
  • over time, play around with SDK… let it mature and stabilize
  • if/when it’s time to migrate (either to SDK or something else entirely), it will be obvious and an efficient path will be clear

Should you start a new project with Redwood GraphQL? That’s a more nuanced question. It sounds to me like it’s a tool you currently use with confidence to “ship value to customers.” If that’s the case, and it’s good enough, then I won’t discourage you from using it nor encourage you to learn something new.


Helpful?

1 Like