The essentials · 30-second read
Wized adds login, data and API logic on top of a Webflow site. Free on a webflow.io domain; paid plans per domain from $12 a month, or $9 a month billed yearly.
- Wized keeps your Webflow design and adds requests, user sessions and logic configured in a visual editor.
- Free for projects on a webflow.io staging domain. Paid plans are priced per domain, from $12 a month ($9 billed yearly) to $169 ($149 yearly).
- Plans are limited by page views and by the number of elements Wized controls, not by the number of users.
- Our verdict: a good fit when a Webflow site must become a small app. Plan the backend (Xano, Supabase) and the maintenance from day one.
Summarize this page with AI
Wized is the tool we look at when a Webflow site has to become an application: a client portal, a member area, a dashboard or an MVP. Instead of rebuilding the design in another platform, Wized adds the missing app layer on top of Webflow. This page explains what Wized is, what it costs in 2026, when we recommend it to clients, when we advise against it, and what a Wized development project really involves.
01What is Wized?
Wized is a low-code JavaScript framework for building web applications on Webflow. Its own website describes it as the application layer on top of your Webflow project. You keep designing pages, components and styles in Webflow; Wized then reads and changes those elements in the browser, based on requests to a backend and on rules you configure in a visual editor.

A Wized app has three layers. The interface is your Webflow site. The logic (events, requests, conditions, variables) lives in Wized. The data lives in a backend such as Xano, Supabase or any REST API. Wized is operated by Finsweet, the company behind the Client-First convention used on many Webflow sites, and the Finsweet ecosystem (forum, agency) supports it.
What Wized is not: it is not a database, not an authentication service and not a hosting platform. It connects your Webflow front end to the services that do those jobs.
02How we use Wized at BeBranded
BeBranded is a Webflow Certified Partner since 2023 and builds sites, web apps and automations for clients. Wized is not part of our daily stack: our own site moved from Webflow to Next.js and Payload CMS in November 2026. We use it as an option in our web app work, and here is how we decide.
We recommend Wized when three conditions are met:
- The site is already in Webflow and the marketing team keeps editing it there.
- The app part is limited: a login, a few private pages, lists filtered from a database, forms that write data.
- A backend is chosen and owned: usually Xano or Supabase, with its own access rules.
We advise against it when the "app" is the product itself, with dozens of screens, complex state and a team of developers. There, a dedicated framework such as Next.js is easier to test, version and maintain. We also warn clients that a Wized project is code in disguise: requests, error handling and security still need someone who thinks like a developer. That is why searches for a "Wized agency" or "Wized development" make sense: the tool is visual, the work behind it is not.
03Key features
- Requests: call any REST API (GET, POST, PATCH, DELETE) with parameters, headers and authentication tokens.
- Events and actions: react to page load, clicks, form submits or input changes, and chain actions.
- Data binding: fill Webflow texts, images, links and lists with data returned by the backend.
- Conditional display: show or hide elements depending on the user, a status or a value.
- User sessions: store a token after login and protect pages for logged-in users.
- Visual editor: configure all of this without writing raw JavaScript in most cases, with JavaScript available when needed.
- Environments: build on a webflow.io staging domain, then publish to production domains on paid plans.
04Use cases
Client portal on top of a Webflow site
A service company has a Webflow site and wants clients to log in and see their projects, invoices or documents. Wized handles login and loads each client's records from Xano or Supabase into Webflow templates. What to know: access rules must be enforced in the backend, so a client can never request another client's data by changing an ID.
Member area or paid content
A media or training business wants to reserve content for members. Wized can show or hide sections based on the user's status returned by the backend or by a membership tool. For simple gating, a dedicated tool like Memberstack is often faster; Wized makes sense when member pages also show personalised data.
Directory or marketplace MVP
A founder wants to test a directory with search, filters and listing pages, without a full development budget. Wized calls the backend with the user's filters and renders results in Webflow collection-like layouts. It lets the founder validate demand with a real design, then rebuild later if the product grows.
Internal dashboard
An operations team needs a simple dashboard showing records from an API with a few actions (approve, update a status). Wized works, but compare it with internal tool builders: if nobody outside the team sees the screens, design matters less than speed of change.
Multi-step forms and calculators
Quotes, onboarding flows or booking forms with steps, conditions and a final write to a database. Wized handles steps and logic in the page and sends the result to the backend in one request.
05Integrations
Wized talks to services through their APIs. Its website lists, among others, Xano, Supabase, Firebase, Airtable, Memberstack, Stripe, Shopify, HubSpot, Salesforce, Notion, Make, Zapier, Twilio and SendGrid, plus any REST API. In practice:
06Wized pricing in 2026
Prices checked on wized.com/pricing on 14 November 2026, in US dollars, per domain. The page has a Monthly / Yearly switch: the first figure is the monthly price, the second the monthly equivalent billed yearly.

