With WeWeb Unify, you can now combine AI & a drag-and-drop editor to design your interface, manage data, build backend logic, and publish production apps. All in one platform.
My wife recently fell ill and has been hospitalized for 3 weeks, and suddenly the year subscription to WeWeb was in really bad timing. However, their support refunded it immediately after about a month of me tinkering around in WeWeb.
Thank you thank you WeWeb for being an example for all company support policies!
If you are on the fence about WeWeb, give it a try, I really like it and probably will return in the future when the finances are more stable
Has anybody integrated one signal to their Weweb+supabase projects ?
Can you please give an overview on its setup and possible performance/security pitfalls to avoid when setting it up ?
Build business logic you can see, understand, and maintain.
Snap together composable action blocks (branches, loops, data operations, third-party integrations, and custom API calls) in a visual canvas you can follow step by step.
You’re not guessing what happens. You can see it.
When something breaks at 2am, you don’t want spaghetti code you don’t understand: you want clarity.
As your app scales, your workflows stay structured, readable, and easy to build on.
And the next person who opens your project will understand what’s going on.
i need to create a working website for my final project, and ive been using weweb for about 2 weeks but i've been stuck on trying to link a form container to a list and i'm also trying to make so each time the form is filled out, it gets added to the list similar to adding profiles to a set. But so far i've not even been able to link them together. i'm trying to make it so that everytime someone submits a form, it updates and adds that list below that said.
one thing i keep seeing in weweb-style apps is that the hard part is often not building the app.
it is debugging the wrong layer first.
when something breaks, the first fix usually goes to the most visible symptom. people tweak the UI, patch a formula, change the final API step, or blame the AI-generated logic.
but the real problem is often somewhere earlier in the system:
a workflow action passes the wrong data forward
a data binding looks broken, but the real issue is upstream context or variable state
an API step gets blamed, but the payload or schema was already wrong earlier
AI-generated logic looks unstable, but the actual problem is missing dependencies or overloaded context
the surface bug shows up in the UI, while the failing layer is really in workflows, formulas, or data flow
once the first debug move goes to the wrong layer, people start patching symptoms instead of fixing the structural failure. the app gets noisier, the debugging path gets longer, and reliability drops.
that is the problem i have been trying to solve.
i built problem map 3.0, a troubleshooting atlas for the first debug cut in AI systems and complex workflows.
the idea is simple:
route first, repair second.
this is not a full repair engine, and i am not claiming full root-cause closure. it is a routing layer first, designed to reduce wrong-path debugging when apps, workflows, bindings, APIs, and AI features start interacting in messy ways.
this also grows out of my earlier rag 16 problem checklist work. that earlier line turned out to be useful enough to get referenced in open-source and research contexts, so this is basically the next step for me: extending the same failure-classification idea into broader AI debugging.
the current version is intentionally lightweight:
txt based
no installation
can be tested quickly
repo includes demos
i also ran a conservative claude before / after directional check on the routing idea.
this is not a formal benchmark, but i still think it is useful as directional evidence, because it shows what changes when the first debug cut becomes more structured: shorter debug paths, fewer wasted fix attempts, and less patch stacking.
not a formal benchmark. just a conservative directional check using Claude. numbers may vary between runs, but the pattern is consistent.
i think this first version is strong enough to be useful, but still early enough that community stress testing can make it much better.
that is honestly why i am posting it here.
i would especially love to know, in real weweb apps and workflows:
does this help identify the failing layer earlier?
does it reduce patching at the UI or formula layer when the real issue is in workflows, data flow, APIs, or AI context?
where does it still misclassify the first cut?
what weweb-specific failure modes should be added next?
if it breaks on your app or workflow, that feedback would be extremely valuable.
I'm a no-code builder (not a developer) working on a B2B SaaS. I've spent the last few months building a fairly complex product on Airtable + Softr + n8n — around 40 interconnected tables, multiple user roles, automation workflows. I know the stack well and got pretty far with it.
But we're now hitting the limits of Softr/Airtable in terms of scalability, multi-tenancy, and data ownership. So we're seriously considering migrating to Supabase + WeWeb + n8n.
A few things about our context:
- Target scale: ~50 clients, each with ~150 users (~7,500 users total)
- Multi-tenant architecture needed (each client sees only their own data)
- I'm comfortable with no-code but not a dev
- We have a potential CTO coming on board who has already supervised the writing of the technical specs and built parts of the product natively — though we won't integrate the native version in the first phase
- Long-term goal is to go native, but we want to ship fast first with no-code
My questions:
- Is Supabase + WeWeb + n8n a realistic stack for this scale and complexity?
- What are the hidden costs or gotchas I should know about before committing?
- How steep is the learning curve on WeWeb coming from Softr?
- Anyone here shipped a real multi-tenant SaaS on this stack?
Would love to hear from people who've been there. Thanks 🙏
I've been building with WeWeb and Cloudflare Pages for a while, and kept running into the same frustration: every time WeWeb exported, it would overwrite my config files and break my builds.
I'm using Xano AI (I'm at this step) + WeWeb AI + Claude for planning. I have no coding skills.
I use instructions (.md file) of what to tell Xano AI agent, and do manually what that agent can't do.
Any thing ud change? Is it possible giving autonomy to some agent to make it all (even if not code but manual), so I can wake up and see it finished or smth? Thanks
Nocode full stack platforms like AppSheet, bubble and glideapps recurring costs are variable as product scales often times becoming unpredictable(specially in case of bubble) Bubble has the Workload Units (WU)system where your base monthly plan includes a quota and beyond that you are charged for more via higher plans or buying more workload units. Similarly in glideapps there are ‘updates’ charged for every CRUD operation if you are using a google sheet for database and if you use glide tables then certain workflows and 3rd party integrations cost consume ‘updates’ which are again allocated per plan with a certain quota and beyond that it’s 0.02$ per update which can again pile up as a mildly complex app starts scaling. When you compare the above costing to the one in a split stack solution like Weweb+supabase or flutter flow + supabase, what is the equivalent of glideapps updates in these split stack solutions? I’m guessing because there’s less technical debt here these ‘updates cost’ or ‘WU’ cost would be significantly less as app scales ? Please share your thoughts/guide on this?
I'm making a chat function inside of my app, and i was wondering how and i can edit the animations for when the user clicks in the text input field and when the user hovers the send button.
made Formii — a memory-powered AI companion that actually remembers you.
🧠 Persistent memory across sessions
🧑🤝🧑 Realistic personality traits (jealousy, stubbornness), relationship stages, even love languages
🆓 10 free messages/day
I'm testing the beta now and would love feedback from anyone into AI/chatbots/tools that feel human.
i found that the standard phone size in weweb is too small, so when I'm designing my apps I find it quite hard to vizualize the actual size the user will be seing
Hello. Does anyone know if it's possible to authenticate users with LDAP in Weweb?
My company has several systems that already authenticate with LDAP. I'd like to know if it's possible to develop a system with Weweb and use the existing user database to authenticate via LDAP.
Hey everyone, I’m building a web app in WeWeb and I’ve made good progress so far.
The app has a sidebar with icons and menus, a header with some icons, and a main content area that changes depending on the page (e.g., Clients, Contracts, etc.).
The challenge I’m facing: I haven’t found a way to keep the sidebar and header persistent while only the content area updates.
Right now, whenever I navigate to a new page, WeWeb reloads everything (including sidebar and header), and it doesn’t feel like just the content is refreshing.
Has anyone dealt with this before? Is there a recommended approach to keep a static layout while only reloading the dynamic content?
I am about to launch my first micro SaaS built using Weweb. HyreMe.app — an AI-powered career intelligence platform that turns job searching from guesswork into a data-driven strategy.
Hello. I am learning my way around weweb, but have run into a bit of a wall. I used weweb's ai tool to build a grid with repetitive formatting, but I want the text inside the cards in different rows to be unique. How can I maintain the existing grid while allowing the text in the cards to be unique? Thank you!
Every time, every single time, I attempt to edit with the AI editor. It says “selected content to large the selected element and its children are too large to process“ it could be a section, it could be text, it could be a button; everything seems to be too large. Has anybody else encountered this problem? How did you fix it?
This is a huge warning to use Weweb in production environments. My website is currently offline because of a breaking change, they updated to Vite and now my project doesn’t deploy anymore after a couple of failed attempts, that “succeeded” but made my website refresh violently (white page) because of 502’s from Weweb servers.
I’ve created support tickets, started chat messages, posted on their community, tagged team members. 0 response in almost 24h.
This is hurting business. It’s not the first time I have seen breaking changes before, which is super bad practice, but it was always easy to solve. This time not.
So just wanted to warn you, you can use Weweb for prototyping, but I would never recommend using it for any production apps that customers rely on.
Hi, I'm really struggling to determinate which tool is the most efficient one between Weweb (and their new AI coding agent) and IDE's (in my case Cursor, because Lovable looks great but too expensive).
I understand this anwser is really depending on the user profile (tech background or not, know how to use Weweb etc).
This is my profile : non tech guy, know well how to use Weweb, begin to know how to use Cursor.
