The short version
Retool is a platform for building internal software from prebuilt components wired to your databases and APIs. A custom internal tool is a web app your engineers or a partner write in code, usually React with a backend and Postgres.
The decision usually turns on three things: how many people will use it, how unusual the interface is, and how central it is to the business.
Where Retool wins
Speed for standard screens. Tables, forms, detail views, charts and approval buttons over an existing database take days in Retool. Writing the same thing by hand, with permissions and validation, takes weeks.
Security plumbing included. Single sign-on, user groups, permissions and audit logs come with the platform, depending on plan. Building those well in a custom app is real work that adds no visible features.
Many small tools. If operations needs ten small admin panels, Retool lets one engineer build and maintain all of them. Retool Workflows add scheduled jobs and alerts next to the apps.
Engineer time. Retool is built for developers. It lets them write SQL and JavaScript where it matters and skip front-end boilerplate everywhere else.
Where custom tools win
Large user counts. Retool bills per user. A tool used by 300 warehouse staff or outside partners can cost more over a few years than building it once.
Core workflows. When a tool is how your team quotes, schedules or fulfills orders every day, a purpose-built interface with the exact steps and shortcuts can save real time. Our internal gifting portal case study is an example of an internal portal built in code.
Unusual interfaces and AI. Drag-and-drop planners, maps, mobile use and agent-driven screens are easier to build in code. So are AI features that need tight control over tools and cost, such as natural-language SQL reporting.
Ownership. The code lives in your repository and runs anywhere, with no platform pricing changes to absorb.
What we recommend
Start with Retool for admin panels, back-office screens and dashboards with a modest number of users. Build custom when the tool is core to operations, has a large or external user base, or needs an interface or AI behavior that components cannot express. It is also common to keep the data in Postgres so either option can sit on top of it, as covered in Airtable vs Postgres for operations data. If you want a second opinion on a specific tool, start here.