windmill

It's very close to the direction we're taking for windmill.dev, we call it "operator builders" rather than focus on "knowledge graph" which the article is very light on details of. What I'm mostly reading is a developer platform and runtime where users can build agents that can run tools and for that you need a secure code runtime, ACL/permissions, easy way to build apps or what cloudflare OS call gadgets. We're betting on this too at https://github.com/windmill-labs/windmill, very curious to see if that's the future for most enterprise and if a model where everyone vibe-code/fork cloudflare OS to their enterprise need is the future, or a more exhaustive/enterprise platform like ours does.

I think Windmill.dev (https://github.com/windmill-labs/windmill) is really cool, and fully support their desire to be paid for their work. However, their README says: > “Windmill is fully open-sourced (AGPLv3)…” But their LICENSE says: > ... The files under backend/ are AGPLv3 Licensed, except any snippets of code under the compile flag ‘enterprise’. Those snippets and files are under a proprietary and commercial license. Private and public forks MUST not include the proprietary/commercial code mentioned above. I dove deeper into the code, there are around 300 files in the codebase that contain references to enterprise or private features, so it's not a clearly separated directory that can just be removed. They have 1.1k forks of their repository that I can see on Github, and I doubt all of them took the time to strip the proprietary code

I cannot believe there has been no mention of things like n8n, activepieces and windmill in this thread. SaaS will utterly collapse in 18 months. https://github.com/n8n-io/n8n https://github.com/activepieces/activepieces https://github.com/windmill-labs/windmill

Windmill - https://github.com/windmill-labs/windmill

Inngest is very cool, and if you are interested in the topic but absolutely want to self-host, 2 other high-performance durable execution engines that enable all the above and that you can self-host and are open-source and mature would be temporal and windmill. Both can use postgresql as the queue (temporal can use cassandra too), the rest can be done leveraging the transactional properties of postgresql, such as atomic counters for the concurrency keys: https://github.com/windmill-labs/windmill/blob/main/backend/... or re-queuing jobs that haven't progressed when they should have (most likely, worker crashed). There are very cool things you can do today without too much complexity with the primitives that modern database are capable of. Should one rebuild it for their startups, no, but if you were to extract the very core of the durable

Look very similar to the script builder portion of https://github.com/windmill-labs/windmill, but not open-source, not self-hostable, without open-source integrations (https://hub.windmill.dev/) and without a workflow engine disclaimer: I'm founder of ^

For an alternative to airplane.dev, you can checkout Windmill. https://github.com/windmill-labs/windmill "Open-source developer infrastructure for internal tools (APIs, background jobs, workflows and UIs). Self-hostable alternative to Airplane, Pipedream, Superblocks and a simplified Temporal with autogenerated UIsm and custom UIs to trigger workflows and scripts as internal apps. Scripts are turned into sharable UIs automatically, and can be composed together into flows or used into richer apps built with low-code. Supported script languages supported are: Python, TypeScript, Go, Bash, SQL, and GraphQL. " If you search HN, you'll find the creator of Windmill comment on comparisons to airplane.dev: https://hn.algolia.com/?dateRange=all&page=0&prefix=false&qu...

Yes it goes in that direction, however note that you can already do this in a not too hard way. Our openflow spec is both open-source and has a full openapi definition: https://github.com/windmill-labs/windmill/blob/main/openflow... you can use that to generate client sdks in any languages and build your own dag with it. That's what one of our customer did building a reactflow to openflow library: https://github.com/Devessier/reactflow-to-windmill It's not as good as the decorator way but we move fast and if you still have interest for it we could prioritize it (and ask for feedbacks :))

I would love to begin using this system, but the licensing is giving me serious pause. While most of the software is under the AGPLv3, the Commercial License section of the README [0] implies that the company takes on a fairly broad interpretation of the AGPL. In particular, the line "[...] to build a feature on top of Windmill, to comply with AGPLv3 your product must be AGPLv3 [...]" seems to imply the company aligns with the stance taken by Google and other companies: that even calling the application via API is enough to trigger copyleft [1]. This implies that if I were to build a sign-up form that triggers a Windmill workflow in the backend, my entire application would either need to be AGPLv3 or I would need a commercial license. That's perfectly reasonable, as it means any non-AGPL use will have to contribute back to Windmill via a

LICENSE ??? https://github.com/windmill-labs/windmill/blob/main/LICENSE I'm a bit confused.

The GitHub repo for the open source project gives a better intro/sell: https://github.com/windmill-labs/windmill (Especially the video)

Looks cool and thanks for sharing. Founder of windmill.dev, an open-source, extremely fast workflow engine to run jobs in ts,py,gosh whose most important piece, the queue, is also just rust + postgresql (and mostly the FOR UPDATE SKIP LOCKED). I'd be curious to compare performances once you guys are comfortable with that, we do them openly and everyday on: https://github.com/windmill-labs/windmill/tree/benchmarks I wasn't aware of the skip B-tree splits and the REINDEX CONCURRENTLY tricks. But curious what do you index in your jobs that use those. We mostly rely on the tag/queue_name (which has a small cardinality), scheduled_for, and running boolean which don't seem good fit for b-trees.

One way to use raw python/javascript/bash on top of a postgres scheduler is to run a single container of https://github.com/windmill-labs/windmill. It only requires a PG connection and does not require a pg extension. It implements a scheduler that is implemented on top of PG and can run any of the aforementioned language in a very practical and observable interface.