Compare

You built the app. You should be able to run it without them.

Retool gets the first version onto a screen fast. The trouble arrives later — the app only runs inside Retool, the logic hides where you can’t test it, and the wall shows up once you’re already committed. Here is each documented pain, and the Blueprint decision that answers it.

Sourced, not spun — every point below is our summary of a public thread, issue, or standard, linked to its primary or authoritative source. These are references, not paraphrased testimonials; follow each one and check the claim yourself.

Claims last verified against their sources on 27 August 2026.

Ownership · ⚑ regulated

Your apps run only inside Retool.

Retool apps do export — as Retool’s own JSON or a Toolscript archive, containing queries, components and modules. But the format exists to move an app between Retool instances: cloud to self-hosted, or across your org. There is no build you compile and run on your own infrastructure. Leaving Retool means rebuilding, not exporting.

Retool docs — import and export apps

Blueprint’s answer

The contract is open, portable JSON you own, and the runtime is open-source and self-hosted. Walk away whenever you like — the artifact is yours and keeps running without us.

Maintainability

The logic is buried where you can’t search or refactor it.

When behavior lives inside the builder, developers report you can’t search for where a query or value is used — which turns refactoring into a nightmare. The tool that made the first version fast makes the tenth version fragile to change.

HN 24840559

Blueprint’s answer

The contract describes the screen, not the behavior — zero logic in the JSON. Real logic stays in typed, testable React you can grep, unit-test, and refactor like any other code.

Extensibility

It makes hard things easy and easy things impossible.

The recurring verdict on Retool: it makes hard things easy and easy things impossible — and you find the showstopper only once you’re already committed, too deep to cheaply switch. The abstraction is generous until the one thing you need sits just outside it.

HN 42131783

Blueprint’s answer

The escape hatch: anything the closed 36-atom catalog doesn’t cover, you drop in as real, typed React (custom nodes and slots). The wall always has a door, so you never build into a corner.

Compliance · ⚑ regulated

A hosted UI layer makes the vendor’s breach your breach.

When your UI layer is a hosted third party, its incidents become yours. In 2023 a Retool breach — via SMS phishing and an MFA-sync weakness — reached 27 cloud customers, all in crypto, and roughly $15M in assets was reported stolen at one of them, Fortress Trust. Self-hosting removes that shared blast radius.

BleepingComputer — Retool breach The Hacker News — Fortress Trust

Blueprint’s answer

Auditable by design: a versioned, diffable contract you compile and ship yourself, self-hosted with no data egress. There’s no shared platform to breach — “prove this screen behaves” becomes a diff you hand an auditor.

Economics

Priced and shaped for internal tools — not for shipping to customers.

The consistent read from practitioners is that Retool is built and priced for in-house use cases, and its low-code core still needs SQL and JavaScript for anything complex. “No-code speed” quietly becomes trapped, per-seat logic you can’t freely code-review or deploy to your own users.

HN 42131783

Blueprint’s answer

The contract is diffable, versionable, and reviewable like code, and the real logic is real code — no per-seat builder standing between you and the app you ship to your own users.

Own it end to end

Keep the speed. Lose the lock-in, the buried logic, and the wall.

Get early access The full reality check

Also compare: Builder.io · Plasmic