Technology·14 min read

Retool vs Appsmith vs Custom Build: Internal Tools Compared

Low-code platforms like Retool and Appsmith promise to cut internal tool development from months to days. That promise holds up in some scenarios and falls apart in others. This guide breaks down real pricing, feature limitations, and the concrete scenarios where a custom build actually saves money over time.

N

Nate Laquis

Founder & CEO ·

Why the Internal Tools Decision Matters More Than You Think

Internal tools are the unsexy backbone of every growing company. Admin panels, customer support dashboards, data reporting interfaces, approval workflows. Nobody puts them on the marketing site, but teams rely on them every single day. When these tools are slow, clunky, or missing features, the cost shows up in wasted employee hours, not in a line item anyone tracks.

Analytics dashboard displaying business metrics and data visualizations

The market for building these tools has exploded. Retool, Appsmith, Tooljet, Budibase, and a dozen other platforms all promise to let you ship internal tools in hours instead of weeks. On the other side, open-source frameworks like React Admin, Refine, and Tremor have gotten good enough that custom building is faster than it used to be.

The problem is that most teams make this decision based on a 15-minute demo or a blog post from the vendor. They don't think about what happens at 50 users, or when the security team asks for SOC 2 audit logs, or when a critical integration doesn't exist in the connector library. This guide is designed to help you avoid those surprises.

We have helped companies build internal tools using all of these approaches. Some started on Retool and migrated to custom. Some started custom and wished they had used a platform. The right answer depends on your team size, your data security requirements, your budget, and how much you need to customize. Let's break it all down.

Retool: The Market Leader and Its Trade-offs

Retool is the 800-pound gorilla in the low-code internal tools space. Founded in 2017, it has raised over $440 million and is used by companies like Amazon, DoorDash, and NBC. It works well for what it does: connecting to databases and APIs, dragging components onto a canvas, and writing small snippets of JavaScript to glue it all together.

Pricing. Retool's pricing starts at $10/month per user on the Free tier (up to 5 users), jumps to $50/month per user on the Business plan, and goes to custom pricing for Enterprise. The Business plan is where most real companies land because it includes features like audit logs, custom branding, and granular permissions. At $50/user/month, a team of 25 is paying $15,000/year. A team of 100 is paying $60,000/year. That number only goes up.

What it does well. Retool has 100+ pre-built data source connectors (PostgreSQL, MySQL, MongoDB, Snowflake, REST APIs, GraphQL, Google Sheets, and more). The drag-and-drop builder is genuinely fast for standard CRUD interfaces. If you need a table that reads from a database, lets users edit rows, and triggers a webhook on save, you can build that in an afternoon. The component library is mature, with tables, forms, charts, modals, and wizards all available out of the box.

Where it struggles. Vendor lock-in is the big one. Everything you build lives inside Retool's proprietary format. If you decide to leave, you are rebuilding from scratch. There is no export-to-code option. Custom components exist but are sandboxed in iframes, which limits styling and performance. Complex business logic gets awkward quickly because you are writing JavaScript snippets scattered across dozens of event handlers rather than in a structured codebase. Version control exists but is nowhere near as clean as Git-based workflows.

Security considerations. Retool offers cloud-hosted and self-hosted (on-premise) deployments. The self-hosted option is Enterprise-only, which means custom pricing, typically starting around $500/month or more. For companies handling healthcare data, financial records, or other regulated information, this is a critical factor. The cloud version means your queries and data pass through Retool's infrastructure, even with their SOC 2 Type II certification.

Appsmith: The Open-Source Challenger

Appsmith positions itself as the open-source alternative to Retool, and that distinction matters more than it might seem at first glance. The entire codebase is on GitHub under an Apache 2.0 license. You can self-host it on your own infrastructure at zero cost, and many companies do exactly that.

Pricing. The Community Edition is free, forever, with no user limits. That alone makes it attractive for startups and cost-conscious teams. The Business Edition runs $40/user/month and adds features like SAML SSO, audit logs, custom branding, and priority support. The Enterprise tier is custom-priced and includes dedicated support, SLA guarantees, and advanced security features.

