Retool

What Retool Actually Is in 2026

Retool is a platform for building internal software: the admin panels, dashboards, approval queues and data-entry screens a business runs on, but nobody wants to build from scratch. You connect it to your own databases and APIs, build the screen, and publish it to your team with permissions already in place.

That much has not changed since our first Retool review. What has changed is how you build.

In 2026 Retool rebuilt its app builder from the ground up. You now describe the app in a chat, and an AI agent generates it as React code you can read in a Code tab and preview live. Retool calls the old drag-and-drop editor the "classic app builder." Classic apps still work, but Retool's own documentation now calls the new builder "where Retool focuses new development."

Around the apps sit four other products:

• Workflows run scheduled or triggered jobs in the background, such as a nightly report or a webhook that updates a record.
• Agents are AI workers that use tools to complete multi-step tasks. They are billed by the hour.
• Retool Database gives you a hosted database if you do not already have one.
• Mobile builds native iOS and Android apps for teams in the field.

There are also new ways in. Retool has an MCP server and, since September, an updated CLI, so you can build in Claude Code or another AI coding tool and deploy the result on Retool. It can also import React apps built elsewhere, including in Lovable and Replit.

Does Retool Save Time?

Yes, on the first version, and by a lot.

The work Retool removes is the work nobody enjoys: logins, user permissions, tables that sort and filter, forms that validate, and the plumbing that connects all of it to your database. In a traditional build, that is weeks of a developer's time before the first useful screen exists. In Retool it is already there.

The AI builder shortens it further. By Retool's own numbers, an app typically takes three to six prompts at about 12 AI credits each, and the Business plan's 3,000 monthly credits cover 36 to 84 apps a month.

Where the time saving is real:

• Admin panels over a database you already have: look up a customer, fix a record, issue a refund.
• Approval queues, where a person has to review something before it moves on.
• Internal dashboards that need to do more than display numbers, such as editing the record behind a chart.
• Ops tools that replace a spreadsheet five people edit at once.

Those all share a shape: a screen, a database, and a person making a decision. That is the shape Retool was built for, and it is where we reach for it. When a client's automation needs a person to approve something, Retool is often where that approval happens, the step we described in where a person should still approve the work.

Or Does It Build More Drag?

This is the part most reviews skip, because it shows up after launch, not during the build.

In May, a customer who had spent almost a year building production systems on Retool posted in the r/Retool community that small teams "can build serious internal platforms with Retool, but operating them in production becomes difficult without access to tooling locked behind Enterprise features." Monitoring, performance visibility, rollback and versioning, they argued, "feel more like basic operational requirements now, not 'enterprise-only' features."

The replies described the same wall from different sides:

• One user said that after a year of building, the backend "became so amazingly slow it was almost unusable," and they were rebuilding in Next.js.
• The original poster reported a page that took eight seconds to load.
• A founder said they migrated their whole product off Retool "in ~2 weeks with Claude Code."
• In a separate thread, a team described apps "getting too big to save."

Retool answered in public. Its head of developer relations wrote that performance monitoring and source control sit in Enterprise "because that's where the need is most acute," that the company is "regularly reassessing where that line should be," and that some of its API is available on the Business plan, with the full API on Enterprise.

None of this means Retool is slow for everyone. Most internal apps are small, and these are self-selected complaints from a community forum. But the pattern is consistent: Retool's time saving comes at the start, and the drag arrives when an app grows into something the business depends on. Plan for that day before you build, not after.

The Vibe-Coding Question

The loudest question about Retool this year is whether it still needs to exist. If Claude Code can build an internal app in an afternoon, why pay per builder for a platform?

Some long-time users have left. One, whose company was built around Retool apps, wrote in September that "as an individual builder, it just makes more sense to use GitHub, Vercel, and Claude Code." Others miss the drag-and-drop editor the new builder replaced.

Retool's own answer is unusually frank. Its head of developer relations said the company recognizes that "building is commoditized," and is betting on letting you build anywhere, whether in its builder, in Claude Code or by importing an app, then deploy on Retool for security and governance. His case for building inside Retool rather than in a general coding tool: "the LLM doesn't have to have all or nothing access to my data sources."

That is the real trade. A reply in the September thread put the other side of it plainly: build it yourself, and getting logins and row-level access right becomes your job, along with keeping your dependencies free of security problems.

