Budibase fits a team that wants an open source internal tool platform it can self-host for requests and approvals, with unlimited users on its free Community plan, while Retool fits a team that wants a hosted builder with AI app generation and governance, billed per builder and per internal user. Where your apps need to run is the first fork.
Picture the request that starts it: someone needs an approval form, a dashboard over a database, or a small admin panel, and a spreadsheet stops coping. Budibase and Retool both answer that, but they're built on different assumptions about where the app lives and who pays for it.
Eight things to confirm before you build
- Where the app has to run: on your own servers, in a vendor's cloud, or in an air-gapped environment with no outside connection.
- How many people will build or edit apps each month, since Retool bills those builders separately from the people who only use the apps.
- How many people will only use the apps, and whether any of them sit outside your company, such as customers or contractors.
- Which datasources you'll connect, such as PostgreSQL, MySQL, MongoDB, Oracle, Snowflake, Google Sheets or a CSV import.
- Whether you need more than one workspace, because the free open source edition of Budibase lists a single workspace.
- How long you need automation logs kept for troubleshooting and audit.
- Whether AI app generation from a prompt matters, or a visual builder over your own data is enough.
- How you'd move apps out later, through workspace export, code import or a fresh rebuild.
The first two matter most. Where the app runs decides whether the free routes are even open to you, because Budibase's free plan is self-hosted and Retool's is cloud only. The split between builders and users decides how a Retool bill grows, since the two are counted separately.
The datasource question is quicker to settle but easy to skip. Both tools connect to common databases, so the useful check is whether the specific system your approvals live in today is on each list, and whether you'd be reading from it, writing to it, or both. I'd write the answers to all eight down on one page before opening either builder, so the trial is a test of your answers rather than a tour of features.
Where Budibase sits
Budibase describes itself as an open source platform for enterprise processes: internal apps, automations and AI agents built around jobs such as requests and approvals. Its product menu includes a Service portal that brings apps, requests and approvals together in one place.
The Community plan is free to self-host on your own infrastructure, with unlimited users, apps, agents and automations. Budibase 4.0 is pitched around AI agents, apps and automations, and the app builder, agent builder and automation builder all sit in the open source column of its comparison table. Its docs list datasources including PostgreSQL, MySQL and MariaDB, MongoDB, Oracle, Snowflake, Google Sheets and CSV import.
If you'd rather not run servers, Budibase Cloud is hosted by Budibase and billed monthly, with limits on creators, end users and monthly actions. A custom Enterprise plan sits above both.
Where Retool sits
Retool is a hosted platform for building internal apps and workflows, with an AI app builder, agents and governance controls. Its new app builder generates apps from a prompt with security and governance built in, which suits a team that wants to start from a description rather than a blank canvas.
It can also take work from elsewhere: apps built on other platforms can be imported as React code through a ZIP upload or GitHub sync. Its docs describe a Data Sources section for connecting to API and database resources.
Retool defines a builder as a user who created or edited an app or workflow in the billing cycle, and builders are billed separately from internal users. The Free plan includes a small number of users and a pool of AI credits each month. AI credits are pooled across the account and renew monthly without rolling over. External users and embedded apps are included from the Business plan, not on Free or Team, and self-hosted or air-gapped deployment is listed under Enterprise.
How each bill is counted
Budibase has two routes. Self-hosting the Community plan is free, and your cost is the infrastructure and the time to run it. Budibase Cloud is a monthly plan with set limits on creators, end users and monthly actions, and Enterprise is custom.
Retool bills per builder per month plus per internal user per month, with annual billing bringing a discount. So the two numbers to estimate are how many people edit apps in a typical month and how many only use them. AI credit pools also differ by plan. Today's figures for both tools sit on each vendor's pricing page.
Those models reward different team shapes. A team with many users and few builders should price Retool carefully by role. A team with a server and someone to look after it should price Budibase by infrastructure and time, not licence.
Do you make internal tool builders and low-code app platforms? Tool makers can ask to be considered for a featured place on this list.
Want AI doing the heavy lifting in your marketing?
I build the systems that handle the boring 80 percent, so you get your week back. Done properly, with the human kept in.
What the free plans leave out
Both free plans look generous, and both have edges worth reading. Budibase's free Community plan is self-hosted with unlimited users, but its own comparison table limits the open source edition to one workspace and one day of automation log retention. That's fine for a single team's approvals app, and it's tight if several departments want their own space or an auditor wants to see last week's automation runs.
Retool's free plan runs on Retool Cloud only and is capped at five users, and self-hosted or air-gapped deployment is listed only under Enterprise. So a team that must keep data on its own servers can't test that setup on the free plan.
Where each one runs short
Budibase asks you to run it if you want it free, which means patching, backups and uptime are yours. Its open source edition's single workspace and short log retention may push a growing team towards Cloud or Enterprise.
A team can also outgrow the self-hosted free route without noticing. Workspaces and log retention are the two lines to watch, and both are set out in Budibase's own comparison table, so read that table against your plans for the next year, not just the first app.
Retool's per-builder and per-user billing can grow quickly with headcount, external users need the Business plan, and self-hosting needs Enterprise. Its AI credits don't roll over, so a quiet month's unused credits don't carry into a busy one.
Moving apps and data across
Budibase has a documented page on exporting and importing workspaces, so apps can be moved between Budibase instances, for example from a self-hosted test server to Cloud. Because Budibase connects to external databases such as PostgreSQL, MySQL and MariaDB, MongoDB and Oracle, the same data sources can be reconnected to a new tool if you leave.
Retool can import front-end code built elsewhere by ZIP upload or GitHub sync, and its page names Lovable and Replit as sources, not Budibase. So moving from Budibase to Retool is a rebuild of the interface on top of the same databases, connected through Retool's Data Sources section. For the wider field, my guide to internal tool builders covers other options, and the list of Budibase alternatives goes deeper on that side.
An approval app, built twice
Take a real request process, such as equipment requests that need a manager's sign-off, and a small table in a database you already use. Build the same app on both in an hour.
On Budibase, start a Community install or a Cloud trial, connect the table, build a form for requests and a view for managers, and add an automation that notifies the manager. Then look at the automation log and note how long it keeps entries on your edition.
On Retool's free plan, describe the app to the AI app builder, connect the same table through Data Sources, and adjust the generated screens. Count how many people would be builders and how many would be internal users in real life.
Finish by going back to the checklist at the top. Budibase fits the team whose answers pointed to self-hosting and many users; Retool fits the team whose answers pointed to hosted speed and AI generation.
Want your tool on this list? Featured spots and reviews here are paid partnerships. Here's how to partner with me.


