Hi! We've considered making Retool open-source (and we may yet). Is there any particular reason you'd want access to the source code? For example, you can host Retool on-prem (https://docs.tryretool.com/docs/setup-instructions), extend it with custom components (https://docs.retool.com/docs/custom-react-components), and bring in data from anywhere (https://docs.retool.com/docs/queries). And if you were concerned about bugs, we're comfortable providing very tight SLAs, along with 24/7 support if need be.

We felt the same way about Retool and that's why we built Appsmith. https://github.com/appsmithorg/appsmith

Our project has similar goals like Retool, Powerapps or other low code builders for internal tools, but we are building an open ecosystem instead of a closed one.

How close is this project to Retool? We have all the major features already so you won't miss much but we don't have all the UI widgets and native integrations yet. We'll probably reach feature parity in ~6 months.

I would be happy to talk if I can help. I am building https://github.com/brainless/dwata but from a different angle. It is not a builder as such and has no SQL in the interface at all.

It is where non-technical folks can do everything - dig into data, merge data from CSV even, create reports. SQL is generated automatically from schema reflection. There is no engineering help needed, at least at this stage and it does multi-table JOINs by itself already.