Your tools live in Retool, not your app
Admin built in Retool isn't part of the app you ship to clients or run in production — it's a separate system, with its own auth and its own bill.
microservices.sh vs Retool
Retool is genuinely fast for ad-hoc internal tools — drag-drop UI over any data source, nothing to deploy. But those tools live in Retool, priced per user, separate from the app you ship. The admin-shell module gives you schema-driven CRUD with RBAC and audit as part of your own app, in code you own.
Compared against: Retool, Forest Admin, Appsmith
Credit where due
The gap
Admin built in Retool isn't part of the app you ship to clients or run in production — it's a separate system, with its own auth and its own bill.
Cost scales with every internal user, and you never own the admin you built.
It's internal-tooling-shaped; you can't hand it to a client as part of the product they own.
Side by side
| Retool | microservices.sh | |
|---|---|---|
| Where it lives | Retool cloud | Your app, your Cloudflare |
| Shape | Standalone internal tools | Admin that ships with your app |
| Access control | Retool roles | org-team-rbac + per-action checks |
| Audit | Add-on tiers | audit-log module, append-only |
| Pricing | Per user | Flat — in your plan |
| Own the code | No | Yes — source-visible |
You need ad-hoc internal dashboards across many data sources, fast, with nothing to deploy.
The admin is part of the app you ship and own — on your infra, in your repo, handed to the client with everything else.
Retool is the fastest internal-tools builder; admin-shell is admin you own. When the admin surface ships with your app — RBAC, audit, your Cloudflare, your repo — compose it as a module instead of renting another dashboard.