Hire a Certified WeWeb
Developer or Agency

Multi-tenant SaaS portal

Launched to 200+ users on day one. Row-level security, per-tenant branding, and Stripe billing — all without a single line of frontend code.

⏱ Delivered in 6 weeks

Client document portal

3 permission tiers (admin, manager, client), drag-and-drop document upload, automated email notifications via Make. Client onboarding dropped from 2 days to 20 minutes.

⏱ Delivered in 5 weeks

Internal ops dashboard

Real-time KPI dashboard with AI-generated weekly summaries. Team of 12 switched from 4 separate spreadsheets to one source of truth.

⏱ Delivered in 4 weeks

✓ Choose WeWeb when

✕ Consider alternatives when

What WeWeb Actually Is — And Why People Confuse It with Webflow

WeWeb and Webflow share the same drag-and-drop visual editor surface, which causes a lot of confusion for first-time buyers. The difference is fundamental: Webflow is a website and CMS builder designed for marketing pages and content sites, while WeWeb is an application builder designed for data-driven, authenticated web apps. If your project has user accounts, dynamic data, and complex workflows, WeWeb is the right tool — Webflow will fight you every step of the way. The confusion is compounded by the fact that both tools look similar in screenshots. Side-by-side, you see a canvas, a component panel, and a properties sidebar. But WeWeb's data binding layer, workflow engine, and plugin ecosystem are built specifically for connecting to backends — Supabase, Xano, REST APIs, GraphQL — and rendering that data conditionally based on user state. Webflow has no native concept of a logged-in user or row-level data access. The clearest way to decide: if your app requires a login screen, it almost certainly belongs in WeWeb. If your project is a public-facing website with mostly static content, Webflow or even plain HTML will serve you better and cost less. WeWeb is deliberately overbuilt for marketing sites — and that's the point. It is a serious application development environment that happens to look approachable.

WeWeb Architecture: Frontend-Only and Why That Matters

WeWeb is a pure frontend tool. It renders your UI, handles client-side state, manages routing, and makes API calls — but it does not store data, run server logic, or manage authentication on its own. This is a deliberate architectural choice, not a limitation. By staying frontend-only, WeWeb can connect to any backend you choose: Supabase, Xano, a custom Node.js API, or anything that speaks REST or GraphQL. This separation of concerns gives you flexibility and avoids vendor lock-in at the data layer. Your database is yours — hosted on Supabase, in your own cloud, or behind your own API. WeWeb just consumes it. If you ever want to rebuild the frontend in React, you can do that without touching your backend. If you want to migrate from Xano to Supabase, your WeWeb frontend barely changes. Each layer evolves independently. The practical implication is that you need to think about your stack before opening WeWeb. A WeWeb project without a backend plan is a car without an engine. Most teams pair WeWeb with Supabase for the database and auth layer, and optionally add Xano if they need complex business logic that belongs server-side. Once you have that mental model, WeWeb's architecture feels natural — and the speed advantages of building visually without sacrificing separation of concerns become obvious.

Connecting WeWeb to Supabase Step-by-Step

Connecting WeWeb to Supabase is one of the most common setups in the no-code ecosystem, and WeWeb has a native Supabase plugin that handles both the data connection and the authentication layer. Start in WeWeb's plugin panel, install the Supabase plugin, and paste your Supabase project URL and anon key. WeWeb will immediately fetch your database schema and make all your tables available as data sources. From there, you create collections in WeWeb that map to Supabase tables. A collection is a named data fetch — you define which table, which columns, any filters, and the sort order. WeWeb will call Supabase's auto-generated REST API to populate that collection, and you can bind any element on your canvas to any field in any collection. Updates to the Supabase table are reflected in the WeWeb UI on the next fetch or in real time if you enable Supabase Realtime. For authentication, the Supabase plugin handles login, logout, and session management automatically. You configure your auth provider in Supabase (email/password, Google OAuth, magic link, etc.), then tell the WeWeb plugin which page is the login screen and which pages require authentication. WeWeb will redirect unauthenticated users and pass the user's JWT to every subsequent Supabase request, which means your Row-Level Security policies fire automatically without any extra configuration in WeWeb. The result is a fully secured, data-driven web app with almost no manual plumbing.