| Plan | |||||
|---|---|---|---|---|---|
| Free | Billed monthly $0 | Billed yearly $0 | Page views Unlimited | Wized elements Unlimited | Publishing Staging only (webflow.io) |
| Lite | Billed monthly $12/month | Billed yearly $9/month | Page views 100,000 | Wized elements 20 | Publishing One production domain |
| Small | Billed monthly $39/month | Billed yearly $29/month | Page views 100,000 | Wized elements 100 | Publishing One production domain |
| Medium | Billed monthly $69/month | Billed yearly $59/month | Page views 200,000 | Wized elements 400 | Publishing Multiple and wildcard domains |
| Large | Billed monthly $169/month | Billed yearly $149/month | Page views 300,000 | Wized elements Unlimited | Publishing Multiple and wildcard domains |
| Enterprise | Billed monthly On quote | Billed yearly On quote | Page views Unlimited | Wized elements Unlimited | Publishing SLA, SSO add-on, dedicated infrastructure |
All plans include 90 days of backup. Big projects can add 1,000,000 page views for $199 through Wized support. If you go over your quota, Wized emails you to upgrade and the site stays online.
Is Wized free? Yes, for building. The Free plan has no time limit and no cap on page views or elements, but it only publishes to a webflow.io staging domain. A real app on your own domain starts at Lite, and most apps with several screens need Small or Medium because of the element limit. Remember to add the cost of Webflow hosting and of your backend.
07Pros and cons
Advantages
- Keeps the Webflow design and the Webflow editor for marketing pages.
- Works with any REST backend, so the data is not locked inside Wized.
- Visual configuration that a Webflow developer can learn without a JavaScript framework.
- A free plan with no time limit for prototyping.
- Pricing per domain, not per end user.
Drawbacks
- The total stack has three bills: Webflow, Wized and the backend.
- Logic runs in the browser: security depends entirely on the backend rules.
- Complex apps become hard to debug and to hand over to another team.
- The element limit pushes medium-sized apps to the higher plans.
- Tied to Webflow: if the site leaves Webflow, the Wized layer must be rebuilt.
08Our verdict
Who it's for
- Teams with a Webflow site that need login, private pages or live data.
- Founders testing an MVP with a strong design before investing in custom development.
- Webflow agencies and freelancers who want to deliver small apps on a stack they master.
- Projects with an existing API or backend that needs a designed front end.
Who it's not for
- Products where the app is the core business, with many screens and developers: a code framework is safer.
- Teams with no one able to design a backend and its security rules.
- Sites that only need gated content: a membership tool is simpler.
- Projects planning to leave Webflow soon.
09Wized alternatives
| Tool | |||
|---|---|---|---|
| Wized | Best for App layer on an existing Webflow site | Free plan Staging only | Paid from $9/month per domain (yearly) |
| WeWeb | Best for New front ends built in a dedicated app builder | Free plan Yes | Paid from Paid plans |
| Memberstack | Best for Logins, gated content and memberships on Webflow | Free plan Test mode | Paid from Paid plans |
| Bubble | Best for All-in-one app with built-in database | Free plan Yes | Paid from Paid plans |
| Softr | Best for Portals on Airtable or other data sources | Free plan Yes | Paid from Paid plans |
| Next.js | Best for Custom apps written in code | Free plan Open source | Paid from Hosting costs |
Our rule: use Memberstack for simple gating, Wized when a Webflow site needs real app logic, and WeWeb or Bubble when you start a new app from zero. When the app is your product, we build it in code as a custom web app or an MVP. Our comparison of Bubble and WeWeb goes deeper on that choice.
10Wized vs WeWeb
Both tools build front ends on top of a backend you choose, and both call REST APIs. The difference is where the interface lives. With Wized, the interface is a Webflow site: designers keep Webflow's visual tools, CMS and hosting, and Wized adds behaviour. With WeWeb, the interface is built inside WeWeb, which is designed for apps from the start (pages, components, state, authentication plugins). If your marketing site and your app are the same Webflow project, Wized avoids a rebuild. If the app is a separate product, WeWeb gives a cleaner structure.
11Getting started with Wized
- Design the backend first. Define the tables, the authentication and the access rules in Xano or Supabase before touching Wized.
- Prepare Webflow. Build the screens with clean classes, then add Wized attributes to the elements that will change.
- Add the Wized script to the Webflow project and connect it in the Wized editor.
- Start with login and one list. Test the session, error states and the empty state before adding more screens.
- Document the logic. Name requests and variables clearly, and write down which page calls which endpoint, so another developer can take over.
If you are unsure whether your project needs Wized, Memberstack or custom code, we can scope it with you in a project scoping session, or build a client portal directly.



