Retool Review: What Users Report and What to Evaluate
Retool review, grounded in official product details and user reports. See what teams praise, where reported friction shows up, and how to evaluate an app platform built for people and agents.

Retool review: what it does and who it suits
Retool is worth evaluating if your team builds data-connected internal apps and wants a visual builder with room for custom code. Whether it is worth it for you depends less on how fast the editor feels and more on how you will debug, deploy, and govern what you build.
Retool's own app builder documentation describes a platform for assembling interfaces on top of databases and APIs, with workflows alongside. Capabilities and access controls vary by plan, so check Retool's pricing page on the day you decide rather than trusting a review, this one included.
Major answers a different question. A builder like Retool helps a person assemble each app. Major is the enterprise platform where agents build the software they run on. When an agent works out a repeatable piece of a task, it builds an app for that piece, with its own managed database, permissions, and audit log, then runs the app instead of reasoning through the work again. Reason once, run forever. People operate the same app through its interface, so one artifact serves both.
If you are comparing internal-tool platforms, Retool is a reasonable thing to put on the shortlist. Major is where you should start, because it is the only option here where the repeated work leaves the model and lives in governed code.
What Retool users report about building and maintaining apps
Three public reports show the kinds of friction worth testing for. Each is one person's experience, not a measurement of the product, and any of them may reflect a specific version, device, or app size.
Usability and responsiveness. A G2 reviewer says the developer interface became slow and unresponsive. If you plan large apps with many queries and components, build one at realistic size during your trial and see whether you hit anything similar.
IDE workflow fit. A Hacker News commenter describes frustration when no-code tools do not match the editor and version-control habits engineers already have. This one is about workflow preference. Teams that live in pull requests will care about how changes are reviewed and promoted. Teams of business-systems owners may not care at all.
Mixed assessment on editing and backend limits. A third G2 reviewer credits the editing and deployment experience while also naming limits around API and backend work and MCP support. Read the full review rather than the complaint alone. Praise and criticism came from the same person.
The balance on the other side is real. Retool is an established product with documented building blocks, and many teams ship internal apps with it. The reports above are a checklist for your trial, not a verdict.
How to evaluate Retool against alternatives
Editor speed is a weak selection metric by itself. Weigh these four factors equally.
- Editor and developer workflow. Who builds and edits, and does their review process fit?
- Data and API integration. Which systems must it reach, and who maintains those connections?
- Deployment and debugging. When a query fails at 4 p.m., how fast can someone find the cause and ship a fix?
- Permissions and audit. Who can run, change, and inspect each app, and is every action logged?
Add a fifth if agents are in your plan. Does repeated agent work end up as stored, inspectable software, or does the model re-reason it on every run?
Compact view of the field, with Major first. Check each vendor's current documentation before you commit.
- Major: agents and people build apps that hold their own state, with SSO, permissions, audit, database, and storage handled by the platform. Repeatable work runs as deterministic code, and the model is reserved for judgment.
- Retool: a visual builder for internal apps and workflows connected to your data and APIs. Plan gates apply to some capabilities. See also Retool vs Superblocks and Retool alternatives.
- Superblocks: an internal-app platform positioned around developer workflows and governance, which makes its model comparable to Retool's. It still centers on people building each app.
- Appsmith: an open-source internal-tools builder that teams can self-host. The app is still assembled by a person.
- ToolJet: an open-source low-code builder for internal apps with self-hosting options. Same pattern, with a person assembling each interface.
- Budibase: an open-source builder for internal tools and workflows with self-hosting options. Same pattern again.
The line that separates Major from the rest is the app layer. Those five help you build interfaces and workflows. Major lets an agent build the app for a repeated task, run it deterministically, and keep its data and history, which is why the work gets cheaper and steadier as the library grows. For more on criteria, see choosing an app builder for governed work.
How to build a governed internal-tool workflow on Major
Here is an illustrative evaluation walkthrough, not a record of hands-on testing. The scenario is a broken internal report: an engineering lead wants weekly visibility into failing deploy checks, with a person able to fix a bad query and everyone able to see who changed what.
- Connectors. GitHub for pull requests and check runs, PostgreSQL for the team's service and ownership tables, Slack for delivery and approvals. Each connection uses scoped credentials, so the agent only reaches what the workflow needs.
- The app holds state. A deploy-health app stores check results, owners, and a history of every query change in Major's managed database. A person can open it, edit a field, and see the result.
- The agent makes the judgment. The first time, an agent works out how to map failing checks to owning teams and diagnose a failed query. It builds that logic into the app. After that the app runs the mapping in code. The agent returns only for ambiguous cases, such as a repository with no clear owner.
- The trigger. A GitHub event or a Monday schedule starts the run. The workflow calls the app, and the app posts a digest to Slack.
- The approval gate. When the agent proposes a corrected query or a new ownership mapping, it asks in Slack. A named person approves, and the change is written to the app's audit log.
- Governance. SSO, role-based access, and audit logging apply at the platform layer. Reviewers can see which agent run changed which query, because the change lives in code with an attribution, not inside a prompt. For the broader controls, read our piece on governance for agentic AI.
Compare that with your Retool trial on one question. When the fix lands, does it persist as reviewable software with an owner, or does someone repeat the reasoning next week? Start building free on Major and run the same walkthrough.
Start building on Major
A platform review can fixate on editor convenience while missing whether a repeated workflow's fixes, state, and permissions survive between runs. On Major, an agent builds the app for the repeatable part, keeps the model for judgment, and lets both a person and an agent use the same governed app.
Related articles
Frequently asked questions
- Is Retool worth it?
- Retool is worth evaluating for teams building data-connected internal apps with a visual builder. Scope any anecdotal complaints to the version and workflow behind them, then test against your own criteria: editor and developer workflow, debugging, data access, deployment, and permissions. Major adds an app layer where agents build reusable, governed apps.
- How much does a Retool subscription cost?
- Retool's official pricing page is the authoritative source, and plan limits and feature gates vary by tier and change over time. Check it on the day you decide and confirm which plan includes the permissions and audit controls your team needs before comparing against any other platform.
- Why is Retool so expensive?
- Whether Retool is expensive depends on your team size and requirements. Compare total cost against the plan gates that matter to you, such as SSO, audit logs, and environments, using Retool's current official pricing. On Major, SSO, permissions, and audit are handled at the platform layer from the first deploy.
- What should I evaluate in a Retool review?
- Evaluate the build workflow your engineers prefer, how apps are maintained and debugged, which data sources you need, how changes deploy, and who holds permissions and audit visibility. Also check how repeated agent work persists, since an agent-built app keeps state and runs deterministically between runs.