Retool → Appsmith
What it saves, what actually moves, what you rebuild — and the thing that catches people.
What it costs, and what it saves
Retool, as listed on its pricing page on 2026-10-03: Free covers up to 5 users. Team is $10/month per builder and $5/month per internal user on annual billing ($12 and $7 on monthly billing). Business is $50 per builder and $15 per internal user on annual billing ($65 and $18 monthly). Enterprise is quoted, and on self-hosted deployments SSO, Git source control and audit-log streaming are Enterprise-only. Appsmith, as listed the same day: Free is $0 (up to 5 users on its cloud, 5 workspaces, 3 Git repos, 3 standard roles); Business is $15/month per user for up to 99 users; Enterprise is $2,500/month for 100 users. The self-hosted Community edition is free under Apache-2.0. Worked example from these list prices: 3 builders and 20 internal users cost $130/month on Retool Team (annual) or $450/month on Retool Business (annual), against $345/month on Appsmith Business, which charges every workspace member the same rate. On self-hosted Community the licence cost is $0, plus your own server; Appsmith's docs ask for at least 8 GB of RAM for the all-in-one Docker container.
Moves cleanly
Your data does not move at all. Both tools query your existing databases and APIs, and Appsmith has connectors for PostgreSQL, MySQL, MongoDB, SQL Server, Oracle, Snowflake, Redshift, DynamoDB, REST and GraphQL, among others. The SQL text of each query and most of the JavaScript logic can be copied over one query at a time and wired back to the new widgets.
You rebuild
You rebuild every screen. Retool's export (JSON or a Toolscript ZIP) contains queries, components and modules but no resources, and Appsmith imports only its own JSON export, so nothing reads a Retool app directly. You recreate layouts, component wiring, permissions, workflows and datasource credentials by hand.
What Retool costs you today
Free for up to five users. Team runs around $10 per standard user and $50 per builder per month; Business is roughly $50 per user with builders higher again. The mechanic that surprises people is the builder-versus-viewer split — anyone who edits an app costs several times what a viewer does, and internal tools have a way of accumulating editors. Self-hosted deployment exists on higher tiers and does not remove the per-user licence. Figures checked 2026-08-07.
What actually holds you in
High, and unusually so, because the app IS the vendor's format. There is no meaningful export: an application built in Retool exists as Retool's internal representation, and moving it means rebuilding it in another builder. Queries and SQL are portable; the interface, the state wiring and the component logic are not. This is the category where the number of tools you have built is the real switching cost.
What you are moving to
Appsmith is the most direct open replacement for Retool: a drag-and-drop builder with widgets, JavaScript anywhere, and connectors for the major databases and APIs. It self-hosts with Docker or Kubernetes and the core is Apache-2.0, which is the most permissive licence of the serious options here. Around 40.6k stars. If your reason for reading this page is per-builder pricing, this is the first thing to try, and the conceptual jump from Retool is small enough that an existing Retool user is productive quickly.
Free and open source to self-host. Paid cloud and enterprise tiers.
Appsmith strengths
- Closest feature match to Retool of anything open
- Apache-2.0 core — the most permissive licence among serious options
- Self-hosts on Docker or Kubernetes with no per-builder fee
- Large widget library and broad database connector support
What you give up
- Some governance and SSO features sit behind the paid tier
- Fewer third-party integrations than Retool out of the box
- You now operate a service, including upgrades and backups
- Polish trails Retool in places, particularly complex state
The migration, step by step
- 1Take an inventory of each Retool app. Export it to JSON or a Toolscript ZIP as a record, and list its resources, queries, transformers and modules. Note which resources have 'Disable converting queries to prepared statements' turned on.
- 2Deploy Appsmith: run the Community image (`appsmith/appsmith-ce`) or the commercial one (`appsmith/appsmith-ee`) in Docker on a host with at least 8 GB of RAM, or start on Appsmith's cloud. Pin a version tag rather than `latest`.
- 3Recreate each datasource in Appsmith using the same database users, ideally read-only users for reporting apps. Re-enter the credentials, because neither Retool's export nor Appsmith's import carries them.
- 4Rebuild one app at a time. Paste each query's SQL, move transformer logic into JS Objects, rebuild the layout with Appsmith widgets and recreate role-based access. If Retool Database held app data, copy it into a PostgreSQL database you run first.
- 5Run both versions side by side with a small group of users for one to two weeks. Check that every write query produces the same result against the same records in both apps.
- 6Cut over one app at a time by moving users and bookmarks to the Appsmith URL. Keep the Retool app read-only until a full business cycle has passed, then remove its write access and archive the export.
The gotcha
The SQL most likely to break is SQL that builds table names, column names or IN lists from JavaScript. Retool converts PostgreSQL queries to prepared statements by default, but an admin can turn that off for a whole resource with 'Disable converting queries to prepared statements', so dynamic SQL works in every query on that resource. Appsmith's docs state that prepared statements 'are turned on by default' for each query. They list the cases that fail while the setting is on: dynamic table names, clauses added by conditional code, dynamic WHERE columns, and arrays bound into IN clauses. PostgreSQL can use `= ANY` instead of IN. Each affected query needs 'Use Prepared Statement' switched off in its own settings, which removes SQL-injection protection for that query, so check where its inputs come from. One more trap: Retool's own docs say the Free plan's Retool Database is paused after a month of inactivity, which breaks its connection strings. Copy that data out early, while the database is still active.
When to stay on Retool
Stay if your apps depend on Retool Workflows, Retool Database, mobile apps or a large library of shared modules, or if most of your users are internal users. Retool Team prices internal users at $5/month (annual), while Appsmith Business charges every member $15, so a team of mostly internal users can pay less on Retool. Teams with nobody to run Docker upgrades also benefit from Retool's hosted plans.
More Layer 5 migrations
Figures verified 2026-08-07 against vendor pricing pages. Prices change and migrations differ by estate — treat the cost delta as a starting model, not a quote. Rankings and recommendations here are merit-only; affiliate income never changes a verdict. See our methodology.