What it does well. Self-hosting is the headline feature. You can run Appsmith on a $20/month VM and give access to your entire team without per-seat costs. For a 50-person operations team, that is the difference between $0/month and $24,000/year on Retool Business. The UI builder is solid, the connector library covers most common databases and APIs, and the JavaScript-based query system is flexible enough for most use cases. Appsmith also supports Git-based version control natively, which is a genuine advantage over Retool for teams that care about code review workflows.

Where it struggles. The component library is smaller and less polished than Retool's. Some components lack advanced configuration options that Retool handles natively. Performance can be inconsistent on complex pages with many queries. The self-hosted experience requires you to manage your own infrastructure, including updates, backups, and scaling. If your team does not have someone comfortable with Docker and basic DevOps, this becomes a real burden. Community support is active but slower than Retool's paid support channels.

Security considerations. Self-hosting gives you complete control over where data lives and how it flows. No third-party infrastructure touches your queries. For regulated industries, this is often the deciding factor. The Business Edition adds audit logs and SAML/OIDC SSO, which are table stakes for enterprise security compliance.

Tooljet, Budibase, and Other Contenders Worth Knowing

Retool and Appsmith get the most attention, but they are not the only options. Two other platforms deserve a serious look depending on your needs.

Tooljet is another open-source low-code platform with a very similar feature set to Appsmith. It supports 50+ data sources, has a drag-and-drop builder, and can be self-hosted for free. The paid plans start at $19/user/month, making it the cheapest commercial option in this space. Tooljet's UI is clean and improving quickly, though it still trails Retool in component depth and Appsmith in community size. If budget is your primary constraint and you want a managed cloud option, Tooljet is worth evaluating.

Budibase takes a slightly different approach by focusing on data modeling built into the platform. You can create a database directly inside Budibase rather than only connecting to external sources. This makes it useful for teams that need a quick internal app but do not have an existing database schema to connect to. Pricing starts at $5/user/month for the Premium plan. The trade-off is that Budibase's query capabilities for external databases are less flexible than Retool or Appsmith.

Both Tooljet and Budibase are viable for simpler use cases. If you need a basic admin panel or a data entry form connected to a PostgreSQL database, either will get the job done at a lower price point. For complex workflows, heavy customization, or large-scale deployments, Retool and Appsmith remain stronger choices.

Developer writing code on a laptop with a modern IDE open

The Custom Build Option: React Admin, Refine, and Tremor

On the other end of the spectrum, you can skip platforms entirely and build your internal tools with code. This used to mean months of work. Today, frameworks purpose-built for admin interfaces make it significantly faster.

React Admin is the most established option. It is an open-source framework that gives you a complete admin panel architecture: data providers, authentication, CRUD views, filters, pagination, and a library of pre-built components. You connect it to any API (REST, GraphQL, or custom) and get a functional admin panel in days rather than weeks. The learning curve is moderate. You need to be comfortable with React, and the documentation is good but dense.

Refine is the newer alternative that has gained traction fast. It is framework-agnostic (supporting React, Next.js, and Remix), comes with data providers for popular backends like Supabase, Strapi, and Hasura, and has a cleaner developer experience than React Admin. Refine also includes an optional UI layer using Ant Design or Material UI, so you do not start from a blank screen. For teams already using Next.js, Refine integrates more naturally than React Admin.

Tremor is specifically focused on dashboards and data visualization. If your internal tool is primarily about displaying metrics, charts, and KPIs rather than CRUD operations, Tremor gives you beautiful, responsive dashboard components built on React and Tailwind CSS. It is not a full admin framework, but for analytics-heavy interfaces, it is faster than building chart layouts from scratch.

Cost structure. The frameworks themselves are free. Your costs are developer time and hosting. A mid-level React developer can build a solid internal admin panel in 3 to 6 weeks using React Admin or Refine. At a blended rate of $150/hour, that is $18,000 to $36,000 in development cost, plus maybe $50 to $200/month for hosting on a service like Vercel, Railway, or a small AWS setup. There is also ongoing maintenance: plan for 5 to 10 hours per month for bug fixes, updates, and small feature additions.

