How to Lock Down Retool Permissions and Row-Level Access
Group permissions, per-resource credentials, row-level filtering and query-level guards that stop a well-meaning internal tool from leaking every customer record.
Drag-and-drop builder for internal admin panels on top of your own database.
Retool is a low-code builder for internal tools: connect a Postgres or REST API, drag a table and a form onto the canvas, bind them to queries, and ship an admin panel in an afternoon. It’s free for up to 5 users; the Team plan starts at $10 per user per month.
Every company has the same problem. A support agent needs to refund an order, and the only tool available is a SQL client and a Slack channel. Retool exists to shorten that loop without pulling an engineer off the roadmap for two weeks.
Queries are real SQL. The UI is React components bound to query results with {{ query.data }}. When the visual builder runs out of road, you drop into JavaScript rather than hitting a wall.
What separates Retool from BI dashboards is that ops teams can act, not just look. That’s also why it becomes a production dependency that nobody documents.
Free covers 5 standard users with unlimited apps. Team is $10/user/mo for standard users but $50 for end users, and adds audit logs, environments and SSO. Business and Enterprise are quoted. The pricing trap is end-user seats: a read-only dashboard for 300 people costs $15,000/mo on Team.
No. Internal CRUD screens, approval flows and dashboards fit almost perfectly. Customer-facing products with specific design requirements will fight the component library every sprint. Budget for one person to own the app’s data model, or you get twelve overlapping admin panels in a year.