---
title: "Retool vs Windmill vs Tooljet: Internal Tools for Startups 2026"
author: "Nate Laquis"
author_role: "Founder & CEO"
date: "2026-05-03"
category: "Technology"
tags:
  - Retool vs Windmill
  - Tooljet comparison
  - internal tools platform
  - low-code internal tools
  - admin dashboard builder
excerpt: "Picking the right internal tools platform can save your startup thousands of hours. Here is an honest breakdown of Retool, Windmill, and Tooljet so you can stop researching and start building."
reading_time: "14 min read"
canonical_url: "https://kanopylabs.com/blog/retool-vs-windmill-vs-tooljet-internal-tools"
---

# Retool vs Windmill vs Tooljet: Internal Tools for Startups 2026

## Why Internal Tools Platforms Matter More Than Ever

Your engineering team did not join your startup to build CRUD admin panels. They joined to work on the product. Yet every growing company hits a point where someone needs a customer lookup tool, an order management dashboard, a refund processing screen, or a permissions editor. These internal tools are unglamorous but essential, and they multiply fast. By the time you have 20 employees, you probably need 5 to 10 of them.

Building each one from scratch with React and a backend framework takes 2 to 6 weeks of engineering time. That is time pulled directly from your product roadmap. Internal tools platforms like Retool, Windmill, and Tooljet exist to compress that timeline to hours or days. They give you drag-and-drop builders, pre-built database connectors, and components for tables, forms, charts, and modals so your team can assemble functional tools without writing an entire frontend from scratch.

The catch is that these platforms differ dramatically in philosophy, pricing, hosting options, and developer experience. Retool is the well-funded market leader. Windmill is an open-source challenger built for engineers who want code-first workflows. Tooljet is another open-source option that positions itself as the accessible, community-driven alternative. Choosing the wrong one can mean vendor lock-in, unexpected costs, or hitting capability walls right when you need the platform most.

This guide breaks down the real differences across the areas that matter: builder experience, database and API connectivity, self-hosting, pricing, AI capabilities, permissions, and extensibility. I will also cover when you should skip all three and build a custom solution instead.

