Skip to content

Best internal tool builders for customer-facing apps (2026)

Retool, Appsmith, Superblocks and Budibase for customer-facing apps: external-user pricing, embed gates, permissions, self-hosting, AI and MCP. September 2026.

Namanyay Goel · Updated · 10 min read

A founder at FazeShift described the loop to me: "eventually you just lose your mind on like okay I'll add one more toggle one more drop down." A product leader at Vividly said it in fewer words: "it's never enough. It feels like." The customer wants a portal or a configured view, engineering has a roadmap, so somebody opens Retool.

This is my list of the best internal tool builders for customer-facing apps in 2026, with one entry that is not really an internal tool builder (mine) and one that is not a tool at all (writing it yourself with Cursor or Lovable). I run Gigacatalyst, so read the last two entries with that in mind.

What an internal tool builder is

An internal tool builder is a drag-and-drop app editor that connects to your databases and APIs so an engineer can ship an admin panel in a day instead of a sprint. The word "internal" is the point. These products were priced and permissioned for staff, and pointing one at customers shows the seams in six places.

How to judge them for customer-facing use

  1. External-user pricing. Is there a published price per customer who logs in, and what is it at 500 or 5,000?
  2. Authenticated embedding gates. Which plan lets a logged-in customer see a private app inside your product?
  3. Permissions that follow the product. Does the tool enforce which rows a customer can see, or do you rewrite that logic in every query?
  4. Self-hosting. Can it run in your VPC, and does that change the price?
  5. AI generation. Can it build an app from a prompt, and how far does that go?
  6. MCP. Can your team drive it from Claude, Cursor or Codex? The separate list of app builders with an MCP server goes deeper.

Side by side

ToolExternal user price (as of September 2026)Authenticated embedRow-level permissionsSelf-hostingAI generationMCP server
RetoolFirst 50 free, then $8 per user per month annual, sliding to $4 at 500+Business and EnterpriseNo, scope in queriesYes, Docker or KubernetesAssist, classic apps onlyYes, public beta
AppsmithNot published; every logged-in member billed at $15 per user per month on BusinessEnterprise only, $2,500 per monthNoYes, all plansAI datasource; prompt-to-app not publishedNo official
SuperblocksEnd users free; embedded apps Enterprise only, custom priceEnterprise onlyNo, groups and JWT claimsHybrid data plane only, EnterpriseClark AI, Plan and BuildYes, Admin MCP is Enterprise
Budibase$5 per end user per month add-on on cloud; free self-hostedEnterprise only via signed JWTNo, filter by current userYes, open sourceAI columns and JS; whole app not publishedNo
GigacatalystQuoted per deploymentRuns on your product's authYour product's permissionsNo, hostedYes, from a request or transcriptNot for this product today
Cursor or LovableYour engineers' timeYour codeYour codeYour infraYesDepends on your stack

The tools

Retool

