Free desktop automation bots, downloaded as real executables
This is the directory where standalone automation bots are downloaded as real
desktop executables for Windows, macOS and Linux - every bot is free, and every
launcher is built for resellers to distribute under their own brand.
11 bots4 platformsFreeWindows launchers are currently unsignedmacOS (Apple Silicon) launchers are currently unsignedmacOS (Intel) launchers are currently unsignedLinux launchers are currently unsignedSHA-256 checksums published
Featured bots
Editorially curated - not a popularity ranking; this catalogue keeps no usage telemetry.
Every bot listed in this directory was built in the desktop product and compiled into a
standalone executable exactly this way - the launchers you can download here are working
demonstrations of that capability, and the same capability is what you would use to
build and sell bots of your own.
Download the launcher for your platform. It is a real executable, not a
script to paste into a hosted platform.
On launch it fetches its configuration from the directory by the bot id
embedded in its own filename - which is why the file must never be
renamed.
It runs locally on your machine and writes its output beside itself, as
CSV or JSON; nothing is hosted and nothing is queued.
The artifact model needs no infrastructure on your side: no per-client
hosting, no platform instance per customer. You deliver a compiled
launcher; the customer runs an executable. What a licence costs, and
which tiers include reseller rights, is published - and only published -
on the product pricing page.
Sold bots can be switched off remotely when their configuration uses
server-controlled activation: updating the stored activation state stops
the launcher at its next start, within the published cache window - you
never touch the client's machine.
Password-gated delivery is available per listing, with one qualification
stated plainly on the sell page: a password is meaningful only when the
delivered configuration is encrypted, because a plaintext configuration
is readable by anyone who knows the bot's id.
A launcher executable named for the bot (for example BOT_my-bot.exe on Windows). The launcher is a standalone desktop program — no installer, no platform account.
Does it work offline?
The first launch needs an internet connection to fetch the bot's configuration. After that, behaviour depends on the bot: automations touching websites need connectivity, local file automations do not.
Do I need an account to download or run a bot?
No. The directory has no accounts: downloads and configuration fetches are public endpoints rate limited by IP, and nothing you run requires signing in.
Does the bot run on my machine or in the cloud?
On your machine. The launcher is a desktop program that runs locally; the only network calls it makes are the configuration fetch at launch and whatever pages the bot itself visits.
Can I run several different bots on one machine?
Yes. Each bot is its own launcher file with its own configuration id, so multiple bots coexist without interfering; run them one at a time unless a bot's page says concurrent runs are safe.
Can I rename the downloaded file?
No. The filename carries the bot's configuration id; renaming the file breaks the configuration fetch at launch.