![Startup office team collaborating on internal tools and software development](https://images.unsplash.com/photo-1504384308090-c894fdcc538d?w=800&q=80)

## Drag-and-Drop Builder Experience Compared

The builder is where your team will spend most of their time, so the editing experience matters more than any other single factor. All three platforms use a visual canvas where you place components (tables, buttons, text inputs, dropdowns) and wire them to data sources using queries. But the feel is very different across the three.

### Retool

**Retool's builder** is the most polished of the three. Components snap into a grid layout, the property inspector is well-organized, and the query editor supports SQL, REST, GraphQL, and JavaScript transformers in a unified interface. You can reference query results and component states using double-brace syntax like **{{query1.data}}**, and autocomplete makes this fast. Retool also offers a mobile layout mode so you can build responsive tools without duplicating work. The learning curve is moderate: a developer comfortable with SQL and JavaScript can build a functional tool in an afternoon.

Where Retool's builder falls short is flexibility. The grid system can feel rigid when you want pixel-perfect layouts. Custom CSS is limited to component-level overrides rather than full stylesheet access. And for complex multi-step workflows (like "fetch data, transform it, call an external API, then update the UI"), you end up chaining JavaScript queries together in a way that becomes hard to debug.

### Windmill

**Windmill** takes a fundamentally different approach. Its app builder exists, but the real power is in its script and flow editor. Windmill treats everything as a script (Python, TypeScript, Go, Bash, SQL, or even Rust) that runs on a managed execution engine. You build flows by chaining scripts together, each step receiving the output of the previous one. The UI builder then connects to these flows. This is more work upfront but significantly more powerful for data-heavy or logic-heavy tools.

Windmill's UI builder is less mature than Retool's. The component library is smaller, the layout system feels rougher, and there are fewer pre-built templates. If your goal is a quick admin panel with a table, a search bar, and a few action buttons, Windmill will feel over-engineered. But if your internal tool involves complex ETL steps, conditional branching, scheduled jobs, or calling multiple APIs in sequence, Windmill's flow engine is genuinely superior.

### Tooljet

**Tooljet's builder** sits between the two. The drag-and-drop canvas is straightforward, and the component library covers the basics well: tables, forms, charts, maps, modals, tabs, and a calendar widget. The query panel supports REST APIs, databases, and JavaScript, similar to Retool. The overall experience feels like a lighter-weight Retool, which is both its strength and its limitation.

Tooljet's builder struggles with complex layouts. Nesting components inside containers can get finicky, and the event-handling system for triggering actions across components requires more manual wiring than Retool. That said, for straightforward data management tools (view, edit, create, delete records), Tooljet gets you there quickly and the learning curve is gentle.

## Database Connectors and API Integration

An internal tools platform is only as useful as the data sources it can connect to. Your company likely runs a mix of PostgreSQL or MySQL for your product database, a handful of SaaS APIs (Stripe, Twilio, Salesforce, HubSpot), maybe a data warehouse like Snowflake or BigQuery, and a few internal REST or GraphQL endpoints.

### Retool's Integrations

Retool has the widest native integration library of the three, with over 60 pre-built connectors. This includes direct database connections (PostgreSQL, MySQL, MongoDB, DynamoDB, Snowflake, BigQuery, Redshift, Elasticsearch), SaaS APIs (Stripe, Twilio, Slack, GitHub, Salesforce, Google Sheets), and generic REST/GraphQL/gRPC support. Retool also supports connecting to APIs behind firewalls using their on-premise agent, which sets up a secure tunnel without exposing your database to the internet. For most startups, Retool's integration library covers everything out of the box.

### Windmill's Integrations

Windmill approaches integrations differently. Instead of building native connectors for every service, Windmill leans on its script execution environment. Because you can write Python or TypeScript scripts that run on the platform, you can use any library available in those ecosystems. Need to connect to an obscure ERP system? Install the Python client library and write a script. This is more work than clicking a pre-built connector, but it means you are never blocked by missing integrations. Windmill also has a growing **Hub** of community-contributed scripts for common integrations (PostgreSQL, Slack, OpenAI, Google Sheets, S3), which function like pre-built connectors.

For database connections specifically, Windmill supports PostgreSQL, MySQL, MS SQL, and BigQuery natively. Everything else goes through scripts. This is fine for engineering-heavy teams but a friction point if your ops or analytics people need to add new data sources without writing code.

### Tooljet's Integrations

Tooljet offers around 45 pre-built connectors, including the major databases (PostgreSQL, MySQL, MongoDB, ClickHouse, Elasticsearch, Redis, DynamoDB) and common SaaS tools (Stripe, Slack, Google Sheets, Airtable, Twilio, SendGrid). It also supports REST and GraphQL APIs. The connector list is smaller than Retool's but covers the 80% case for most startups. One notable gap: Tooljet's connectors sometimes lag on feature parity. For example, the Stripe connector may support charges and customers but not newer APIs like payment links or billing meters. When you hit these gaps, you fall back to the generic REST connector, which works but means more manual configuration.

If your startup relies heavily on a specific SaaS platform, check the connector documentation for all three before committing. A pre-built connector with full CRUD support saves hours compared to manually configuring REST endpoints with authentication headers, pagination, and error handling.

![Analytics dashboard showing database connection metrics and API integration performance](https://images.unsplash.com/photo-1551288049-bebda4e38f71?w=800&q=80)

## Self-Hosting and Open Source: Windmill and Tooljet vs Retool Cloud

This is where the three platforms diverge most sharply, and for many startups, it is the deciding factor.

### Retool: Cloud-First with Limited Self-Hosting

Retool started as a cloud product and has added self-hosting options, but they come with caveats. Retool's self-hosted edition requires an Enterprise license, which starts around $50 per user per month (with annual contracts and minimum seat counts). You get Docker and Kubernetes deployment options and can run Retool on your own AWS, GCP, or Azure infrastructure. This matters for companies with strict data residency requirements or compliance needs (SOC 2, HIPAA, ISO 27001). However, self-hosting Retool is not free, and the self-hosted version has occasionally lagged behind the cloud version on feature releases.

For most early-stage startups, Retool's cloud version is the practical choice. But be aware that Retool's cloud stores your queries, component configurations, and metadata on their servers. Your actual database data passes through Retool's proxy layer unless you configure a direct database connection. For companies handling sensitive financial or healthcare data, this can be a compliance concern.

### Windmill: Fully Open Source, Self-Host Everything

**Windmill is AGPLv3 licensed and fully open source.** You can self-host the entire platform on your infrastructure at no licensing cost. The deployment is Docker-based and straightforward: a single docker-compose file gets you running with PostgreSQL as the metadata store. Windmill also offers a cloud-hosted version starting at $10 per user per month if you do not want to manage infrastructure.

The open-source angle is genuine. Windmill's core features, including the flow engine, the app builder, the script editor, and all integrations, are available in the self-hosted community edition. The paid tiers (Pro and Enterprise) add features like audit logs, SAML SSO, priority support, and SLAs, but nothing that blocks you from building production internal tools on the free tier. For startups with a DevOps-capable team that wants to own their infrastructure, Windmill is the strongest option.

### Tooljet: Open Source with a Generous Community Edition

**Tooljet is also open source**, licensed under AGPLv3 (with some components under a proprietary license). The self-hosted community edition includes the builder, all connectors, basic SSO, and multi-environment support. You can deploy via Docker, Kubernetes, or one-click options on AWS EC2, DigitalOcean, and Heroku. The deployment experience is smoother than Windmill's for teams that are less comfortable with infrastructure, thanks to good documentation and community guides.

Tooljet's paid cloud tiers add features like audit logging, granular permissions, custom branding, and priority support. The Business tier starts at $20 per user per month. Compared to Windmill, Tooljet gates more features behind the paid tier (notably granular RBAC and audit logs), so evaluate carefully whether the community edition meets your compliance needs.

If self-hosting is a hard requirement and your team is engineering-heavy, Windmill gives you the most power. If self-hosting is a soft preference and you want a gentler setup process, Tooljet is the easier path. If you do not care about self-hosting and want the most polished product, Retool cloud is hard to beat.

## Pricing Breakdown: What You Will Actually Pay

Pricing is where internal tools platforms get tricky. The published per-user rates are just the starting point. You also need to account for execution limits, connector costs, and the inevitable price increases as you grow.

### Retool Pricing (2026)

Retool's free tier allows up to 5 users with limited features, which is enough for prototyping but not production use. The **Team plan** runs $10 per standard user per month and $5 per end user per month (end users can view and interact with tools but not build them). The **Business plan** is $50 per standard user per month with RBAC, audit logs, and staging/production environments. **Enterprise** pricing is custom and typically lands between $50 and $80 per user per month with annual contracts.

The hidden cost with Retool is user count growth. Internal tools tend to spread across an organization once they exist. What starts as 3 builders and 10 end users quickly becomes 8 builders and 40 end users, pushing your monthly bill from $175 to $280 on the Team plan, or from $650 to $2,200 on the Business plan. Budget for 2x to 3x your initial user estimate within the first year.

### Windmill Pricing (2026)

Windmill's self-hosted community edition is free with unlimited users. The **Pro plan** (cloud or self-hosted) is $10 per user per month and adds premium support, audit logs, and dedicated workers. **Enterprise** starts at $40 per user per month with SAML SSO, SLAs, and priority support. Windmill also charges based on executions: the free tier includes 1,000 executions per month, and additional executions cost $0.001 each. For most internal tools, this is negligible, but if you are running high-frequency scheduled jobs or processing thousands of webhook events, monitor your execution count.

The real cost advantage of Windmill is the self-hosted free tier. A startup with 25 users running Windmill on a $50/month server pays $50 total, compared to $250 to $1,250 per month on Retool's Team or Business plans. That is $2,400 to $14,400 per year in savings, which matters at the pre-Series A stage.

### Tooljet Pricing (2026)

Tooljet's self-hosted community edition is free with unlimited users. The **Business plan** (cloud) starts at $20 per user per month with SSO, audit logs, and granular permissions. **Enterprise** is custom-priced. For cloud usage, Tooljet sits between Windmill and Retool on cost.

The cost calculation for your startup depends on three factors: (1) how many builders vs. end users you have, (2) whether you can self-host, and (3) what governance features you need. If you have a small team, can self-host, and do not need enterprise compliance features, Windmill or Tooljet's free tiers save you real money. If you have a larger team with mixed technical skills and need production-grade RBAC and audit trails, Retool's Business plan is expensive but complete.

## AI Features, Version Control, Permissions, and Custom Components

Beyond the basics of building and connecting data, several secondary features separate these platforms. Here is how they stack up on the capabilities that become important as your internal tools mature.

### AI Features

Retool has invested heavily in AI. **Retool AI** lets you embed LLM-powered features directly into your tools: natural-language search over your database, AI-generated summaries in table views, and a "Generate App" feature that creates a starting tool from a text description. Retool also has a vector database integration for RAG-based features. These are production-ready and well-documented. If you are exploring [AI-powered internal tools](/blog/ai-powered-internal-tools-automation), Retool gives you the shortest path to shipping.

Windmill's AI story is different. Because Windmill scripts can import any Python or TypeScript library, you can call OpenAI, Anthropic, or any other AI API directly from your flows. Windmill also has a built-in AI assistant that helps generate scripts from natural language. The flexibility is greater than Retool's, but the out-of-the-box AI components are fewer. You are building with AI libraries rather than using pre-built AI widgets.

Tooljet has basic AI integrations: an OpenAI connector and the ability to call AI APIs via REST. There is no built-in AI assistant for generating tools or natural-language querying. If AI features are a priority, Tooljet is the weakest of the three today.

### Version Control and Git Sync

Retool supports Git Sync on the Business plan and above, allowing you to connect a GitHub or GitLab repository and track changes to your tools as code. This enables branching, pull requests, and code review for internal tool changes. It works, though the generated code is JSON-based and not particularly readable in diff views.

Windmill stores everything as code natively (scripts in their original language, flows as YAML). Git integration is a first-class feature, and you can develop entirely in your local IDE, push to a repo, and sync to the Windmill deployment. For engineering teams that live in Git, this is a major advantage.

Tooljet added Git Sync in late 2025, supporting GitHub repositories for version tracking. The feature is functional but less mature than Retool's or Windmill's. Multi-environment deployments (staging to production) via Git are supported on paid plans.

### Permissions and RBAC

All three platforms offer role-based access control, but the granularity differs. Retool's Business and Enterprise plans provide granular permissions: you can control who can view, edit, or use specific tools, query specific data sources, and access specific environments. Windmill offers folder-based permissions and user groups on all tiers, with more granular controls on Pro and Enterprise. Tooljet's community edition has basic role-based access (admin, builder, viewer), with granular object-level permissions reserved for Business and Enterprise tiers.

For a startup with 5 to 15 users, basic RBAC is usually sufficient. Once you grow past 30 users or start handling customer data in your internal tools, granular permissions become essential. Factor this into your platform choice: if you are on Tooljet's free tier and suddenly need fine-grained permissions, you will face an upgrade cost.

### Custom Components

When the built-in component library does not have what you need (and eventually it will not), you need the ability to build custom components. Retool supports custom React components that you can bundle and upload, giving you full control over rendering and interactivity. The development experience is decent, with a local development mode and hot reloading. Windmill lets you write custom frontend components in Svelte (its native framework) or React. Tooljet also supports custom React components, though the documentation and developer tooling are thinner than Retool's. If you are building a [B2B customer portal](/blog/how-to-build-a-b2b-customer-portal) that doubles as an internal admin interface, custom components will matter sooner than you think.

![Kanban board view of project management tool with task cards and workflow automation](https://images.unsplash.com/photo-1512758017271-d7b84c2113f1?w=800&q=80)

## When to Skip All Three and Build Custom

Not every internal tool belongs on a low-code platform. There are specific scenarios where building a custom solution with React, Next.js, or a similar framework is the better investment, even though it takes longer upfront.

**Build custom when your tool is customer-facing or semi-external.** If partners, vendors, or customers will interact with your internal tool, the branding limitations, URL structures, and UX constraints of Retool, Windmill, or Tooljet will frustrate you. A customer-facing order tracking portal or a vendor management dashboard needs to feel like part of your product, not like a generic admin panel. Custom development gives you full control over the experience.

**Build custom when performance is critical.** Low-code platforms add overhead. Queries pass through an intermediary layer, UI rendering depends on the platform's component engine, and real-time updates are limited. If you are building an internal tool that needs to display thousands of rows with sub-second filtering, handle real-time data streams, or support complex drag-and-drop interactions, a custom build will outperform any of these platforms.

**Build custom when your tool is your competitive advantage.** Some startups discover that their internal tool is actually the product, or could become one. If your operations tool embodies unique business logic that differentiates you from competitors, building it on a third-party platform creates a dependency you do not want. Own the code.

**Build custom when you need deep AI integration.** While Retool and Windmill support AI features, truly custom AI workflows (multi-agent orchestration, fine-tuned models, complex RAG pipelines with domain-specific retrievers) are easier to build and maintain in a proper codebase. If you are planning to build an [AI copilot](/blog/how-to-build-an-ai-copilot) into your internal tool, a custom build gives you the flexibility to iterate on the AI layer without fighting platform constraints.

For everything else, one of the three platforms will save you time. The key is matching the platform to your team's skills and your tool's complexity. Use Retool if your team values polish and speed and your budget supports per-user pricing. Use Windmill if your team is engineering-heavy, you want self-hosting, and your tools involve complex backend logic. Use Tooljet if you want a simpler open-source option with a gentler learning curve and your tools are primarily data management interfaces.

## Our Recommendation and Next Steps

After building internal tools for dozens of startups using all three platforms (and custom code), here is my honest take.

**For most startups with 5 to 30 employees and a mix of technical and non-technical staff**, Retool is still the default choice. The builder is the most intuitive, the integration library is the largest, the AI features are the most mature, and the documentation is excellent. Yes, the pricing adds up. But the time savings over building custom tools is substantial, and you can always migrate off later if costs become unacceptable.

**For engineering-led teams that value self-hosting, code-first workflows, and cost control**, Windmill is the most exciting platform in this space. The flow engine is powerful, the open-source model is genuine, and the community is growing fast. If your team is comfortable writing Python or TypeScript scripts and managing a Docker deployment, Windmill gives you more capability per dollar than either competitor. The trade-off is a rougher builder experience and a smaller ecosystem of templates and resources.

**For teams that want open-source simplicity without Windmill's complexity**, Tooljet is a solid middle ground. It is the easiest to self-host, the builder is approachable, and the community edition is generous enough for many use cases. The gaps are in AI features, git integration maturity, and connector depth, but these are improving with each release.

If you are unsure which direction to go, or if your needs sit at the intersection of a low-code platform and custom development, we can help you figure it out. We have built internal tools on all three platforms and migrated teams between them when needs changed. [Book a free strategy call](/get-started) and we will map out the right approach for your specific situation, team, and budget.

---

*Originally published on [Kanopy Labs](https://kanopylabs.com/blog/retool-vs-windmill-vs-tooljet-internal-tools)*