Retool is the default. It reads 40+ resources including REST and GraphQL, and since 2023 it sells Portals (hosted, custom domain, themed login) and React and JavaScript embed SDKs. External users are a third seat type on Business and Enterprise: the first 50 are free, then $8 per user per month annual from 51 to 250, $6 from 251 to 500, and $4 above that, as of September 2026 (https://retool.com/pricing). Builders on Business are $50 a month annual.

The gaps for customer-facing use are governance and math. Permissions are group based (Use, Edit, Own) with no row-level data policies, so tenant scoping lives in each query. Git source control and SSO for unlimited users are Enterprise only. On the Portals launch thread on Hacker News, one comment was "I can't pay that much per user" and another warned "your data gets locked and you have got to pay per user as you scale." Still, if you have JavaScript in house and a few hundred customers, Retool works. My longer take is on the Retool alternatives page.

Appsmith

Appsmith is the open-source option (Apache 2.0, 40.9k GitHub stars) with REST, GraphQL, 14 databases and 26 SaaS integrations. Free is up to 5 users on cloud, Business is $15 per user per month up to 99 users, and Enterprise is $2,500 a month for 100 users, as of September 2026 (https://www.appsmith.com/pricing).

The catch for customer-facing apps: public embeds work on every plan, but a private, authenticated embed is Enterprise only and needs SSO on a self-hosted instance. A user is anyone added to a workspace, billed for the full month even if they log in once. There is no published external-user price and no row-level permission model. See Retool vs Appsmith for the head to head.

Superblocks

Superblocks is the enterprise AI-first builder. Clark generates apps from natural language with Plan and Build modes, and it can import a Lovable, v0, Replit or Claude project as a zip and rewrite the auth and secrets into platform features. Teams is $125 a month billed monthly or $100 annual, with up to 15 builders, unlimited end users and one hosted app ($10 per additional app), as of September 2026 (https://www.superblocks.com/pricing).

Unlimited end users sounds like the answer for customer-facing apps until you read the next line: embedded apps, SSO via JWT, audit logs, Git sync and the Admin MCP are all Enterprise, custom priced. There is no full self-hosting; Hybrid keeps the control plane in Superblocks cloud and runs a data plane in your VPC. G2 reviewers (about 4.7 of 5, 190+ reviews) rate ease of use highly and list "missing features" as the top dislike. Compared in Retool vs Superblocks.

Budibase

Budibase is open source (GPLv3 with BSL for paid features, 28.3k stars) and free to self-host with unlimited users. Cloud runs $19, $49 and $299 a month annual for Pro, Premium and Business, with end users at $5 per user per month as an add-on, as of September 2026 (https://budibase.com/pricing/).

For customers, the embed model is the constraint. Published apps embed by iframe, and "only application screens with Public Access level can be viewed within an embedded Budibase app" unless you are on Enterprise, which adds signed-JWT authenticated embeds. Row-level security is not native; maintainers point to filtering by the current user's relationship. There is no Git integration and no MCP. Budibase itself says it is built for internal apps, "not intended for consumer-facing apps." Pick it for a free, self-hosted internal builder, not for a customer portal.

Gigacatalyst

Gigacatalyst is a different shape, so I will explain the shape rather than rank it. It turns a customer request (a spreadsheet report, a dashboard ask, a demo requirement, a call transcript) into a working dashboard, report or configured app that runs on your SaaS product's own APIs and permissions. It does not sit next to your product with its own user table. It calls your approved APIs as the customer, so tenant isolation is whatever your product already enforces, and it cannot show a field your API does not return.

That is why the customer keeps it at go-live. A former solutions leader at Enable told me "it wouldn't do me much good to be able to show a customer this dashboard, but then they don't have it when they go live." With an internal tool builder, the portal is a second app you now maintain. With Gigacatalyst, it is the product. A product leader at Jarmin put it as "a new take on Retool, but with the Lovable approach."

Limits, plainly: it is not a general internal-tool builder for your ops team (Retool is better there), it is hosted rather than self-hosted, and we are a young Y Combinator company that will need to pass your security review. Pricing is quoted per deployment with a pilot; start at /contact. The build vs extend calculator helps you compare against the DIY path below. More for product teams at /for-product-teams.

Code it with Cursor or Lovable

The honest sixth option. A product leader at Chargebee told me, "right now I use Lovable, I use Claude Code because that's what I know my team can understand." For one portal with one customer, this is often right. You own the code, the auth, the permissions and the bill.

The cost shows up on the second and tenth request. An engineering leader at Agilis pushed back on us with exactly this: "my engineering time is a one time spend, right?" It is, per app. Generated code still needs someone to review the tenant filter, deploy it, and patch it when your API changes. Superblocks now imports Lovable and Claude projects for that reason. Generating the UI is no longer the hard part; keeping it inside your permissions is.

The objection you already have

A sales engineering lead at Wrike asked, "Can I force the platform to not build new stuff, but only replicate what is already there?" For Gigacatalyst, yes, by construction: it only calls the APIs you approve. For Retool, Appsmith, Superblocks and Budibase, the app can do anything the connected credential can do, and it is on your builder to scope every query. A product leader at Klue wanted "a permission system where the capabilities would be predefined and then the app builder can only operate within those bounds." That is the question to put to every vendor on this list.

Next step

If your ops team needs an admin panel, pick Retool or Appsmith and stop reading. If a customer is waiting on a portal, report or configured view, send us the request and your API docs and we build it on your APIs. See it on your own APIs.

Questions people ask

Can Retool be used for customer-facing apps? Yes, through Portals and embed SDKs on Business and Enterprise. As of September 2026, external users are free up to 50, then $8 per user per month annual, and there are no row-level data policies, so you scope tenants inside each query.

Which internal tool builder has the cheapest external users? Budibase self-hosted is free with unlimited users but only allows public screens in embeds unless you are on Enterprise. Superblocks does not charge end users, but embedded apps are Enterprise only. Retool has the only published sliding scale.

Do any of these tools enforce row-level permissions for customers? None of the four internal tool builders ship native row-level policies as of September 2026. Gigacatalyst relies on your product's own API permissions, so the rows a customer sees are the rows your product already lets them see.

Is it better to just build the portal with Cursor or Lovable? For a single app for a single customer, often yes. The cost appears when requests keep coming and each generated app needs its own tenant filter, deploy and maintenance.

Why is Gigacatalyst on a list of internal tool builders? Because teams evaluate it against Retool. It solves the same customer request but runs on the product's APIs, so the customer keeps the result at go-live instead of getting a second app.

Which of these has an MCP server? Retool (public beta, OAuth) and Superblocks (Admin MCP on Enterprise, plus a Builder MCP). Appsmith has only community projects, and Budibase has none.

Gigacatalyst turns a customer request into a working dashboard, report or configured app on top of your own product APIs and permissions, so the demo is the real product.

See it on your own APIs

Related comparisons