Every engineering team eventually needs an internal admin panel: a tool for support to refund an order, for ops to update a customer record, for finance to approve a payout. Building that from scratch burns real engineering time on something that generates no product value. Retool, Appsmith, and ToolJet exist to solve exactly that problem, and the decision between them is really a decision about whether you want to pay for polish or spend engineering time avoiding the bill.
Retool: The Paid Standard for a Reason
Retool launched in 2017 and is used internally by Amazon, DoorDash, and NBC to build operational tooling without dedicating frontend engineers to internal apps full-time. The builder works by dragging pre-built components (tables, forms, charts, maps, file uploaders) onto a canvas and wiring them to data sources through SQL queries or API calls. Supported connections include PostgreSQL, MySQL, MongoDB, Redis, DynamoDB, Snowflake, REST APIs, GraphQL, Google Sheets, and S3, which covers nearly anything a real internal tool needs to touch.
Pricing: free for up to 5 users with unlimited apps, Standard at $10/user/month adds custom branding and audit logs, Business at $50/user/month adds a self-hosted option, SSO, granular permissions, and environments. That jump from $10 to $50 per user is steep, and it's specifically gating self-hosting behind the top tier, which matters if data residency is a requirement rather than a preference.
Reddit engineering threads consistently recommend Retool for exactly this use case: giving non-technical stakeholders operational access without building a custom admin panel from the ground up. The consistent caveats are real too. Retool is not built for customer-facing applications; performance and customization limits show up fast if you try to stretch it past internal tooling. And the per-user pricing at $50/month for the tier most companies actually need (self-hosted, SSO) adds up quickly for a 20-person ops team: $1,000/month for tooling that generates no revenue directly.
Appsmith: Free, Self-Hosted, Genuinely Capable
Appsmith is open-source with 39,000+ GitHub stars, and the source is fully available on GitHub to inspect or self-host without a vendor relationship at all. The free tier is the whole open-source platform, self-hosted via Docker, with core features and community support. Business tier runs $15/month and adds SSO, priority support, and advanced features on top of the free foundation.
Functionally, Appsmith covers the same ground as Retool: drag-and-drop widgets (tables, charts, forms, maps, rich text editors), database and REST API connections, JavaScript for custom logic anywhere in the platform, Git version control for tracking application changes, and role-based access control. For a team spending weeks building internal dashboards from scratch, Appsmith reduces that to hours, the same pitch as Retool, at a fraction of the cost once you're self-hosting.
The honest tradeoff: complex apps still require real JavaScript knowledge to get right, and there's a genuine learning curve around Appsmith's specific patterns that isn't dramatically shorter than Retool's. What you're trading isn't capability, it's the $50/user/month Retool Business tier for a $0 self-hosted deployment plus whatever server you're already running.
ToolJet: The Workflow and Collaboration Angle
ToolJet is open-source with 37,000+ GitHub stars, connecting to PostgreSQL, MySQL, MongoDB, and APIs including REST, GraphQL, and gRPC. Free tier covers self-hosted core features for up to 5 users. Business runs $20/month and adds enterprise SSO, advanced connectors, and priority support.
The differentiator from Appsmith is workflow automation and multiplayer editing. Built-in workflow automation handles multi-step processes beyond a single app's UI, and real-time multiplayer editing lets a team build the same application simultaneously rather than working in sequence or on separate copies. A marketplace of pre-built templates covers common internal tool patterns, which shortens the time-to-first-app for standard use cases like a support dashboard or an inventory tracker.
For organizations building multiple internal tools across different teams, ToolJet's consistency (one platform, shared templates, real-time collaboration) reduces duplicated effort in a way that matters more as the number of internal tools grows past a handful.
Migration and Lock-In
Switching between these three later is real work, not a config export. Retool's proprietary query and component format doesn't map cleanly to Appsmith or ToolJet's underlying structures, so moving off Retool means rebuilding apps rather than importing them. This is the practical shape of the vendor lock-in concern that shows up in Retool discussions: the apps you build accumulate real engineering time, and that time isn't portable if you decide to leave.
Appsmith and ToolJet, being open-source with more similar underlying architectures, have an easier migration path between each other than either has with Retool, though "easier" still means rebuilding UI and re-testing data connections rather than a clean import. The practical implication: evaluate all three with a real internal tool before committing broadly, not a toy example, since the cost of guessing wrong compounds every app you build afterward.
Where the Real Decision Sits
The three tools are not meaningfully different on core capability: all three connect to the databases and APIs you actually use, all three offer drag-and-drop component builders, all three support custom JavaScript for logic the builder can't express visually. The decision is about three other things.
Cost at your actual team size. Retool's free tier covers 5 users, matching Appsmith's and ToolJet's self-hosted free tiers directly. Past 5 users, Retool Standard is $10/user/month, and Business (the tier with self-hosting) is $50/user/month. A 15-person team needing self-hosted deployment pays $750/month on Retool versus $15-20/month flat on Appsmith or ToolJet Business, regardless of headcount, since those tiers price per instance rather than per user.
Operational capacity. Self-hosting Appsmith or ToolJet means someone owns the Docker deployment, the updates, and the infrastructure it runs on. Retool's hosted tiers hand that off entirely, which is worth real money if your team doesn't have spare DevOps capacity, the same tradeoff pattern that shows up across the self-hosted software landscape covered in the best self-hosted apps roundup.
Polish versus control. Retool's interface and component library are more refined after eight years of dedicated development. Appsmith and ToolJet are closing that gap steadily but haven't fully closed it. If the internal tool is customer support facing internal stakeholders who expect a certain level of polish, that gap is worth noticing before committing.
The Recommendation
For a team without spare infrastructure capacity that wants the most polished builder and is willing to pay for it: Retool, and budget for Business tier from the start if self-hosting or SSO is a real requirement, since Standard doesn't get you there.
For a team with any DevOps capacity at all, especially one already running Docker or Kubernetes for other services: Appsmith. The functional gap versus Retool is smaller than the cost gap, and the free self-hosted tier covers most internal tooling needs completely.
For a team building several internal tools across multiple departments, where workflow automation and real-time collaborative editing matter: ToolJet, for the same self-hosted economics as Appsmith with a stronger story for teams building more than one or two tools.
The same free-versus-paid tradeoff pattern shows up in infrastructure monitoring, covered in the Sentry vs Datadog comparison: pay for a managed platform once, or accept the operational overhead of self-hosting in exchange for the recurring bill disappearing. For internal tooling specifically, that overhead is genuinely low if a team is already running containers, which makes Appsmith or ToolJet the default recommendation for any team with a server to spare.