# WeWeb is full-stack šŸš€ **URL:** \ **Category:** New Releases\ **Created:** [April 8, 2026, 9:16pm UTC](https://community.weweb.io/t/weweb-is-full-stack/21002 "2026-04-08T21:16:51Z")\ **Posts on this page:** 20\ **Page:** 3
**Author:** ![Joyce](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/joyce/32/13232_2.png) [@Joyce](https://community.weweb.io/u/Joyce)\ **Post date:** [April 10, 2026, 9:50am UTC](https://community.weweb.io/t/weweb-is-full-stack/21002/44 "2026-04-10T09:50:39Z")
> [@fynn](#): > > please bring back the old logs filterā€¦ šŸ˜¢ hehe, Iā€™m screenshotting all the feedback and sharing the product team so they can explore possible updates in the coming weeks šŸ˜„ ---
**Author:** ![Corner](https://avatars.discourse-cdn.com/v4/letter/c/f0a364/32.png) [@Corner](https://community.weweb.io/u/Corner)\ **Post date:** [April 10, 2026, 10:19am UTC](https://community.weweb.io/t/weweb-is-full-stack/21002/45 "2026-04-10T10:19:51Z")
okay thanks @Joyce for your reply. Indeed, itā€™s not very intuitive but I understand the constraint behind it. Maybe you could display explicit hints or use cases somewhere e.g. ā€œYouā€™re using Supabase the old way ? Do thisā€, ā€œYou want to try Wewebā€™s backend ? Do thisā€ ---
**Author:** ![flo](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/flo/32/13260_2.png) [@flo](https://community.weweb.io/u/flo)\ **Post date:** [April 10, 2026, 10:22am UTC](https://community.weweb.io/t/weweb-is-full-stack/21002/46 "2026-04-10T10:22:46Z")
This is not an easy subject. Many users have also mentioned that logs are hard to read and make it difficult to understand what is happening. Thatā€™s why we transitioned to displaying workflows and allowing you to see results for every action. We are actually planning to add an expand button there soon to improve readability. If you wish to see data in the main panel now, you can add a **Log action** to your workflows to see the results there. However, I understand your frustration and know that adding log actions manually is cumbersome. I have a feeling that the priority for you is seeing what I call ā€œnetwork actions.ā€ Would a dedicated panel that displays all calls made and results received work for you? ---
**Author:** ![Corner](https://avatars.discourse-cdn.com/v4/letter/c/f0a364/32.png) [@Corner](https://community.weweb.io/u/Corner)\ **Post date:** [April 10, 2026, 10:25am UTC](https://community.weweb.io/t/weweb-is-full-stack/21002/47 "2026-04-10T10:25:43Z")
Quick question on the pricing (sorry idk if this is the place to discuss like this but maybe that will help others), Iā€™m building apps as a freelance and I have my clients. Iā€™m on the partner plan. What is your recommandation as a building and workflow pricing ? Should I build everything on my side, and then when itā€™s done, I transfer the project to my clientā€™s, who can only subscribe to a front-end only plan ? My point is, is it possible for my clients to pay only for hosting the app, as they donā€™t build, and on my side Iā€™m paying my partner plan so I can build. ---
**Author:** ![Corner](https://avatars.discourse-cdn.com/v4/letter/c/f0a364/32.png) [@Corner](https://community.weweb.io/u/Corner)\ **Post date:** [April 10, 2026, 10:27am UTC](https://community.weweb.io/t/weweb-is-full-stack/21002/48 "2026-04-10T10:27:38Z")
or maybe a little ā€œ+ā€ button below the log to add the log action and details in a handy way ? You keep your logic and the user is not frustated anymore, he can easily chose to add it or not ---
**Author:** ![Magicnetworks2010](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/magicnetworks2010/32/16152_2.png) [@Magicnetworks2010](https://community.weweb.io/u/Magicnetworks2010)\ **Post date:** [April 10, 2026, 3:38pm UTC](https://community.weweb.io/t/weweb-is-full-stack/21002/49 "2026-04-10T15:38:55Z")
When I perform custom authentication and save the API key as an environment variable, I always get the ā€œnot authenticatedā€ error. But the API call works in n8n. ---
**Author:** ![Joyce](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/joyce/32/13232_2.png) [@Joyce](https://community.weweb.io/u/Joyce)\ **Post date:** [April 10, 2026, 3:43pm UTC](https://community.weweb.io/t/weweb-is-full-stack/21002/50 "2026-04-10T15:43:32Z")
Hey Bastian šŸ‘‹ Would you mind creating a separate topic with some screenshots or a short video walking us through what you are trying to do and where youā€™re stuck or, if you believe itā€™s a bug on our side, create a ticket [here](https://support.weweb.io/?category=bug)? Itā€™ll make it easier for us to follow up and find a solution for you šŸ™‚ ---
**Author:** ![Slavo](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/slavo/32/13253_2.png) [@Slavo](https://community.weweb.io/u/Slavo)\ **Post date:** [April 10, 2026, 3:51pm UTC](https://community.weweb.io/t/weweb-is-full-stack/21002/51 "2026-04-10T15:51:54Z")
Hello! Your customer must have a paid seat plan, regardless if they develop the app or not. Regarding the development flow, there are two options. Both assume you have a Partner Workspace. 1. You can develop the app in your workspace. When ready, you can transfer the app to your customerā€™s workspace. There is an option for that in ā€œSettingsā€ of the project. You must be a member of your customerā€™s workspace. After you transfer their app to their workspace, they can either export and self-host it or purchase a WeWeb Cloud plan to host it on WeWeb. OR 1. Your customer invites you their workspace. You develop the app in their workspace. When ready, they can either export and self-host the app or purchase a WeWeb Cloud plan to host it on WeWeb. ---
**Author:** ![Antiokh](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/antiokh/32/2794_2.png) [@Antiokh](https://community.weweb.io/u/Antiokh)\ **Post date:** [April 10, 2026, 6:18pm UTC](https://community.weweb.io/t/weweb-is-full-stack/21002/52 "2026-04-10T18:18:52Z")
I was surprised seeing the release with the same imperfections Iā€™ve highlighted to @Aneeq. Some of them are very annoying: 1. When I use new ā€œparametersā€ property of the page url, I canā€™t see it as a variable. ![image (13)](https://us1.discourse-cdn.com/flex016/uploads/weweb/original/3X/8/d/8da8fd8774a2ef030fccb84683ebdee1be4a9e74.jpeg) 2. Iā€™ve found the collections, but I wonder, why canā€™t we access the new backend views similar to how we did it before? Do you wanna scare the old developers having two types of working with sources? Collections were the killer feature of WeWeb, unlike Webflow, Webstudio, Bubble or any other lowcode tool. The way to see all the data clearly. ![image (14)](https://us1.discourse-cdn.com/flex016/uploads/weweb/original/3X/d/f/dfdf0ff8f984b96fd2750aeebb41c1c81d1dc1a3.png) 3. I expect it to work for redirection, it has no ā€œnavigate toā€ option, so I need to work old way, from checking the previous step. When I open it and create a OnAfter workflow, thatā€™s not obvious hot to go back to upper workflow. ![image (16)](https://us1.discourse-cdn.com/flex016/uploads/weweb/original/3X/c/a/ca92b5bd23de200430b806c0fb8aeaa87628239d.jpeg) 4. You have 4 ā€œGear-typeā€ icons. The 6th feeling doesnā€™t help/ ![chrome_8WttpqlKCo](https://us1.discourse-cdn.com/flex016/uploads/weweb/original/3X/4/2/42252accd21022b56743deded62efcb0b83ea287.jpeg) 5. Thereā€™s no UI zoning. Project-specific actions are mixed with visual editor settings. Please move all vision-mode-changers at the same place, if the button ā€œpreviewā€ jumps to the top-right, leave it there. ā€œDeployā€ button can be on the left from ā€œPreviewā€, like in Bubble, because usually we preview before deploy. Also, you can extend the help with hotkeys. Please rely on key codes, not codepages (in Serbian and Russian hotkeys stop working). 6. My avatar now has no real meaning except when we work together with someone (I have no stats, how many users use this mode). It can open the settings, it will be more intuitive. You can move it with Undo/Redo to the left, near the ā€œHelpā€ button, extending ā€œUndo/Redoā€ to backend changes. 7. All editing-related stuff can be placed inside the editor canvas. Please zone the elements to ā€œproject-relatedā€, ā€œuser-relatedā€ and ā€œeditor-relatedā€. Some additional wishes: 1. If itā€™s possible, extend the canvas width switcher to make it possible to set custom breakpoints. Like in Webflow and Bubble. 2. Please update ā€œJS Collectionsā€ with a bug editor and fix a field overlap bug. ![image (21)](https://us1.discourse-cdn.com/flex016/uploads/weweb/original/3X/5/2/52b9cbedd118f322368e6a9794c9348c1c1d0a95.png) ---
**Author:** ![RPAL](https://avatars.discourse-cdn.com/v4/letter/r/85f322/32.png) [@RPAL](https://community.weweb.io/u/RPAL)\ **Post date:** [April 10, 2026, 6:20pm UTC](https://community.weweb.io/t/weweb-is-full-stack/21002/53 "2026-04-10T18:20:48Z")
![image](https://us1.discourse-cdn.com/flex016/uploads/weweb/original/3X/7/1/71a63cac77f47de5a703f302ae62c96b359473be.png) As a temporary solution could we at least get the old return format (below) as a toggle in the code editor settings? ![image](https://us1.discourse-cdn.com/flex016/uploads/weweb/original/3X/8/a/8a2b20fcdeee05bcb85f07c1e3138e6b34c97c22.png) Above is definitely better for readability than below. ![image](https://us1.discourse-cdn.com/flex016/uploads/weweb/original/3X/f/6/f6b962ef72a5124092b575eedaa534ed0b108b64.png) Or better solution, restore the old return format and if people want access to the raw response instead add some buttons like the other helpers (toggle, find, replace) to make it appear. Maybe even a copy button that copies the raw response to the clipboard. ![Screenshot 2026-04-10 111254](https://us1.discourse-cdn.com/flex016/uploads/weweb/original/3X/d/d/dd232e2005610dafdfa3afc7633b46533bdde839.png) ---
**Author:** ![Antiokh](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/antiokh/32/2794_2.png) [@Antiokh](https://community.weweb.io/u/Antiokh)\ **Post date:** [April 10, 2026, 8:13pm UTC](https://community.weweb.io/t/weweb-is-full-stack/21002/54 "2026-04-10T20:13:08Z")
Some news: 1. We donā€™t have a workflow editing option from the page settings. It means, If we have some redirects in ā€œon page loadā€, weā€™re no longer have an access to them and the page is ruined, including everything in it. 2. Some calls now return a veeery detailed error json, which is not useful at all, because before the update everything just worked. ---
**Author:** ![TechaSoftware](https://avatars.discourse-cdn.com/v4/letter/t/90ced4/32.png) [@TechaSoftware](https://community.weweb.io/u/TechaSoftware)\ **Post date:** [April 11, 2026, 5:12pm UTC](https://community.weweb.io/t/weweb-is-full-stack/21002/55 "2026-04-11T17:12:29Z")
This looks good, Iā€™ve had a quick use of it and Iā€™m impressed considering itā€™s only in Alpha. @Raphael @Joyce just curious, what features and improvements are the team going to be working on now? ---
**Author:** ![Yaj](https://avatars.discourse-cdn.com/v4/letter/y/eb8c5e/32.png) [@Yaj](https://community.weweb.io/u/Yaj)\ **Post date:** [April 12, 2026, 10:11pm UTC](https://community.weweb.io/t/weweb-is-full-stack/21002/56 "2026-04-12T22:11:24Z")
This man knows what the people want ---
**Author:** ![akram](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/akram/32/16102_2.png) [@akram](https://community.weweb.io/u/akram)\ **Post date:** [April 13, 2026, 7:49pm UTC](https://community.weweb.io/t/weweb-is-full-stack/21002/57 "2026-04-13T19:49:32Z")
I think this was migrated to the workflow tab? or am I missing something? ![image](https://us1.discourse-cdn.com/flex016/uploads/weweb/original/3X/e/6/e62aaeaeb6380a685e21931da3185a31f96dbb8b.jpeg) ---
**Author:** ![Raphael](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/raphael/32/13247_2.png) [@Raphael](https://community.weweb.io/u/Raphael)\ **Post date:** [April 14, 2026, 8:32am UTC](https://community.weweb.io/t/weweb-is-full-stack/21002/58 "2026-04-14T08:32:59Z")
Hey @TechaSoftware thanks for asking! Short term (April - May): - Improve the new UX/UI based on usersā€™ feedback. - Improve the quality of AI generation quickly (Iā€™m very excited about this, I believe it will work really well fairly soon thanks to the new AI system we built). - Add a few things that are missing in the new WeWeb backend: the ability to easily copy/paste data between environments (editor / prod / staging), the ability to import data easily (from a csv for example), automatically set up auth workflows & pages when a user sets up WeWeb auth and support for CRON jobs. - Improve support for workflows involving AI calls: add more native actions + give users the ability to either use their own AI API key or use our infrastructure to run AI workflows. - Improve the Stripe integration and add more integrations. - Resume work on ready-made elements. Then, the prioritization will mostly depend on user feedback, but here are a few things we want to cover in the months to come: - Roles & Permissions (RBAC) - Branching - Release a WeWeb CLI so users can do things in WeWeb from Claude, Codex, Cursor, etc. - Add audit features (performance, security, compliance, etc.) - Ongoing: bug fixes and improvements based on feedback (on AI, the WeWeb editor, the WeWeb backend, etc.) What do you think about this list? What would you like us to focus on? ---
**Author:** ![Farouk](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/farouk/32/15528_2.png) [@Farouk](https://community.weweb.io/u/Farouk)\ **Post date:** [April 14, 2026, 11:24am UTC](https://community.weweb.io/t/weweb-is-full-stack/21002/59 "2026-04-14T11:24:17Z")
Hey @raphael, Thanks a lot for the update, really exciting direction! The new version is honestly great, and building with WeWeb has become a real pleasure. One thing that would be amazing to include is database triggers. Theyā€™re key for handling data consumption and aggregation efficiently, especially for more advanced use cases. Also, weā€™ve noticed that some videos are starting to be published on YouTube, which is great. It would be incredibly valuable to have a full end-to-end tutorial showing how to build an app from A to Z using a pure WeWeb backend, covering all the main aspects. On my side, Iā€™m currently building with Xano, but my next app will definitely be built using WeWeb Tables really excited about the direction youā€™re taking there. Keep up the great work šŸš€ ---
**Author:** ![Magicnetworks2010](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/magicnetworks2010/32/16152_2.png) [@Magicnetworks2010](https://community.weweb.io/u/Magicnetworks2010)\ **Post date:** [April 14, 2026, 1:14pm UTC](https://community.weweb.io/t/weweb-is-full-stack/21002/60 "2026-04-14T13:14:05Z")
> [@Raphael](#): > > Hey @TechaSoftware thanks for asking! > > Short term (April - May): > > - Improve the new UX/UI based on usersā€™ feedback. > - Improve the quality of AI generation quickly (Iā€™m very excited about this, I believe it will work really well fairly soon thanks to the new AI system we built). > - Add a few things that are missing in the new WeWeb backend: the ability to easily copy/paste data between environments (editor / prod / staging), the ability to import data easily (from a csv for example), automatically set up auth workflows & pages when a user sets up WeWeb auth and support for CRON jobs. > - Improve support for workflows involving AI calls: add more native actions + give users the ability to either use their own AI API key or use our infrastructure to run AI workflows. > - Improve the Stripe integration and add more integrations. > - Resume work on ready-made elements. > > Then, the prioritization will mostly depend on user feedback, but here are a few things we want to cover in the months to come: > > - Roles & Permissions (RBAC) > - Branching > - Release a WeWeb CLI so users can do things in WeWeb from Claude, Codex, Cursor, etc. > - Add audit features (performance, security, compliance, etc.) > - Ongoing: bug fixes and improvements based on feedback (on AI, the WeWeb editor, the WeWeb backend, etc.) > > What do you think about this list? What would you like us to focus on? yes that sounds great, a cli would be great for weweb. is it plan to create also supbase ai functions for example that the ai create a new supabase table field or is it only plan for weweb database? ---
**Author:** ![Raphael](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/raphael/32/13247_2.png) [@Raphael](https://community.weweb.io/u/Raphael)\ **Post date:** [April 14, 2026, 2:11pm UTC](https://community.weweb.io/t/weweb-is-full-stack/21002/61 "2026-04-14T14:11:21Z")
Perfect! We are putting together a build guide video that will cover building a fullstack app from A to Z. It should come online in May. Noted for the db triggers! ---
**Author:** ![Raphael](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/raphael/32/13247_2.png) [@Raphael](https://community.weweb.io/u/Raphael)\ **Post date:** [April 14, 2026, 2:13pm UTC](https://community.weweb.io/t/weweb-is-full-stack/21002/62 "2026-04-14T14:13:25Z")
Thanks for asking! The first version will be WeWeb focused, then weā€™ll adjust depending on usersā€™ demand. But thinking outloud, I think it would probably make more sense to use both Supabase MCP & WeWeb CLI from your IDE / Terminal rather than looping everything through the WeWeb CLI. To be confirmed as we build it! ---
**Author:** ![Yaj](https://avatars.discourse-cdn.com/v4/letter/y/eb8c5e/32.png) [@Yaj](https://community.weweb.io/u/Yaj)\ **Post date:** [April 15, 2026, 4:51am UTC](https://community.weweb.io/t/weweb-is-full-stack/21002/63 "2026-04-15T04:51:50Z")
Are the new [integrations coming soon](https://www.weweb.io/integrations) going to be available for front end only as plugins? [Previous page](https://community.weweb.io/t/weweb-is-full-stack/21002.md?page=2) [Next page](https://community.weweb.io/t/weweb-is-full-stack/21002.md?page=4)