How to Build an Internal Admin Dashboard With Retool
Retool is a low-code platform for internal tools. You connect a database or API, drag in a table and a few buttons, and wire them to queries. No React, no routing, no deployment pipeline for a tool only your team will use.
Quick answer: Create an app, add a resource (Postgres, REST API, etc.), drop a Table component, bind it to a query, and add a form for edits. A working admin panel takes a few hours, not a sprint.
The trade-off is real: you trade full control for speed and standardization. For internal tools, that is usually a good trade. For anything customer-facing, it usually is not.
How do you connect a data source?
Add a resource once and every app can use it. Retool supports Postgres, MySQL, MongoDB, REST and GraphQL APIs, and more, with credentials stored server-side.
-- A query named getOrders
SELECT id, customer, total, status, created_at
FROM orders
WHERE status = {{ statusFilter.value }}
ORDER BY created_at DESC
LIMIT 100;The double braces are bindings. Type {{ }} in any query or component property and you can reference another component’s value. That is the core mechanic of the whole builder.
How do you lay out the UI?
Drag a Table onto the canvas, then bind its data to {{ getOrders.data }}. Columns appear automatically from the query result. Add a Select for the status filter and bind its value into the query as above; the table refreshes when the filter changes.
For editing, add a Form component, pre-fill it from the selected row ({{ table1.selectedRow }}), and run an update query on submit.
How do you handle writes safely?
- Use parameterized queries —
{{ form1.data.total }}rather than string concatenation. - Gate destructive actions behind a confirmation modal.
- Log who changed what in an audit table you control.
- Test with a read-only database role first.
How do permissions work?
Retool has built-in users, groups, and a permission system that can restrict apps, resources, and even individual queries. For internal tools, mapping to your SSO groups is the usual approach, so no separate account list to maintain.
What does Retool cost?
| Plan | Rough price | Fits |
|---|---|---|
| Free | $0 | Up to 5 users, limited apps |
| Team | Per user/month | Small teams, standard apps |
| Business | Higher per user | SSO, granular permissions |
Self-hosted plans exist for teams that need data residency. Check current pricing — the tiers and caps change, and the free tier’s user limit is the constraint that pushes most teams up.
What are the downsides?
- You are tied to the platform; migrating off means rebuilding.
- Complex custom interactions hit the limits of the component model.
- Per-seat pricing gets expensive if you want to give access to many people.
- Multi-page apps with heavy logic become hard to debug without discipline.
When is Retool the right choice?
Internal tools where speed matters more than pixel-perfect control: admin panels, ops dashboards, data correction screens, review queues. If you would otherwise spend three weeks building and deploying a React app for five users, this is the obvious call.
Who this suits: ops, support, and data teams who need tools now and have no frontend bandwidth. Who should skip it: product teams building customer-facing interfaces, where the platform constraints and per-seat cost rarely make sense.
Quick Summary
- Retool builds internal tools by binding components to queries.
- Connect a resource once, then reference its queries with
{{ }}bindings. - Parameterize writes and confirm destructive actions.
- Free tier caps at 5 users; Team and Business are per seat.
- Great for internal dashboards, wrong for customer-facing products.
