Windmill allows you to write code in any places but we have a hub augmented every day with pre-made integrations so that you do not have to: https://hub.windmill.dev. We also have native support for BigQuery, Snorflake, Mysql, GraphQL, with dedicated editors.
Hence, I fail to see how it would be any faster to build workflows in tooljet than in windmill. I do not have a business license of tooljet so I have not been able to do the comparison. Interested to hear feedbacks on that.
Our workflow engine and UX seems to be a lot more advanced from what I can see because we have been iterating on it for longer. Congrats on the launch though and may the best open-source alternative to Retool win.
The issue with low codes tools is that I cannot ask gpt to do stuff for me, and I have the risk that gpt cannot help me as he don't know the tool.
IMHO, real value is when you can extend/customise ToolJet using custom code or database queries. And this is where GPT can help. We even have a inbuilt Copilot for these use cases.
Windmill is a great product too but it is totally pro-code and building workflow with it, one has to write a lot of code compared to ToolJet. Hence, ToolJet would be definitely faster here.
While make.com is focussed just on automation but for all kinds of use cases and not focussed on solving internal tooling problems for the companies.
However, process street does look focussed on building software for internal applications but it is more towards no-code spectrum which has its advantages but makes it less customisable. ToolJet, on the other hand is more customisable and developer friendly because of our low-code approach.
On a more serious note how does this compare with Retool? I remember that doing the HN rounds in 2019 and it’s still going