Alternatives to Retool
Retool is a hosted canvas for building internal tools over your data, with the widest integration catalogue in the category. Teams leave for two reasons, and they are almost always the same two: the per-user price as the tool succeeds, and handing a third party a credential to the production database.
Published by Rebase, which is one of the tools on this page. Every other entry is described by what it is good at, several of the recommendations below are not us, and there are no prices anywhere — competitor pricing changes quarterly and a stale number is worse than none.
Start from why you are leaving
Almost nobody wants "the best alternative". They want the one that fixes the specific thing that broke. Find your row.
“The per-seat bill grows every time someone new needs access”
Rebase, Budibase or AppsmithAll three are open source and self-hostable, so the eleventh person who needs read access does not change the bill. Rebase's hosted option is priced per resource rather than per seat.
“We cannot give an outside service database credentials”
Anything self-hostedSelf-hosted means the tool sits with the database instead of reaching into it, and no credential leaves your network.
“Rebuilding every screen after a schema change”
RebaseScreens are generated from the collection definitions, so a new column appears in the table, the form and the API at once. A canvas builder keeps whatever you drew.
“We mostly need people to edit rows in a grid”
NocoDBA spreadsheet interface over the database, which is often the whole actual requirement and takes an afternoon.
“We mostly need people to read numbers”
MetabaseA surprising share of internal-tool requests are reporting requests. Metabase answers those directly and does not pretend to be an operations surface.
“We need to join Stripe, Salesforce and three databases”
RetoolHonestly, stay. The integration catalogue is the product and nothing open source is close to it.
8 alternatives to Retool
Ordered roughly by how often each one turns out to be the answer, not by any score. Where a head-to-head exists, it is linked.
- 1
Rebase
That's usOpen source· BothBest for: A back office generated from your Postgres schema, with no per-seat cost
A Postgres backend — REST API, typed SDK, auth, realtime, storage, functions, cron — plus an admin panel generated from the same TypeScript collection definitions. Row-level security is written in code and compiled to real Postgres policies, so authorization is enforced by the database rather than by the layer in front of it. Connects to a Postgres database that already exists.
- 2
Budibase
Open source· BothBest for: Self-hosted internal tools, built by dragging
A low-code builder for internal apps over a database or an API, self-hostable and open source. The nearest open equivalent to Retool's model — you draw screens, and they stay drawn, which is fine until a schema change means visiting all of them.
- 3
Appsmith
Open source· BothBest for: Internal tools with a lot of custom JavaScript
A drag-and-drop internal-tool builder with a wide set of data connectors and JavaScript everywhere. Self-hostable. Same trade as every canvas builder: fast to a first screen, linear cost per screen after that.
- 4
NocoDB
Open source· BothBest for: A spreadsheet view over a database, for non-technical users
Turns a SQL database into an Airtable-like grid, with views, forms and automations. Excellent when the requirement is genuinely 'let the ops team edit rows'. Less suited to being the backend of an application, which is a different job.
- 5
Directus
Source-available (MSCL)· BothBest for: A mature editorial interface over an existing database
Wraps a SQL database in a REST and GraphQL API and a well-built admin app, and it will work with a schema you already have. Permissions are enforced in the Directus layer rather than in the database, and the app owns a set of its own tables.
- 6
Metabase
Open source· BothBest for: Asking questions of the data, not editing it
Dashboards, exploration and reporting over a SQL database, usable by people who do not write SQL. Worth naming here because a good share of 'we need an admin panel' turns out to be 'we need to look at the numbers'. It is read-oriented and not a place to run operations.
- 7
Django admin
Open source· Self-hostBest for: Teams already writing Python
The original batteries-included admin, and still one of the best if your backend is Python. It is tied to Django's ORM and to server-rendered templates, so a separate frontend still needs an API you write and maintain yourself.
- 8
Retool
Proprietary· BothBest for: Joining many data sources quickly
The most complete integration catalogue in this category — databases, Stripe, Salesforce, S3, arbitrary REST — and a very fast path to an internal screen across several of them. Priced per user, which is what makes an internal tool expensive precisely as it succeeds.
Rebase and Retool, answered
What is the best open-source alternative to Retool?
Budibase and Appsmith are the closest in kind — both are self-hostable drag-and-drop builders with a similar model. If your data is mostly in Postgres and you would rather the interface followed the schema than be drawn screen by screen, Rebase is a different answer to the same problem: the panel is generated from collection definitions, and the API comes with it.
Why is Retool so expensive?
Because it is priced per user, and internal tools succeed by being used. The cost lands exactly when the tool starts working — the tenth colleague who wants read access to a dashboard is a line item. Self-hosted alternatives remove the per-seat dimension; that is usually the entire reason a team moves.
Can I self-host Retool?
Yes, and if the concern is only where the software runs, that is the smallest possible change. It does not remove per-user pricing, so if the bill is the reason you are looking, self-hosting Retool does not address it.
What is the difference between a low-code builder and a generated admin panel?
Where the screens come from. A builder gives you a canvas: you place components and bind them to queries, once per screen, and they stay as you left them. A generated panel derives the screens from the schema, so a new field shows up everywhere at once — less control over any single screen, far less maintenance across all of them.
Do I need a separate backend as well?
With a builder, usually yes — it draws the interface and something still has to serve your application. Rebase is both: the same collection definitions produce the REST API and typed SDK your app uses and the admin panel your team uses, against one database with one set of policies.
Don't take our word for it.
The comparison that matters is the one you run. Point Rebase at a Postgres database you already have and see how it holds up next to Retool.