glad to read! what is your use case?
Hi Raphael, thanks for the update - sounds pretty awesome!
As for the backend capabilities, if I understand correctly this is like a builtin cms like webflow has, right? If I may suggest (if youāre not already familiar) I think one of the best cmsās out there is Craft CMS. And one of the things that make it so powerful is their āmatrixā content type. It allows for a crazy amount of flexibility from a content authoring perspective. Might be worth checking out!
Cheers
1 Like
@Raphael @flo we appreciate if we can have access to the beta of the human chat element so we can test from our side as we are in a hurry to test the streaming api as well as we will dedcate a streaming server to bypas the CORS, aslo to raise feedbacks .
Thanks
Hi Niels, thanks for your message. Itās going to be closer to an Airtable-style or built-in database solution than a CMS. We might add CMS capabilities in the future, but that would be a separate feature set, more along the lines of what Webflow or Craft offer - and only if we decide to support SEO-focused use cases, which is still under internal discussion.
hello @yma unfortunately we canāt provide access to a beta for this element, it will be released in production either this week or the next.
Ah yes, I wouldāve been surprised if it was a fully fledged cmsā¦ Iāve been looking into figuring out how to run and connect strapi to weweb - I can imagine people that want to keep their web app and āfrontā of the website like home/blog/etc all on weweb, it could be an interesting option - even if it means re-deploying static pages for seo purposes or in combination with the Cloudflare workaround. It could drastically cut development time if content authoring is taken care of already within the backend, which xano or supabase or air table cannotā¦ If looked into running craftcms headless but couldnāt get it working (yet). Not sure if there are any other (cloud based?) good headless cms options
I hope this 88% is not actually used as a reflection of this feature interest? The WWII survivorship bias chart springs to mind.
Everyone who needs SSR is just building elsewhere, such as myself. Iāve just used Cursor with Nuxt + VueJS and Iām impressed. I have a need for websites to rank on Google (who doesnāt?), so I simply couldnāt consider WeWeb for this type of task unfortunately, and I love using it.
I canāt plan on waiting this long in the future with a possible āQ3 2026ā. This feature is forever in ādiscussionā. With the pace of Ai now, it needs to move faster to keep up.
The 12% of users requiring SSR are most likely the ones like me who didnāt realise the platform was so limited in SEO initially. For most others now, theyāve likely done their research, read the forums, asked Ai what tools to use.
The frontend web space is far larger than backend dashboards. If WeWeb wants this piece, it needs to focus on it now, not next year.
5 Likes
@what.gift This is one of the most truly accurate and insightful posts I think I have ever read. Well done and agreed 100%.
2 Likes
To use Airtable as a backend and also have some sort of authentication for an app that I intend to self-host. Also, Iāve never ever tried the SQL capabilities before because my understanding was that that was mostly for smaller/internal apps, but now Iām curious about the SQL capabilities with the new backend as well to assess if I can use SQL directly as the database for my app (self-hosted).
@Raphael The select element needs to support server search trigger and return result or just expose a trigger like on search change so we can run an action to return results form the server instead of throwing all or using the select drop down element which is a hassle
1 Like
Please make sure that existing components are still working when releasing new components. For example the file upload was completely broken once the new version was released. Thanks in advance.
Pretty disappointed to see branching postponed again after several delays. As a freelancer with production apps, this is becoming a real bottleneck on multiple projects.
Iām dubious about prioritizing backend features over this - though I could be wrong since I donāt know your actual user base breakdown. But Iād imagine loyal production apps that have been around for a while bring in the most revenue?
I originally chose WeWeb for its ability to push boundaries and provide solutions rather than the limiting simplicity of other no-code platforms. I love your work and this platform brings me the most development joy ever. Thatās why this limitation is so frustrating.
You mentioned sharing tips from 20+ dev teams working without branching - definitely interested in those insights!
Thanks
4 Likes
Iād love to see Database select from supabase done in parallel, similar to how we are able to fetch collections in parallel. For my backend structure, I canāt really make creating collections work and have to stick to multiple selects or running it through an edge function. Would love to see it on the frontend for sake of build speed 
1 Like
You can probably build views in supabase from your queries and fetch these as collections.
Looking forward to have a select trigger to send to the backend a certain query, the select component is excellent but pushing a 20 or 30K record to select from is not ideal
We need a trigger on search change or typed or what ever to reload our data source with the query input
1 Like
Hi @light_poichich ,
A helpful way for me to ābranchā by duplicating your project and then publish it to a test.url.com or whatever. And after testing you place this into production by switching your DNS.
Also, Weweb confirmed that for the duplicated project you need to buy a new hosting plan, but you can cancel your paid plan on the old version and any remaining prepaid amounts will be credited.
Hello everyone,
Instead of sharing screenshots, I recorded a short video to walk you through the work in progress. In it, youāll see:
-
the new editor UI
-
the new backend tab with table creation
-
backend workflow creation
-
integrations
-
user management
Please keep in mind this is still a work in progress, weāre working hard to make it available as soon as possible.
Of course, AI will assist you by creating and editing everything directly.
I hope youāll enjoy the preview! Feel free to share your thoughts or ask any questions.
9 Likes
Looks great, is there a chance for the Rest API to have this backend feature?
Wow 
!!! Thatās a massive update youāre dropping !
Iā ve got so many questions 
Weāre going to need to understand how the backend workflows are going to work,
the pros & cons compared to a supabase backend for instance,
and the impacts on the costsā¦
For supabase, will we also have visual backend workflows ?
Or is it going to be reserved to the nodejs backend ?
How does that work ?
And, what about security ?
We need more answers to cover that this huge update
But that seems like great job, well done 
2 Likes
Very good indeed.
Looking forward to the arrival of this new interface and the other backend features. It makes everything much easier.
3 Likes