How to choose an internal tools platform

None of the tools in this category are analytics products. A dashboard built in a BI tool answers questions by reading data; an internal tool built here reads and writes — an approval queue, an admin panel, a CRUD console on top of a database, a support-ops screen with write-back to a CRM. Data and analytics teams end up owning these builders because the fastest way to put a working interface on a warehouse or operational database is usually one of these tools rather than a bespoke web app. If what you actually want is a read-only dashboard for a KPI, you want a BI tool, not this category.

The first fork: open source and self-hostable, or not

This category splits cleanly on licensing, and it matters more here than in most software categories because these apps often carry write access to production data.

• Open source, self-hostable at no cost. Appsmith (Apache-2.0) and Lowdefy (Apache-2.0) are both free to self-host at any scale with no user limits on the community edition. Budibase's core is GPL-3.0 with a free, unlimited self-hosted Open Source edition, though its own paid enterprise features run under a separate Business Source License. ToolJet is AGPL-3.0, with a separate commercial license for reselling it as a service. Windmill's Community Edition is also AGPL-3.0 and free to self-host with unlimited executions.
• Source-available, "fair-code," not OSI-approved open source. n8n can be self-hosted and inspected for free under its Sustainable Use License, but that license restricts reselling it as a competing hosted service, so the Open Source Initiative does not classify it as open source.
• Fully proprietary, no free self-hosted tier. Retool and Superblocks are both closed-source commercial products; Retool has a free cloud tier for small teams, while Superblocks has none.

Open source and self-hostable is not automatically the cheap option — you are trading license fees for the engineering time to run, patch, and secure the deployment. For a two-person ops team, a hosted commercial product with a real support line is often cheaper than "free" software nobody has time to maintain.

Who is actually building the apps

• Engineers who want speed without hand-rolling a web app. Retool and Superblocks both assume the builder is comfortable in JavaScript or Python and wiring direct database/API connections; Superblocks adds Clark, an AI agent that scaffolds and edits apps and workflows and carries memory across builds.
• Teams that want to self-host from day one without a licensing conversation. Appsmith, Budibase, and ToolJet are all designed to run free at scale on your own infrastructure, with paid tiers reserved for SSO, audit logs, and removing vendor branding.
• Developers who would rather write code than drag components. Lowdefy is config-first: apps are defined declaratively in YAML rather than built visually, which the project positions as easier for both humans and AI assistants to review and maintain than generated source code. Windmill goes further, turning Python, TypeScript, Go, Bash, or SQL scripts directly into APIs, scheduled workflows, and auto-generated UIs — it is explicitly pitched as an open-source alternative to Retool and an Airflow-style orchestrator combined.
• Teams automating between systems rather than building a UI at all. n8n is a workflow automation tool, not an app builder — data teams reach for it to trigger a dbt run, post a Slack alert on a data-quality failure, or move records between a CRM and a warehouse on a visual, node-based canvas.

How pricing scales

Nearly every vendor in this category prices on a mix of builder/creator seats, end users, and usage (actions, executions, or AI credits), which makes sizing a real exercise rather than a lookup. Retool and Appsmith separate builder pricing from internal-user pricing; Budibase and ToolJet price primarily per creator/builder seat with action or AI-credit allowances; n8n and Windmill price cloud usage on executions and worker compute rather than seats; Superblocks uses a "Governed Agent Unit" allowance with a per-additional-app fee. None of these figures are reproduced here — check each tool's profile for current tiers, and re-price at the builder and end-user counts you expect once the tool is embedded in daily operations, not the pilot team.

Deployment and compliance

Every tool in this category offers both cloud and self-hosted deployment except n8n, which is cloud or self-hosted as well — the real differentiator is depth of enterprise controls rather than availability. Superblocks supports VPC deployment on AWS, GCP, or Azure and source-control integration with GitHub, GitLab, Bitbucket, or Azure DevOps on its Enterprise tier, and is SOC 2 Type II certified and HIPAA compliant. ToolJet offers an air-gapped self-hosted edition. If regulatory or data-residency requirements are firm, confirm the specific compliance certifications and air-gap options directly — they vary by tier, not just by vendor.

A shortlist by situation

• You want a free, unlimited, self-hostable builder and don't need enterprise SSO on day one: Appsmith or Budibase.
• You want an AGPL open-source builder with active AI-agent development (including MCP integration for Claude Code, Codex, or Cursor): ToolJet.
• You're an engineering team that wants the market-standard commercial tool with the deepest ecosystem: Retool.
• You want an AI agent to scaffold and iterate on the app for you, and enterprise deployment controls matter more than a free tier: Superblocks.
• You'd rather write config or code than drag widgets: Lowdefy (YAML-first) or Windmill (script-first, with orchestration built in).
• The job is moving data between systems and firing alerts, not building a UI: n8n.

Questions to ask before you commit

1. What does the license actually permit — can we self-host indefinitely for free, and does that include the features we need, or only a stripped-down edition?
2. How is pricing metered (seats, actions, executions, AI credits), and what does it cost at our expected end-user count in a year?
3. What role-based access control and audit logging exist, and are they on the free tier or gated to Enterprise?
4. Who owns and patches the self-hosted deployment, and does that person have the bandwidth?
5. Can the app write back to production systems, and what approval or review gate sits in front of that?

Common mistakes

• Choosing based on the demo's drag-and-drop polish and discovering later that write-back permissions and audit logging are Enterprise-only.
• Treating "open source" as "free" without budgeting for the person who runs, secures, and upgrades a self-hosted instance.
• Building dozens of small internal tools with no data governance review of which ones can write to production data.
• Picking a workflow-automation tool like n8n to build a user-facing app, or an app builder to run a scheduled data pipeline — each tool here is opinionated about which of those two jobs it does.

See Appsmith vs Retool and Retool vs Superblocks, or browse every tool in this category.