Retool alternatives for teams that mostly run scripts Appsmith, Budibase, Windmill, Rundeck and Button compared

If your team mostly needs to put a web form in front of existing scripts, Windmill and Rundeck are built for server-hosted script execution, Appsmith and Budibase cover database apps, and Button runs scripts directly on your own computer. With Button, the Free plan is $0 for 1 published tool and 3 invited colleagues, while Pro is $15/month (or $144/year) for up to 50 tools, 250 people and 5,000 runs per month. Which one makes sense depends on whether you want to host workers and servers or just share a script from the machine where it already works.

Why teams look past Retool for scripts

Retool is built for internal apps, workflows and agents on top of your databases and APIs. If that's what you're building, Retool is often the better choice and you probably shouldn't switch.

The friction starts when your team mostly has Python, Bash or PowerShell scripts that non-technical colleagues need to run. In Retool, code in apps and workflows runs on the Retool deployment - either Retool Cloud or your self-hosted instance, which is part of Enterprise plans - and not on an individual user's laptop. You can use Retool RPC to call functions, though you still have to run those on your own backend server. Then there's the pricing: Retool's Free plan covers up to 5 users on Retool Cloud, and paid plans (Team, Business) are billed per builder plus per internal user, which adds up when lots of people only need to run a script once in a while.

How the alternatives compare

All facts and prices below were checked in October 2026.

Appsmith and Budibase

If you still want a full app builder like Retool for CRUD apps and dashboards on databases and APIs, Appsmith and Budibase are the direct open-source comparisons.

Appsmith is Apache 2.0 licensed, and its self-hosted Community Edition is free. On Appsmith Cloud, the Free plan covers up to 5 users, Business is $15 per user per month for up to 99 users, and Enterprise starts at $2,500 per month for 100 users. Queries run from the Appsmith server, and there's no built-in way to run a script on a particular user's computer.

Budibase has a GPLv3 core. Self-hosting it is free and gives you unlimited creators and end users. If you use Budibase Cloud, Pro costs $19/month billed annually ($23 monthly) for 1 creator, with end users at $5 per user per month billed annually, while Premium is $49/month and Business is $299/month (annual). Like Appsmith, Budibase automations run on the Budibase backend, so it has no built-in way to run a script on an end user's computer. Pick Appsmith or Budibase when you're actually building database interfaces and want open-source self-hosting or different cloud pricing than Retool.

Windmill

For teams that want an open-source developer platform (AGPLv3 core) built specifically around scripts, Windmill is usually the strongest fit. It takes scripts in Python, TypeScript, Go, Bash, SQL and 20+ other languages and turns them into auto-generated forms, webhooks, schedules, workflows and apps.

When you self-host, scripts run on Windmill workers you host, on any machine that can reach Windmill's database. If you need schedules, multi-step workflows, webhooks or a central worker pool, Windmill is a better choice than Button. Self-hosted Windmill is free with unlimited executions, up to 50 users (with a max of 10 with SSO) and 3 workspaces. Windmill Cloud also has a free tier with 1,000 executions per month.

Rundeck

Rundeck Open Source is maintained by PagerDuty, with PagerDuty Runbook Automation as the commercial edition. It's the right choice when your scripts are really ops runbooks that need to execute across fleets of remote machines, because Rundeck jobs run commands on nodes over SSH or WinRM, or locally on the Rundeck server.

When you set up a job, its options appear to users as a form with text, file and multi-line options, allowed values and regex checks. You do have to run the infrastructure for it: Rundeck needs a Java 17+ server and, in production, a database (MySQL/MariaDB, PostgreSQL, SQL Server or Oracle).

Button

Button (https://button.bitgate.dev) is for the simpler case where a script already works on your own computer and you just want colleagues to be able to run it through a web form without setting up servers, databases or worker fleets. Any program works - Python, Node, R, PowerShell, shell scripts, compiled binaries.

Jobs run on the creator's computer, never in Button's cloud, while Button's servers relay the form values and files between the browser and that computer. Because it uses your machine, that computer has to be on and online (tool pages show Ready, Busy or Offline), and each workspace pairs with one computer on every plan; pairing a new computer replaces the previous one.

The security model is locked down to what you explicitly allow. The runner only executes the exact command the creator approved on that computer, pinned by hash. Every form value is passed to the program as its own argument with no shell, and a value can't start with "-". If you change a tool, people have to confirm the new version before running it. Every run is logged with who ran it and when, and you can revoke access or set it to expire at any time.

There are fixed limits you should check against your workload:

• Files up to 25 MB each, and up to 8 files and 100 MB per run.
• 30 minutes per run, one run at a time per computer, and logs up to 1 MB per run.
• Inputs are deleted 24 hours after a run ends, and outputs after 7 days.

Recipients never pay, and you don't count toward the "people" limit; runs per month do include your own runs. Downgrading deletes nothing.

How to put a script on Button

If your script currently uses hard-coded paths or interactive prompts, you'll do a quick cleanup first, then publish it:

1. Update the script to take inputs as command-line arguments (like argparse in Python, commandArgs() in R, a param() block in PowerShell, or $1 and $2 in bash). Take each input file path as an argument, and write the results as files into an output folder that is also passed as an argument. Fixed flags stay part of the command you approve, so colleagues only supply values for the form fields.
2. Sign in at button.bitgate.dev and install the Button runner on your computer (macOS, Linux or Windows) using the one-line command the site shows you - curl on macOS and Linux, or PowerShell on Windows.
3. Open the local setup page, pick your program, describe its inputs (text, number, yes/no, choice, files) and publish to give the tool its own page.
4. Invite your colleagues. They open the link from their invite email, sign in with Google or a one-time email code, fill in the form, press Run and download the results without installing anything.

FAQ

Does my data stay entirely on my computer with Button?

No. While the job itself runs on the creator's computer and never in Button's cloud, Button's servers relay the form values and files between the browser and that computer. Inputs are deleted 24 hours after a run ends, and outputs are deleted after 7 days.

Can one Button workspace run scripts across multiple servers?

No, Button supports one computer (runner) per workspace on every plan, and pairing a new computer replaces the previous one. If you need to execute commands across multiple nodes over SSH or WinRM, use Rundeck, or use Windmill if you want to host multiple workers connected to a database.

What happens if my computer is asleep when a colleague tries to run a Button tool?

The tool won't run because the creator's computer has to be on and online. Colleagues will see the tool page marked as Offline instead of Ready or Busy.

Do the people running my Button tools need paid accounts?

Recipients never pay and don't install anything. On the Free plan ($0) you can invite up to 3 distinct colleagues, and on the Pro plan ($15/month or $144/year) you can invite up to 250 people, with your own account not counting toward those limits.