8 No-Code and Low-Code Builders: Where Each One Stops Being No-Code

Every one of these eight tools is sold as "no-code," and every one of them eventually makes you write something: an expression, a workflow rule, a custom action, or actual Dart. The useful question is not whether you need code but at what point you hit it, because that is the point where your project's cost curve bends. The order below runs from least technical to most, and the boundary in each case is stated plainly.

1. Bubble: The Most Freedom, and the Deepest Lock-In

Bubble is the reference no-code builder: a visual canvas, a database with relations, and a workflow editor that can express real logic. Teams have shipped funded startups on it without a developer.

Pricing: A free plan for building and testing, then paid tiers that scale mainly by workload units and collaborator seats.

Where it stops being no-code: Performance optimisation. Bubble bills and throttles by workload units, so an inefficient workflow that "just works" in testing becomes an expensive one in production. Getting under the limit requires understanding how the platform executes your logic - which is engineering, whether or not it looks like code.

2. Glide: A Spreadsheet That Becomes an App

Glide takes a table - Google Sheets, Excel, or its own data source - and renders it as a mobile and web app with forms, lists and role-based access. The mental model is rows, not screens.

Pricing: A free tier for personal use, with paid plans charged per user or per app depending on tier.

Where it stops being no-code: The moment your data model needs joins. Glide's computed columns can derive values, but complex relational logic across several tables quickly exceeds what column formulas express, and you end up reshaping the spreadsheet to fit the tool rather than the other way round.

3. Adalo: Mobile-First, With Native Constraints

Adalo targets phone-shaped apps: drag components onto a mobile canvas, define collections, publish to the App Store or Play Store through its build service.

Pricing: A free plan for building, then paid tiers; publishing to the stores requires a paid plan.

Where it stops being no-code: Anything beyond CRUD. Push notifications, offline behaviour and third-party SDKs are the usual breaking points, and each one either has a workaround inside Adalo or forces a custom component build.

4. FlutterFlow: Low-Code With Real Dart Underneath

FlutterFlow is honest about being low-code: it generates a Flutter project you can export and keep. That export is the reason teams pick it over pure no-code tools.

Pricing: A free tier for building and testing, then paid plans; code export and some integrations sit on higher tiers.

Where it stops being no-code: Custom widgets. The visual editor covers layout and standard flows, but anything requiring precise animation, platform channels or performance tuning means writing Dart in a custom widget - at which point you are a Flutter developer using a generator.

5. OutSystems: Enterprise Process, Enforced

OutSystems is built for organisations that need governance more than speed: role-based deployment pipelines, architecture validation, and an AI assistant that scaffolds modules within those rules.

Pricing: Quote-based enterprise licensing; no self-serve price list.

Where it stops being no-code: Immediately, in the sense that matters - you cannot adopt it without a platform team. Its value comes from enforcing standards across many apps, and that enforcement is exactly what a solo builder experiences as overhead.

6. Mendix: Model-Driven, With a Real IDE

Mendix is model-driven rather than form-driven: you edit domain models, microflows and pages in a desktop IDE, and the platform compiles them into a running app.

Pricing: A free tier for learning and small apps, then per-user enterprise licensing quoted by sales.

Where it stops being no-code: The IDE itself. Modelling microflows is a skill with its own vocabulary and its own failure modes, and the free tier's limits appear precisely when an app starts carrying real users.

7. Power Apps: Cheap If You Already Pay for Microsoft 365

Power Apps is the pragmatic choice inside a Microsoft estate: it reads SharePoint lists, Dataverse tables and Teams, and Copilot can draft a working app from a description.

Pricing: Included with some Microsoft 365 plans for basic use; premium connectors and larger usage need per-user or per-app licensing.

Where it stops being no-code: Connectors. Every data source beyond the built-in set is a premium connector, and that licensing boundary usually decides the project before any technical question does.

8. AppSheet: Google Sheets, Turned Into an App

AppSheet is the closest thing to zero setup here: point it at a sheet, and it infers a form, a list view and a detail page from your columns. It now sits inside Google's Workspace ecosystem.

Pricing: Per-user plans billed through Google Workspace, with a limited free tier for prototyping.

Where it stops being no-code: Expressions. AppSheet's behaviour rules, security filters and computed columns are written in an expression language that is code in all but name - and getting a security filter wrong exposes data rather than breaking a page.

How to Choose

Pick by the boundary you can tolerate, not by the feature list. If you will never need joins or performance tuning: Glide or AppSheet. If you need a mobile app with a real store presence and can accept component limits: Adalo. If you might outgrow the platform: FlutterFlow, because you can take the code with you.

If you are inside a Microsoft or Google estate and the app is internal: Power Apps or AppSheet, where the licence is often already paid. If the app must pass an architecture review: OutSystems or Mendix, and budget for the platform team that makes them worth their price.

Bubble remains the strongest general-purpose choice, provided you plan for workload-unit costs from the first workflow rather than discovering them at scale.