Windmill looks cool! I've always wanted to write something like Huginn [1] available as a single binary.

Can I ask, what were the benefits of writing a new workflow engine instead of building around Temporal?

1 - https://github.com/huginn/huginn

The biggest reason is to be able to deploy, as you mentioned, windmill as a single binary that you can then easily scale horizontally. The second one is deeply rooted to how it works, it is running fork of those scripts calling the interpreter of those respective languages. It has pros and cons but you can do interesting things like having workflows in different languages, first step in python, second step in go.

Overall it would have been possible to build this on top of Temporal but the biggest benefit of Temporal, which is idempotency/checkpointing is not something we could have offered at the level of abstraction that we operate, running arbitrary single scripts piped together using a result graph and a shared mounted folder. So why bother?

WOW. I have been looking into this at work today, and windmill is def. what I was looking for, a low-code solution that do not hate code (as text). Thank you so much for creating this. The value prop. that you have in the intro[1] is perfect. The first paragraph on github is maybe correct. But I'm still not sold on what it actually does. Marketing is hard. Hope you will succeeded, the product looks great!

[1] https://docs.windmill.dev/docs/intro/