vs 
Compare
Retool or custom code for your internal tool?
Both are good. They are good at different stages, and we build on both. This is how we decide.
In short
Use Retool when a small team needs an admin panel or operations tool on top of data you already have, and speed matters more than control. Move to custom code, usually Next.js on Supabase, when the tool has many users, outside users such as customers or suppliers, complex logic, or a per-user cost that has outgrown the value. We have moved several clients from Retool to custom code once they reached that point.
-
Retool
Best for Internal admin panels and operations tools for a small team, built fast on existing databases and APIs.
- Fast to build tables, forms and approvals
- Connects to most databases and APIs out of the box
- Workflows and a database included
- Priced per user, which grows with the team
- Harder to build for outside users such as customers
- Logic spread across many queries is hard to test and review
-
Custom code (Next.js and Supabase)
Best for Tools with many users, outside users, complex rules, or a long life ahead of them.
- No per-user platform fee
- Full control of the interface, permissions and logic
- Tested, reviewed and versioned like any software
- Takes longer to build the first version
- Needs engineering ownership after launch
- You maintain what a platform would have handled
Side by side
Where they differ.
| Retool | Custom code (Next.js and Supabase) | |
|---|---|---|
| Time to first version | Days to a few weeks | A few weeks |
| Cost as users grow | Rises with each user | Mostly flat; hosting scales with use |
| Outside users | Possible, but not its strength | Built for it |
| Complex business rules | Spread across queries and scripts | Written, tested and reviewed in code |
| Who can change it | Anyone trained on Retool | An engineer |
| Moving later | Data stays in your database; screens are rebuilt | Not applicable |
How to choose
Pick by the situation, not the brand.
- 01
A team of a few people needs an admin panel on data you already have
Retool - 02
Customers, suppliers or partners will log in
Custom code - 03
The per-user bill now costs more than an engineer would to maintain code
Custom code - 04
You need it next week and expect it to change often
Retool
Questions
Can we start on Retool and move to custom code later?
Yes, and it is often the right order. Keep the data in a database you own, such as Postgres or Supabase, not only in Retool’s own database, and moving later means rebuilding screens, not migrating data. We have done this move for clients, including an order system and a price tracker.
Is custom code always more expensive?
The first version usually costs more. Over a few years, with many users, custom code is often cheaper because there is no per-user fee. The audit puts both numbers side by side.
What does SBD charge?
Internal tools start at $3,000 and multi-module systems at $5,000, each at a fixed price set after a $500 Automation Audit that is credited to the build.
Related: Retool consulting, Supabase consulting, Internal tools, Build vs buy tool, Retool portfolio. All comparisons.
Not sure which fits?
We build on both. We will tell you which.
On a discovery call we look at your data, users and volumes and tell you which option fits now, and what would make you move later.
Book a discovery call