The real advantage. You own everything. The code lives in your Git repository. You can customize any component, implement any business logic, and integrate with any system. There are no per-seat fees that scale linearly with your team. When you need to add a complex workflow that would require ugly workarounds on a low-code platform, you just write the code. For a deeper look at the full cost picture, check out our guide on web app costs.

Pricing Comparison at Scale: 10, 25, 50, and 100 Users

Pricing is where these decisions get real. A platform that looks cheap at 5 users can become shockingly expensive at 50. Here is what you are actually looking at across the major options.

Annual cost at 10 users

  • Retool Business: $6,000/year ($50/user/month)
  • Appsmith Business: $4,800/year ($40/user/month)
  • Appsmith Community (self-hosted): $0 software + ~$240/year hosting
  • Tooljet Cloud: $2,280/year ($19/user/month)
  • Budibase Premium: $600/year ($5/user/month)
  • Custom build (React Admin/Refine): $18,000 to $36,000 upfront + ~$1,800/year hosting and maintenance

Annual cost at 25 users

  • Retool Business: $15,000/year
  • Appsmith Business: $12,000/year
  • Appsmith Community (self-hosted): $0 software + ~$600/year hosting
  • Tooljet Cloud: $5,700/year
  • Budibase Premium: $1,500/year
  • Custom build: $18,000 to $36,000 upfront + ~$2,400/year hosting and maintenance

Annual cost at 50 users

  • Retool Business: $30,000/year
  • Appsmith Business: $24,000/year
  • Appsmith Community (self-hosted): $0 software + ~$1,200/year hosting
  • Tooljet Cloud: $11,400/year
  • Budibase Premium: $3,000/year
  • Custom build: $18,000 to $36,000 upfront + ~$3,600/year hosting and maintenance

Annual cost at 100 users

  • Retool Business: $60,000/year
  • Appsmith Business: $48,000/year
  • Appsmith Community (self-hosted): $0 software + ~$2,400/year hosting
  • Tooljet Cloud: $22,800/year
  • Budibase Premium: $6,000/year
  • Custom build: $18,000 to $36,000 upfront + ~$6,000/year hosting and maintenance

The math is clear: per-seat pricing punishes you as you grow. At 100 users, Retool costs $60,000 every single year. A custom build that cost $30,000 to create pays for itself in under 7 months compared to Retool, and the gap only widens from there. But this math only works if your custom tool actually gets built and maintained properly. A failed custom project that needs to be rebuilt costs far more than two years of Retool. For a broader look at when building makes sense versus buying, read our build vs buy analysis.

Feature Comparison: RBAC, Audit Logs, SSO, and Custom Components

Price is only half the picture. The features your team needs, especially around security and compliance, vary dramatically across these options.

Role-Based Access Control (RBAC)

Retool includes granular RBAC on the Business plan: you can control access at the app, page, and even component level. Appsmith Business offers app-level and workspace-level permissions but is less granular at the component level. Tooljet and Budibase both offer basic role-based permissions, though neither matches Retool's depth. With a custom build, you implement exactly the permission model you need, whether that is simple role-based or complex attribute-based access control (ABAC). The trade-off is that you have to build and test it yourself.

Audit Logs

Audit logs are a compliance requirement for many companies, especially in healthcare, finance, and any organization pursuing SOC 2 certification. Retool includes audit logs on the Business plan ($50/user/month). Appsmith includes them on the Business plan ($40/user/month). Tooljet and Budibase include basic logging on their paid tiers. With a custom build, you can implement audit logging exactly how your compliance team needs it, including custom retention policies and integration with your existing SIEM tools. This is one area where custom builds often outperform platforms because compliance requirements are rarely "standard."

Single Sign-On (SSO)

SAML and OIDC SSO is a Business or Enterprise feature on every platform. Retool charges $50/user/month to get SSO. Appsmith charges $40/user/month. This is a common pattern in SaaS pricing: security features that should be baseline are gated behind higher tiers. With a custom build, you integrate with your identity provider (Okta, Auth0, Azure AD) once, and every user gets SSO at no incremental cost.

Custom Components

