Awsome! Looking forward to your feedback.
The fact that it can be set up as an independent app or as a library is really useful.
I would also like to point out Journey ( GitHub - shipworthy/journey: Durable Workflows in a[n Elixir] package. )
Cool! Thanks for pointing it out.
Been interested in something like this. The real killer is the integrations. I did poke at some LLMs to figure out if we could run the existing Python Airflow integrations in a Port or similar and do the stuff we want in Elixir. Just as a solution to bootstrapping serious integration support.
Yep, integrations are one of the key pieces! I already started to experiment on how to run some of our existing Airflow DAGs into Gust, using Pythonx. Hopefully, next quarter we’ll be able to ship this feature into Gust.
If you want to contribute to this idea, let me know!
shout about it when it happens, I wanr to try it. No spare cycles or clients in that area unfortunately ![]()
From a workflow implementation perspective, most real-world use cases require API-level integration with multiple systems to avoid forcing users to switch between different interfaces while completing a single task.
This typically includes API services , human-in-the-loop steps, event-driven triggers, and webhook-based callbacks. With that in mind, I wanted to understand whether the current approach is to handle these integrations directly within the workflow step logic, or whether there is an intention to adopt a standard communication or integration pattern to support these interactions more consistently.
Could you add Lightning (OpenFn 2.0) to your comparison?
Done ![]()
Update: Gust can be deployed in a multi-node architecture ![]()
Really excited to see this. Airflow always felt like too much software for my simple self-hosting needs.
Hi! Yes, I’ve checked durable, both parse and run durable workflows. However, Gust has some key differences:
- Is UI centric: Dashboard with graphs, errors, logs, code, and other things like editing secrets and runs.
- It’s not a proof of concept; I am using on production, multiple nodes, and it has a good amount of test coverage.
Overall, they’re alternative approaches to the same problem. ![]()
Hi,
I saw it had live log update in the UI but I wonder if it track the log per run as this might be important for audit purposes ?






















