Retool
Builds internal tools on top of databases and APIs with drag-and-drop components and AI app generation.
- Free plan or free tier
- Open source or self-hostable
Internal tools are the screens your team uses behind the scenes: a support console to look up customers, an approval queue for refunds, an inventory dashboard, an admin panel for your own product. Internal tool builders let you assemble these from tables, forms, charts and buttons connected to your databases and APIs, without a front-end developer.
The work is mostly about data access. You connect the builder to a database or service, write or generate the queries, and decide what each person may see and change. AI features in these tools can draft whole apps from a description, write SQL, and explain errors, which helps people who know the data but not the syntax.
Because these apps touch production data, the details that matter are less visible than the drag-and-drop editor. Look at how each tool handles user roles, audit logs and separate environments for testing. Check whether it can run on your own servers if your data must stay inside your network, and how sign-in connects to the accounts your team already uses.
Pricing usually counts builders and end users separately, and it can change a lot as more staff use the apps. Start with one tool that removes a real daily pain, measure the time saved, and only then roll the platform out to other teams.
What a featured listing costs ยท from $99 a month
Builds internal tools on top of databases and APIs with drag-and-drop components and AI app generation.
Open-source builder for internal apps and admin panels, with AI features and a self-hosted option.
Open-source low-code platform for internal tools, forms and approval workflows that you can self-host.
Platform for building internal apps, workflows and scheduled jobs with AI assistance and central access controls.
Low-code builder for internal tools and admin panels connected to databases and APIs, with an AI app generator.
Microsoft low-code app builder for business apps, connected to Microsoft 365 and Dataverse, with Copilot help.
The best first project is usually something people already do by hand every day: copying data between two systems, checking a record before approving it, or answering the same customer lookup again and again. An internal tool that removes one of those chores pays for itself quickly and shows the rest of the company what the platform can do.
Keep the apps simple and documented. Name queries clearly, write a short note on each screen about what it is for and who owns it, and review access every few months as people change roles. Internal tools tend to grow quietly, and a little order early on saves confusion later.
Typical examples are a customer lookup that pulls account, order and support history onto one screen, a refund or discount approval queue with a log of who approved what, a stock dashboard that warns when items run low, and an admin panel for editing records in your own product. Each one replaces a spreadsheet, a chain of emails or a request to an engineer. When choosing a builder, try one of these on your real data during the trial period and see how long it takes your team to finish it.
It can be, if you set it up with care. Use a database user with only the permissions the app needs, keep a separate staging environment, turn on audit logs, and limit who can edit apps as well as who can use them.
Someone needs to understand your data and write or check queries. Many operations and data people learn these tools without being full developers, and AI help makes the query writing easier.
Open-source builders such as Appsmith and Budibase can run on your own servers, which helps when data must stay in your network. You take on hosting and updates yourself in exchange for that control.
Database apps keep the data inside their own tables. Internal tool builders usually sit on top of databases and APIs you already run, which suits companies with existing systems and larger data volumes.