I’d like to support your comment nicdal.
There will always be bits that can be improved with the editor, improving AI tooling etc. But fundamentally without the improvements SSR would bring we will struggle to stay with Weweb, which would be a real shame, because the flexibility of this tool is game changing for our team.
Looking forward to hearing what’s next!
+1 for SSR !
at least BEFORE Q3 2026, so that we can wait with WeWeb.
And if it’s not planned for 2026, then let us know too
100% about needing SSR for SEO. We will have to cancel our Scale plan behind soon if that is not added to short to mid term roadmap.
Also I agree about stability needing to be priority. The AI features are not very helpful for any real, well built app other than in the prototyping stage only and it can be dangerous to use on production builds, even in staging.
Just a heads up for everyone looking for SSR and SEO. There’s Nordcraft. I considered it for my current project before I went with weweb since it doesn’t require SEO and you can build faster in weweb. Nordcraft is more capable than weweb and it does have excellent SEO and SSR but it’s also more technical than weweb. Nevertheless I liked wewebs editing experience more and that’s why I went with it, but with them currently focusing on becoming an AI first company I really start to regret that choice
Yes, PLEASE implement SSR, you can see how much the builders here want it…
Thanks! I’ve looked into Nordcraft a bit - besides my eyes hurting from the fact that it only has a ‘dark mode’ - I just don’t find it as intuitive to work with as weweb. And as much as we want ssr - I think the Figma plugin and AI to create formulas/functions within weweb are really great tools too. And although hard to compare, the support from weweb and the community both here, on youtube, and direct, has been really good. I’m keeping my faith for now!
Based on this response, I won’t be holding out hope for search engine features. Thanks for the update.
THIS. IS. THE. WAY.
SSR would be so a game changer for weweb.
Please consider it. I would also blend in perfectly with your AI strategy.
What is the benefit of generating awesome pages with WeWeb AI if they aren’t usable for SEO purposes?…
Hi everyone! Here is the latest roadmap update.
First off, apologies for not keeping you all updated, we’ll make sure to share updates more regularly moving forward.
From a roadmap perspective, our main focus today is helping new users succeed with the platform.
Since the launch of WeWeb 3.0 we’ve experienced massive traction and the feedback is now clear: the AI isn’t reliable enough, and, although building the frontend became a lot easier for most users, integrating that frontend with the backend remains difficult and often frustrating.
As a result, we are working on offering built-in backend capabilities that will let users manage databases, handle authentication, and deploy backend functions all directly within WeWeb’s UI.
A second-order benefit of this new feature set is that it will make it much easier for users to work securely with third-party data sources like Airtable or any SQL database - as calls to these data sources can be routed through a backend that’s automatically set up when linking them to WeWeb. This will bring WeWeb closer to market standards in terms of integration capabilities and, once it’s live, we plan to roll out many new integrations.
Finally, this backend will include full export and self-hosting options with no dependency on WeWeb. The entire, full-stack app will be fully portable and deployable anywhere.
As a complement to these new backend capabilities, we will also introduce key UX/UI improvements to make the application easier to read and enhance the experience of working with third-party backends like Supabase and Xano.
One of the most notable updates is a new tab-based layout that will allow users to quickly switch between the frontend environment (the Interface tab), the backend integrations (the Integrations tab), and the WeWeb backend (the WeWeb Backend tab, if you’re using that feature).
As we approach the final stages of this updated UX/UI, @flo will be sharing content to give you a sneak peek of what’s coming.
We are also continuing to invest in AI improvements, with the goal of making WeWeb the best AI-driven Visual IDE. This transition is taking time, we are not done yet, improvements are incremental, and we anticipate it will take another few months before the transition truly feels “complete.” That said, we’re making steady progress and the end result should offer the best of both worlds: an AI that’s genuinely helpful, and visual interfaces that give users full control over their applications.
Finally, we are dedicating time to improving existing features & elements, and fixing bugs based on the feedback we receive - as reflected in our regular release notes.
Regarding the other important topics mentioned in the community:
Figma: we released a proprietary WeWeb to Figma plugin 2 weeks ago, we are getting good feedback and will be working on improvements in Q4.
Branching: we have decided to postpone this for now. With our focus currently on delivering better backend capabilities, introducing branching would have deep implications across the product. We want to first stabilize the backend features before opening this complex topic.
Performances: we will be dedicating full-time resources to this at the end of the year and we expect to see ongoing performance improvements throughout Q1 and Q2 next year.
SSR: we are still evaluating whether this should be a priority. Currently, about 88% of use cases built in WeWeb don’t require SSR. That said, we’re seeing consistent demand for it, and we recognize that enabling it could drive meaningful value for users. I’ve read the community comments and really appreciate everyone who took the time to share their thoughts, your feedback is invaluable. We’ll make a firm decision before the end of the year, and if we move forward, SSR will be available towards the second half of next year. You’ll hear back from us on this in November / December.
Based on the broader roadmap direction outlined above, here is a detailed breakdown of the short-term roadmap:
AI Improvements
Improving file upload in the AI chat - support for uploading images and files to provide more context to the AI will go live next week or the week after.
Improving reliability and UX when building with AI (including coded components) - this is a fundamental focus that continues to keep part of the team busy. We’ll be releasing improvements incrementally as we go.
WeWeb back-end
Supabase
Elements
Chat - will go live next week or the week after.
OTP Input - will go live next week or the week after.
Select - ability to have icons or images displayed in the select will go live next week or the week after.
AI Chat - ETA end of October.
Gantt - ETA end of October.
Stepper - ETA end of October.
As always, feel free to share any questions or feedback in this thread!
Thanks for sharing. Looking forward to future builds!
If you need any external beta testers for the backend, I have an idea and would be happy to test it out!
I think that not having SSR, is a reason that a lot of people just choose not to build on WeWeb. So the 88% figure is accurate, but not correct. I pushed 2 projects on another teach-stack because of that.
Still excited to see the new elements.
I’m not sure about the backend stuff. Xano and Supabase seem very user friendly. But if you are trying to get on Webflow, you definitely need a backend functionality.
Are there any consideration for other out of the box elements?
i.e.: multilevel drop-down.
Also, I feel that the Stepper, better help the multi step forms. Now the multi-step forms are not at their best.
awesome! @flo will reserve a spot for you in the beta!
yes, agreed, if we had SSR this number would be different.
let us know if you have any other elements in mind besides the multilevel drop-down, and we’ll be happy to consider them.
thank you!
When can we test the chat component, even for a beta test?
You in theory can already pull it from weweb-assets and load it from the Dashboard
I don’t think its the same element
There is some work actively being done on it. If you pull the branch, it might be the thing 
But yeah, no way to be sure.
I think it might be the thing! Sadly I see no dropzones, which is a little disappointing. Nontheless, it looks okay.
The new hints are great though, definitely a step in the right (UX) direction.
New hints are really awesome. They would’ve made my understanding of “what-I-should-put-inside-this-variable” significantly easier
I am super excited about this. Thank you for this update @Raphael. 
Can’t wait to see some sneak peek videos.
