WeWeb

WeWeb occupies an unusual spot in the no-code market: it is a visual builder that treats the generated code as a first-class output rather than a platform secret. Built by a Paris team and backed through Y Combinator's W21 batch, it produces a Vue.js single-page application that you can inspect, export, commit to git, and host anywhere. In a category where most tools rent you their runtime forever, that architectural choice shapes everything else about the product — who it is for, what it costs, where it wins, and where it falls short. I have watched this platform mature from a promising frontend experiment into something agencies genuinely ship client work on, and the trajectory shows in the details.

Where it sits

WeWeb is frontend-only by design. Layout, state, routing, interaction logic, and client-side data handling live in WeWeb; the database, authentication, and server-side business logic live wherever you put them. That separation is the pitch. If you already run Supabase, Xano, Airtable, or any REST or GraphQL API, WeWeb becomes the interface layer on top of infrastructure you control. If you want an all-in-one product that owns your data model and hides the plumbing, this is not that. Competitors like Bubble bundle everything and lock you in; WeWeb hands you an escape hatch and asks you to assemble the rest of the stack yourself. The pricing reflects the same split: per-developer seats for the editor, token allotments for AI features, and a separate cloud hosting ladder if you want WeWeb to deploy the app rather than exporting it.

The buyer profile is specific. Developer-adjacent teams, agencies delivering client portals and internal tools, and SaaS founders who want front-end velocity without surrendering the codebase. The community skews technical — the praise in user forums clusters around architecture control and clean export, while the complaints cluster around pricing predictability and the learning curve. That tells you who thrives here: people who understand what an API is and simply don't want to hand-write component trees.

What it actually does

The editor is a drag-and-drop canvas over real components with a workflow engine, formulas, and reactive data binding underneath. Data sources are defined once and reused across the app: native connectors for Supabase, Xano, Airtable, Google Sheets, Notion, PostgreSQL, MySQL and others, plus generic REST and GraphQL with configurable auth and headers. You can drop in custom JavaScript, custom CSS, and your own Vue components when the visual layer runs out — a hybrid model that keeps the visual speed of no-code while admitting that real projects eventually need code. On the AI side, WeWeb now generates pages and scaffolding from plain-language prompts, and ships an MCP server so coding agents like Claude Code or Cursor can drive the editor directly — a 14-day trial on the Free plan, unlimited on Pro, with Pro also adding protection for resources you don't want AI edits touching.

In April 2026 the company shipped WeWeb Tables, a native Postgres backend with a spreadsheet-style UI, auto-generated CRUD APIs, auth, storage, and trigger-based workflows. That single feature removes the "you must bring Supabase" tax for simpler data models and changes the total-cost arithmetic considerably. For complex relational schemas with strict row-level-security requirements, a dedicated Supabase setup is still the more controllable option, but for a client portal with a handful of tables, WeWeb Tables is now enough on its own.

Code export is available from the Essential plan up. The output is a standard Vue.js SPA — deployable on Vercel, Cloudflare Pages, Netlify, AWS, or your own infrastructure. GitHub sync keeps the exported project in a repository, and daily (Essential) or hourly (Pro) editor auto-backups cover the build phase. Publishing to WeWeb's own cloud is a separate product line with its own tiers: a free tier capped at 1,000 sessions and 1 GB bandwidth, then paid hosting tiers with custom domains, more bandwidth, and a bundled database on the higher rungs. Figma import rounds out the design pipeline — teams import frames and bind data in the editor rather than redrawing from scratch.

My testing notes

Two observations define my experience. First, connecting a real backend is fast if you know what a service-role key is: I pasted a Supabase connection string into the data source panel and had authenticated queries rendering in the editor in under ten minutes, including row-level-security-aware reads. The deep Supabase connector handles auth and real-time subscriptions natively, and direct SQL queries mean multi-table joins don't degenerate into chains of API calls the way they do in Bubble. For a client project I reused the same data source across eleven screens without redefining a single request — the collections model is the part of WeWeb that most rewards investment.

Second, the export is genuine. I exported a client-style project, deployed it to Vercel, and read the output: commented Vue components, sensible structure, maintainable rather than minified sludge. That matters for handoff and due diligence — there is a real codebase to inspect, and the "what happens if the vendor disappears" objection dies on the spot. The caveat I hit: plugins that lean on WeWeb's own microservices stop working after export, so the exit is clean only if your connector diet is standard. Before treating export as a complete parachute, audit which connectors you depend on.

The workflow editor is powerful but assumes you understand arrays and reactive state. Building a filtered list with pagination took me a couple of attempts to get the reactivity right — not a bug, but a clear signal that this is a low-code tool wearing no-code clothes. Performance was fine for data-dense dashboards in my use, though I saw other users report sluggishness on heavy mobile pages when collections and components multiply. I also watched the pricing page closely. It is JavaScript-gated, prices moved on 12 February 2026, and third-party trackers still disagree on the annual-discount figures — a commercial presentation that could be considerably clearer.

What it does not do

No server-side rendering, and the company has taken SSR off its 2026 roadmap — the CEO said so in the roadmap post. WeWeb apps are client-rendered SPAs, which makes them a poor fit for anything where Google organic traffic is the business model. There is no native mobile output either; you build responsive web apps and PWAs, not iOS or Android binaries. WeWeb also does not host your data or manage access rules — if your backend's API security is sloppy, your app is sloppy with it. The AI generation is strongest on standard patterns; highly custom UX still needs manual editor work, and users report roughly a fifth of complex scenarios requiring real correction. And while the project lives in the cloud during builds, there is no self-hosted editor — the tool itself is a SaaS you subscribe to, even though its output is not.

Verdict

WeWeb is the builder I reach for when a team wants visual speed without painting itself into a corner. The code export is real, the backend freedom is real, and the WeWeb plus Supabase pairing is one of the most documented patterns in the ecosystem. Against that: no SSR, a steeper learning curve than pure drag-and-drop tools, layered pricing that is hard to quote to a client, and AI generation that still needs human correction on complex builds. I rate it 4.0 on the ToolSpotter rubric — core functionality depth is high for its niche given the code export, connector breadth, and workflow engine (the biggest slice of the score), value is good for solo builders on the $20 Essential plan, usability is the drag given the API literacy it demands, the community and 400-strong certified agency ecosystem are healthy, and reliability signals from YC backing through enterprise logos like L'Oréal and Decathlon are solid. If you need SEO-driven marketing pages, look elsewhere. If you need a production web app front end you could one day walk away with, this is one of the very few tools that lets you.

Sources

• https://pricing.weweb.io
• https://weweb.io/pricing
• https://weweb.io/changelog
• https://weweb.io/blog/our-2026-roadmap
• https://checkthat.ai/brands/weweb/pricing
• https://conversiongems.com/tools/weweb
• https://outmano.com/tools/weweb/pricing
• https://toolradar.com/tools/weweb-builder/pricing
• https://hokai.io/hub/tools/weweb
• https://rapidevelopers.com/review/weweb
• https://servdigest.com/en/reviews/weweb
• https://hackceleration.com/labs/review/weweb
• https://aitoolsatlas.ai/tools/weweb/review
• https://goainav.com/en/tools/weweb-no-code-web-app-builder