Every platform hits a wall when you need a component that does not exist in their library. Retool allows custom components but renders them in sandboxed iframes, which limits their ability to interact with the parent app. Appsmith supports custom widgets with similar limitations. With a custom build, there are no restrictions. You use any React component, any charting library, any design system. For teams building tools that need specialized visualizations, complex form workflows, or domain-specific UI elements, this flexibility is the single biggest advantage of going custom.

Data Security and Migration Risks

Data security is where the conversation gets serious, and where many teams regret not thinking carefully enough upfront.

Team planning session at a desk with documents and laptops

Cloud-hosted platforms like Retool Cloud mean your database credentials and query results pass through a third party's infrastructure. Retool encrypts data in transit and at rest, and they hold SOC 2 Type II certification. But for companies in regulated industries, "our data touches a third-party service" is a conversation with the legal team, not just the engineering team. Even with contractual safeguards, the attack surface is larger than a self-hosted solution.

Self-hosted options (Retool Enterprise, Appsmith Community/Business, Tooljet, Budibase) keep everything on your infrastructure. This is the right answer for companies handling PHI, PCI data, or classified information. The trade-off is operational overhead: you are responsible for patching, scaling, backups, and uptime.

Custom builds give you the most control. You decide where data lives, how it flows, what gets logged, and what gets encrypted. You can meet any compliance framework because you control every layer. The risk is that you need developers who understand security best practices. A custom tool with SQL injection vulnerabilities is worse than a platform that handles parameterized queries automatically.

Migration risk is the sleeper issue. If you build on Retool and later need to move (because of pricing, a security policy change, or an acquisition), you are starting over. There is no "export to React" button. Every query, every component, every workflow must be rebuilt. We have seen companies spend 3 to 6 months migrating off low-code platforms, and the cost often exceeds what the original custom build would have been. Appsmith's open-source codebase gives you slightly more flexibility here, since you can at least inspect and reference the app definitions, but it is still not a clean migration path. For a deeper comparison of no-code and custom costs, see our breakdown of no-code vs custom cost.

When Each Option Makes Sense

After working on dozens of internal tool projects, here is the honest breakdown of when each approach is the right call.

Choose Retool when:

  • You need to ship a functional internal tool this week, not this quarter.
  • Your team is under 25 users and the $15,000/year cost is acceptable.
  • You are connecting to standard databases and APIs with straightforward CRUD operations.
  • You have budget for the Business plan and need features like audit logs and granular RBAC out of the box.
  • You do not have React developers on staff and cannot hire or contract one quickly.

Choose Appsmith when:

  • Self-hosting is a requirement for security, compliance, or cost reasons.
  • Your user count is high (50+) and per-seat pricing would be painful.
  • You want Git-based version control for your internal tools.
  • You are comfortable running Docker containers and managing a small piece of infrastructure.
  • You want the option to inspect and modify the platform's source code if needed.

Choose Tooljet or Budibase when:

  • Your needs are relatively simple: admin panels, data entry forms, basic reporting.
  • Budget is the primary constraint and you want a managed cloud option under $20/user/month.
  • You are building a prototype or proof-of-concept that may evolve later.

Choose a custom build when:

  • Your user count is 50+ and you plan to keep growing. The economics favor custom at scale.
  • You need complex business logic, custom workflows, or specialized UI components that platforms cannot support without ugly workarounds.
  • Data security requirements demand full control over where data lives and how it moves.
  • You have React developers on your team (or can hire them) and want to own the codebase long-term.
  • You are building a tool that is core to your operations and will evolve significantly over the next 2 to 5 years.

The worst choice is no choice at all. Many teams end up with a patchwork of spreadsheets, Retool apps, and hastily written scripts because nobody made a deliberate decision about how to build internal tooling. Pick an approach, commit to it, and invest properly.

If you are not sure which path fits your situation, we can help you figure it out. We have built internal tools on platforms and from scratch, and we will give you an honest recommendation based on your team size, budget, and requirements. Book a free strategy call and we will walk through your options together.

Need help building this?

Our team has launched 50+ products for startups and ambitious brands. Let's talk about your project.

Retool vs Appsmithinternal toolslow-code platformscustom internal toolsenterprise software comparison

Ready to build your product?

Book a free 15-minute strategy call. No pitch, just clarity on your next steps.

Get Started