Building Your First SaaS Dashboard in WeWeb

A SaaS dashboard in WeWeb typically involves a sidebar navigation, a header with user info, and a main content area that displays dynamic data from your backend. Start by laying out the page structure with WeWeb's section and container components — these are standard CSS flexbox containers that give you full control over layout without writing CSS. Once the skeleton is in place, connect your data collections and start binding fields to text, table, and chart components. WeWeb's table component is particularly powerful for SaaS use cases. It supports sorting, filtering, pagination, and inline editing out of the box. You can bind each column to a database field, add action buttons that trigger workflows, and conditionally show or hide columns based on user role. For charts, WeWeb integrates with Chart.js natively — bind a collection to a bar chart or line chart and you have a live data visualization in minutes. The workflow layer is where WeWeb really shines for SaaS. A workflow is a sequence of actions triggered by a user event: a button click, a form submission, a page load. You can call an API, update a Supabase record, navigate to a route, show a modal, or fire a custom JavaScript function — all chained together with conditional logic. This replaces a significant amount of frontend JavaScript code that you would otherwise need to write and maintain. For most SaaS dashboards, 90% of the interactivity lives in WeWeb workflows with no custom code at all.

Authentication and Roles in WeWeb

Authentication in WeWeb is handled through the auth plugin for your chosen backend — Supabase, Xano, or a custom OAuth provider. Once configured, WeWeb manages the session lifecycle: storing the token, refreshing it before expiry, and attaching it to every API call. You define authenticated routes in WeWeb's page settings, and the platform enforces redirects automatically without you writing a single auth guard. Role-based access control in WeWeb is implemented at two levels. At the page level, you restrict access to specific user groups — only users with the role 'admin' can visit the admin dashboard. At the component level, you use WeWeb's conditional visibility bindings to show or hide elements based on the current user's role or any other property on the user object. A manager sees the delete button; a viewer does not. This is pure frontend enforcement and should always be paired with backend Row-Level Security policies in Supabase. Multi-tenancy — where each company's users only see their own data — is handled through the combination of WeWeb's user object and Supabase's Row-Level Security. When a user logs in, their organisation ID is stored on the Supabase user record. Every RLS policy checks that the requesting user's organisation ID matches the row's organisation ID. WeWeb passes the authenticated JWT with every request, which activates these policies automatically. The result is a multi-tenant SaaS where data isolation is enforced at the database level, not by filtering in the frontend UI.

WeWeb Pricing and When to Upgrade

WeWeb's pricing is workspace-based and scales with the number of editors and the tier of features you need. The free plan is useful for exploration and prototyping but lacks custom domain publishing, which makes it unsuitable for production apps. The Starter plan covers a single published app with a custom domain and is appropriate for solo founders and small projects. The Growth and Scale plans add multiple apps, collaborators, white-label options, and advanced support. The most important trigger for upgrading is going live with a paying customer. At that point, the cost of WeWeb's plan is negligible compared to the value it delivers. Where costs accumulate in larger organisations is the per-editor seat model — every person who needs to edit the WeWeb project counts as a seat. Plan accordingly: keep the number of WeWeb editors small and use Supabase's admin UI or a separate internal tool for non-technical team members who need to manage data. One common gotcha is building on the free plan for months and then discovering that migration to a paid plan requires reconfiguring the custom domain and republishing. Do that migration early, before you have users. Also budget for Supabase costs separately — WeWeb's hosting bill and your Supabase bill are independent. For most early-stage SaaS products, the combined monthly cost of WeWeb plus Supabase is under $150, which is a rounding error compared to the engineering hours saved by building visually.

Hire

Need a dedicated WeWeb specialist for your project? Fixed price, fixed timeline.

Migrate

Already on another platform and want to move to WeWeb? We handle the full migration.