Webflow + Xano

Bubble builds UI, logic, and database inside one editor, which is the fastest way to a functional app and the cheapest way to start. This stack splits the jobs the way coded stacks do: Webflow produces the best visual output in the no-code world, and Xano is a real relational database generating real REST APIs, independent of any frontend. The split buys things Bubble cannot: design quality that holds up for client-facing products, a backend a second frontend can point at later (a mobile app, a partner portal), and a clean boundary between content and logic. It costs two subscriptions and two tools to learn. Choose Bubble for internal tools and speed; choose this stack when the product is client-facing or the API matters.

Two subscriptions, both with real free tiers for building. Webflow's Starter plan stages the site free on a webflow.io domain; publishing to a custom domain starts at Basic, $15 a month billed yearly, and the Premium plan at $25 a month billed yearly adds the CMS that this stack's marketing pages lean on. Xano's free plan carries 100,000 database records with rate-limited APIs (10 requests per 20 seconds); production realistically moves to Essential at $85 a month billed yearly once the app needs unrestricted APIs. A working small production deploy lands around $110 a month, with the Xano bill the larger share; see the Pricing section below for the full breakdown.

Half of it, cleanly. Xano is already a REST API over PostgreSQL: a hand-coded frontend (React, Vue, Flutter, anything) can call the same endpoints, so the backend and its data survive a frontend rewrite untouched. The Webflow side is the part that needs rebuilding: sites export clean static HTML and CSS, but the visual interactions, Logic flows, and CMS bindings have no equivalent in a coded framework. A fully coded stack eventually replaces Xano too, but that is its own later migration, done on its own schedule; the frontend rewrite never blocks on it. The practical rule for planning ahead: keep business logic in Xano endpoints rather than Webflow Logic, because that is the part that ports.

Webflow publishes static pages, so data that varies per logged-in user is fetched from the browser: custom code or a Logic flow calls the Xano endpoint, sends the auth token Xano issued at login, and renders the JSON into the page. That has one architectural consequence worth knowing upfront: client-side content is invisible to crawlers, so pages that must rank (listings, public profiles) should stay on Webflow's CMS or get a prerendered public view, with Xano supplying only the private, behind-login data. Auth tokens live in the browser (typically localStorage), which is standard for this shape of app but worth handling deliberately. Sites that mix public marketing pages with an app area behind a login get the best of both worlds: SEO where it matters, dynamic Xano data where it is needed.

There are two legitimate places for money, and the mistake to avoid is splitting one product across both. Webflow Ecommerce handles site-level checkout (physical goods, event tickets) natively, with Stripe underneath. Subscriptions and entitlements that live in Xano (gated memberships, SaaS plans) are implemented on the Xano side: Xano endpoints pair with Stripe's subscription APIs, the Webflow frontend calls those endpoints, and Xano records who is entitled to what. The rule: never bill a Xano-gated feature through Webflow Ecommerce, because Webflow cannot update the Xano database and the two ledgers drift within days. One Stripe account serves both sides, so the money reconciles in a single dashboard even though the implementations differ.