First work out which part of the platform you use: scripts, workflows or internal apps. Most alternatives cover the workflow side only, so if you rely on the app builder you'll need two tools. If you just want durable background jobs, a narrower code-first tool is simpler; for visual automation or declarative orchestration, pick from those groups.
Do you use Windmill for scripts, for workflows, or for the internal apps built on top of them? Your answer decides which of the nine below are even in the running.
Do you need the app builder, or just the jobs?
Windmill's own page covers scripts, workflows and internal apps on one platform. Most rows here cover only the workflow side, so if your team builds admin panels and dashboards in it, plan for a separate internal tool builder for that half; my no-code databases guide is a good place to start if your apps sit on top of simple tables.
If what you need is background jobs and durable workflows in your own codebase, the field narrows and the tools say so. Trigger.dev describes an open source platform for workflows written in TypeScript. Inngest calls itself a durable execution platform. Hatchet, per its site, is a platform for orchestrating agents and scheduling background tasks. Kestra is built around declarative orchestration, where workflows are defined in a declarative language rather than written as application code.
Windmill also highlights open source and easy self-hosting. If that's why you chose it, check the licence and self-hosting terms of each alternative, because open source can mean very different things in practice, from a fully permissive licence to an open core with some features kept for a commercial edition.
Where do the visual automation tools fit?
n8n, per its site, combines AI capabilities with business process automation. Automatisch says it's open source workflow automation. Node-RED describes itself as a low-code tool for wiring event-driven flows. Tines, by its own description, is a platform aimed at enterprise teams. Retool Workflows says it runs automations on event-driven or recurring schedules, which is worth a look if you used Windmill mainly for scheduled scripts.
Visual tools can open automation up to people who don't write code. The trade-off is that complex logic can be harder to review and version than plain code, so ask how each one handles version control before you commit. My AI workflow automation guide shows the kind of jobs these tools take on.
Build a workflow or job platform that belongs in one of these groups? Send it in for consideration ahead of the next update.
How do the nine compare?
| Tool | Style | Good for |
|---|---|---|
| Automatisch | No-code automation | Non-developers |
| Hatchet | Orchestration engine | Running critical workflows |
| Inngest | Durable execution | Backend developers |
| Kestra | Orchestration platform | Data and platform teams |
| n8n | Workflow automation | General business automation |
| Node-RED | Low-code tool | Flow-based programming |
| Retool Workflows | Developer workflow automation | Cron jobs, alerts and ETL |
| Tines | Automation platform | Teams wanting secure automation |
| Trigger.dev | Durable jobs in TypeScript | Long-running tasks |
Which platforms made the list, A to Z?
Alphabetical, so in no particular order of preference, with each line drawn from the vendor's own pitch.
Automatisch
Best for: Building workflow automation without coding, in the cloud or self-hosted, as the vendor offers.
Hatchet
Best for: Self-hosters, since the vendor stresses it's open source and fully MIT-licensed.
Inngest
Best for: Background jobs and workflows with automatic retries and step-level observability, as the vendor describes it.
Kestra
Best for: Simpler, faster and scalable workflows, which the vendor says come from defining them in a declarative language.
n8n
Best for: Combining the flexibility of code with the speed of no-code, which is how the vendor sums itself up.
Node-RED
Best for: Real-time data work; the project calls itself the easiest way to collect, transform and visualise it.
Want AI doing the heavy lifting in your marketing?
I build the systems that handle the boring 80 percent, so you get your week back. Done properly, with the human kept in.
Retool Workflows
Best for: Production automations from one governed platform, in the vendor's words.
Tines
Best for: Large organisations; the vendor pitches apps, agents and automations in one environment for enterprise AI.
Trigger.dev
Best for: Jobs that need retries and queues, plus what the vendor calls LLM observability.
What's my advice if you self-host?
Pick one real job you run today and port it to your top two before anything else. A good test is a scheduled script that calls an external API, retries on failure and writes to your database, because it touches scheduling, secrets, retries and logging all at once. Run both versions for a week and compare how easy it was to see what happened when something failed.
If you self-host, look past the install guide. Check how upgrades work, which features are kept for a commercial edition, and how the platform stores secrets and credentials. A tool that's quick to start but painful to upgrade will eat into your team's time every few months.
- Write down every job, script and app you run on the current platform.
- Mark each one as background job, visual workflow or internal app.
- Choose a tool per group, and keep the list of tools as short as you can.
- Port the lowest-risk job first and run it alongside the original until results match.
Keep a short log as you go of anything that behaved differently, such as time zones on schedules, retry limits or how secrets are referenced, because those details tend to catch the second and third jobs too. Once the first job has run cleanly for a week, move the rest in small batches, and only switch off the old platform when the last job and its alerts have moved across.
Want your tool on this list? Featured spots and reviews here are paid partnerships. Here's how to partner with me.
Frequently asked questions
What's durable execution?
It means a workflow's progress is saved after each step, so if a server restarts or a call fails, the workflow resumes where it stopped instead of starting again.
Can I self-host all of these tools?
Not all of them. Several say they're open source and self-hostable, while others are cloud-first. Check each vendor's own deployment docs and licence.
Do I need a separate tool for internal apps?
If you built dashboards or admin panels on your current platform and the replacement only runs workflows, yes. An internal tool builder covers that part.
Is visual automation suitable for developers?
It can be, especially for joining up SaaS tools quickly. For complex logic, a code-first tool keeps everything in version control with the rest of the app.
How do I move scheduled jobs without missing a run?
Run the new job alongside the old one for a while, compare the outputs, then switch off the original once you're confident both behave the same way.
