We've been using windmill for our internal tooling and dashboards and its been great! Genuinely excited to see GPT-4 integration, we'll definitely give it a go.
Some things we've done with windmill so far:
* Slack bots / alerts from scheduled jobs -> All sourced in one location
* One source of truth for connectors (google drive / sheets, slack, postgres database aggs)
* Complex ATS flows (We load our applicants through a windmill task that runs LLMs to parse against a rubric we made, scores then get pushed back into the ATS system as an AI review, then that job reports to slack which helps us prioritize)
* Dashboards (Though I'll admit a bit of sharp-edges here on the UI builder) running complex python + pandas tasks that pull from postgres and run dashboards for us with pretty VEGAlite plots
* Job orchestration -- (though this is partially on hold) we have prototyped orchestrating some of our large workloads, data pipelines, etc. in a few different ways. (we run spark jobs and ray jobs on distributed clusters, and have been trying to use windmill to orchestrate and schedule these, with alerts)
Additionally, windmill made running and tracking these things (like the ATS system) accessible to my "low"-technical co-founder, who regularly will hop in and run the job or browse through error logs of previous runs.
Last, I found some bugs, reported in their discord and I heard back from rubenf very quickly and fixes went in rapidly too! Huge shoutout to the great work the windmill team is doing.
Some things we've done with windmill so far:
Additionally, windmill made running and tracking these things (like the ATS system) accessible to my "low"-technical co-founder, who regularly will hop in and run the job or browse through error logs of previous runs.Last, I found some bugs, reported in their discord and I heard back from rubenf very quickly and fixes went in rapidly too! Huge shoutout to the great work the windmill team is doing.