There is no way that I would depend on a closed source solution from a company with no proven business model.
Let me take that back. When I was a dev lead where our company made up 60% of our vendors revenue, we refused to sign a contract with them until they agreed to put their code in escrow and under certain conditions we had a right to their code.
Putting the code in escrow with a third party like Iron Mountain doesn’t give you access to the code unless the company folds or the product is discontinued.
I’ve been on the other side at another company where we were forced to put our own code in escrow by a large customer. I suggested we do the same for this vendor to our director he had the lawyers do everything else.
In fact when I was on the other side, our company did go out of business (got acquired for scraps), the escrow conditions were triggered, I was laid off as soon as we got acquired and went to work for the customer as a decently paid contractor.
I don't agree. I want the freedom to choose what tools I use, and what their development/profit models are.
By what definition is a company “thriving” that is losing money?
Confluent (Kafka)
https://siliconangle.com/2022/08/03/confluent-reports-strong...
> The company reported a loss before certain costs such as stock compensation of 16 cents per share, with revenue coming to $139.4 million in the quarter, growing 58% from a year earlier. That resulted in a net loss of $117.6 million for the quarter.
The company behind AirFlow is AirBnB. Yes it’s “thriving”. But not based on AirFlow.
Or is that exactly the point you are making?
So for example, if you wanted to create an admin panel / customer dashboard at your company that has the following functionality, you could do all of this in Airplane:
* Display customer data that's retrieved from a SQL query or REST endpoint
* Allow users to select customers and view more details about their usage
* Have a button next to each customer that says "delete customer" which kicks off a Python script that deletes that customer's data
Our business model is that we are the only ones that can grant a commercial license because we hold the copyright and we provide plugins that only make sense at the enterprise scale such as SSO and exportable audit logs.
So in a sense, if you are an enterprise and need to pay us, what is the difference ? Well you can audit the code and experiment with it prior to deciding if you'd like to pursue with us, and not have to go through a salesy pitch to self-host and stress-test our orchestration runtime.
> Based on your pricing page, those helm charts cost "call us" money to use. Am I reading that right?
I couldn’t tell from your reply whether you were explicitly correcting him.
But it’s clear now, that I made a bad assumption about your pricing.
Developer tools, especially ones around code should be open-source. If you like the idea of productionizing one-off scripts, building flows, and managing secrets and schedules in an integrated platform, we have made the same observation as the Airplane team but in a fully open-source manner: [1]. Being open-source in this space offers a lot of synergies, you can for instance build a community around sharing the modules that compose your flows: [2]
In addition, if your primary languages are Typescript, Python or Go, we offer a more integrated experience by parsing the script parameters directly to generate the input spec and the frontend. We are developing our own UI builder as well, more to be announced in the next month. We just released our helm-charts for easier self-hosted deployments: [4]
You can also try it for free at [5]
[1]: https://github.com/windmill-labs/windmill
[2]: https://hub.windmill.dev
[3]: https://windmill.dev
[4]: https://github.com/windmill-labs/windmill-helm-charts
[5]: https://app.windmill.dev