So the question is not whether AI can build your internal tool. It can. The question is who is responsible for who can see what once it is live.

Retool Pricing in 2026, Decoded

Retool charges per builder, meaning anyone who created or edited an app or workflow that month, and per internal user, meaning employees who only use the apps. These are Retool's published prices, billed annually. Monthly billing costs more: $12 and $7 on Team, $65 and $18 on Business.

What that means for a real team, billed annually:

Two costs sit outside those numbers:

• Agents are billed per hour of runtime, at rates that vary by AI model, after 20 free hours a month on every plan.
• Usage overages. AI credits do not roll over, and extra workflow runs cost $75 per 5,000 a month.

The number that matters most is not in either table: what Enterprise costs. Retool does not publish it, and it is where source control, SSO and 2FA enforcement live.

What You Only Get on Enterprise

These are the features a growing team tends to need once an internal app becomes something the business runs on. On Retool's pricing page, every one of them is Enterprise-only:

• Git source control, for reviewing changes and rolling back a bad release.
• SSO and SCIM, so access follows your identity provider when people join and leave.
• 2FA enforcement across your organization.
• Your own AI provider key, so AI usage does not draw on Retool's credit pool.
• Self-hosting without limits, including unlimited users and air-gapped deployment.

If your plan is to start on Team and grow, price Enterprise before you commit. In January, a Retool salesperson told one customer, in an email the customer later posted publicly, that "there is active work this quarter to make features like source control more accessible without jumping straight to full Enterprise." As of October, Git is still listed as Enterprise-only.

Retool vs n8n, Zapier and Make

Retool sits in our workflow automation category, but it solves a different problem from the other tools there. They move data between apps in the background. Retool gives people a screen to work in.

Retool Workflows overlaps with these tools for scheduled and triggered jobs. In practice, it usually works best to use Retool for the screens and one of the others for the background automation, rather than forcing either one to do both.

Retool vs Building It Yourself With AI

On lock-in, the picture is better than it used to be. Apps from the new builder are React code you can read in Retool's Code tab, and on Enterprise you can work on them from your own editor through Git. Classic apps export as JSON, in a format meant for moving apps between Retool instances. Either way, the logins, permissions and data connections your app relies on belong to Retool, so leaving means rebuilding those parts yourself.

Who Should Use Retool, and Who Shouldn't

Use Retool if:

• You have a database and a team that keeps asking for "just a quick admin screen."
• A person has to review, approve or correct something in a process you otherwise automate.
• You need audit logs and permissions on internal apps and do not want to build them yourself.
• You already build with AI coding tools and want a governed place to deploy what they produce.

Look elsewhere if:

• You need to move data between apps with no person in the loop. Use n8n, Zapier or Make.
• The app is your product. Customer portals work on Business, but a product you sell tends to outgrow a platform you rent.
• You need Git or SSO and cannot budget for Enterprise.
• You have a developer who will happily own hosting and security, and few people who would build in Retool.

How We Scored It

This Retool review scores it 8.1 out of 10. Here is what sits behind each part of the score.

• Capability: 8.3. Apps, workflows, agents, a database and mobile on one platform, connected directly to your data. It loses points because the features you need to run apps at scale sit on Enterprise.
• Ease of use and integration: 8.0. The AI builder makes the first version fast, and the data connections are excellent. It loses points for the learning curve once an app grows, and for the disruption of the rebuild for teams that knew the classic editor.
• Value for money: 7.8. Team is cheap for small groups, and Business is a big jump. The essentials for running apps seriously are priced on request.
• Support and docs: 8.3. The documentation is thorough and current, and Retool's team answers criticism in public, which is rarer than it should be.

Where Retool Fits

Retool earns its place when the job is a screen on top of your data with a person making a decision. It does not replace your automation tool, and it does not have to be your whole stack.

Identify. Block. Automate.

Identify the work your team still does by hand. Block it into tasks. Automate the ones that need no judgment, and give the ones that do a proper screen, which is where Retool comes in. If you want help working out which is which, book a free 30-minute call.

Automate Today. Excel Tomorrow.

So: before you build your next internal tool, ask what it will need on the day it becomes critical, and whether you are ready to pay for that.